Custom Authentication is the ability to integrate your own authentication flow with Web3Auth. We suggest using Custom Authentication instead of relying on Web3Auth's default authentication Modal.
The benefits of using Custom Authentication are:
- It provides a comprehensive user experience from beginning to end.
- You can customize the data required from the authentication service and onboard users according to your specific needs.
- You can seamlessly migrate your existing users to the new authentication flow with Web3Auth, without requiring them to create new accounts.
Supported Login Providers
Federated / Identity Providers
Bring your own Custom Login Providers
For Custom JWT based authentication services, you need to use the
Web3Auth Plug and Play No Modal SDK, since the Web3Auth
Modal will only help you configure the social logins present within the Modal UI.
Bring your own custom providers with Web3Auth, using one of the custom login schemes (either via JWT or ECDSA signatures). This way, your users can still use your existing login provider. The application should follow the JWT specification and use JWKS for signing the JWT, whose public keys are exposed by an endpoint.
Here are a couple of FAQs that might help you:
Which logins should my application support?
- You can select from this list or use your own custom authentication. There are some nuances with certain login providers, so don't hesitate to get in touch with us.
Should different logins lead to the same key?
You can choose to connect logins with the same
Verifier ID. For example if a user uses generic email logins and a gmail login to login on different occasions he/she can still retrieve the same key. This can only be done on logins which share a common unique identifier for a user.
Read more about aggregating logins here.
Can XXXX authenticator/login be supported?