Migrating from Passwords to SAWO's Passwordless
Proper planning is critical for the conduction of successful migration, at SAWO we have already crafted the process to scale for you, the quickguide has outlined all requirements and design considerations, we have made sure that the process mitigates all risks and doesn't hold any disruptions for the end-user.

Why Migrate to SAWO?

Passwords as a form of website and app authentication have been around for decades. They offer just a decent level of security and adding onto them they are pretty cumbersome to remember, enter and maintain, for both the firm and the user and initiate increased bounce rates. So, we welcome you to ditch passwords altogether, along with a great level of security and user convenience. Say hello to SAWO!

How can I implement SAWO in my Own App/Website?

As you already have an authentication logic that validates passwords stored in your own database, most of the work has been completed by you and we don't want you to worry about anything else now, so, we don't store any data of our end clients. A simple payload is returned to you using which you can conveniently map your clients with the identifier you chose.

How does our SDK work?

We authenticate your end customer with asymmetric encryption and post out a payload of your client with details.

Replacing your Login form with Our iframe

This is the moment from where we start taking over your worries, initially, we request you to replace your current login form with SAWO.

What happens after you replace your login form?

After your client is successfully authenticated, a payload is sent from our side to your server so you can further process it from your end. Check out What to do with your payload?​

New Users

If a new user gets authenticated, you can cross check with your Database and make a new entry with the payload provided.

Existing Users

As you already have existing Clients in your Database, you can map your Clients with the identifier sent in the payload by us.
Last modified 2mo ago