Hello,
we need to transition from the default verifier to a custom one. What are our options?
Hi Stefan,
Thank you for reaching out! It’s great to hear you’re working on transitioning to a custom verifier.
With the Plug n Play SDK, transitioning to a custom verifier can typically be done by implementing your own authentication logic and integrating it with the Web3Auth SDK. Here are some general options you might consider:
-
Utilize the Custom Verifier within Web3Auth SDKs: This allows you to define your own custom logic for verification. You can refer to our documentation on how to set it up.
-
JWT Tokens: If you have a custom authentication backend, ensure that it can issue JWT tokens compatible with Web3Auth for seamless integration.
-
Custom Verifier Setup: If you’re looking to create a transactional flow with specific requirements (like custom claims), make sure to define your verifier’s capabilities clearly prior to implementation.
If you have any specific scenarios or requirements in mind, feel free to share them, and I’d be happy to assist further!
Happy coding!
Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.
but how to migrate my existing users to the new verifier? this must be possible somehow
or can we keep both verifiers at the same time?
Unfortunately migration of users is not possible between verifiers. It will case the accounts addresses to change. It will result in different private keys for the users. Please read through this doc to know what are the factors that cause change in private keys: Different Private Keys/ Wallet Address across Integrations | Documentation | Web3Auth
1 Like
Yes you can keep both verifiers available at the same time, but the user has to login through the correct verifier in order to get the correct address.
1 Like
how would i show the different verifiers to the user? does this have to be on a different website/portal?