I’m trying to use aggregate verifier using Google and Discord. It works but the address in each login (using same email) is different. Or in order to get the same address I have to use Auth0?
Please advise
hi @max1 ,
yes, in order to get the same address you can use for example: Auth0.
Please read our documentation about this topic : https://web3auth.io/docs/troubleshooting/different-private-key
Also here is an example:
@TomTom I read the documentation. from what I understand that I can use aggregate verifier and create the sub verifiers under the aggregate verifier in order to get the same address, BUT I did exactly that but without using Auth0, it didn’t works.
Here is my setting in the dashboard:
Here is my code:
So the question is can I use aggregate verifier without Auth0?
Hey @max1,
Absolutely, it’s possible to utilize aggregate verifiers without the need for Auth0. To better assist you with this setup, could you share the specific field of your idToken that you’re using for aggregating the verifiers? The choice of this field is crucial as it determines the basis on which verifiers can be aggregated efficiently.
Looking forward to your response so we can guide you more effectively!
I don’t understand what you mean specific field of the idToken? where can I look to see this? I follow this tutorial - https://web3auth.io/docs/auth-provider-setup/aggregate-verifier and nothing is mentioned there.
Here is my web3auth.connectTo()
this 2 functions returns 2 different wallet even though I set the same verifier with different sub-verifier at the beginning.
Well, for the sub verifier for Google and Discord, the only option is to put the client ID. there is no option to specify the verifier field
Hey @max1,
I hope you’ve had the opportunity to review our documentation on setting up an aggregate verifier here. As outlined, particularly in point seven, aggregate verifiers are configured by adding sub-verifiers with a common identifier. For an app that has the verifier ID as email, this ensures that a user logging in with the same email across different methods is assigned the same wallet address, the core functionality of aggregate verifiers.
It seems there might be some confusion when accessing the subverifier edit modal, it doesn’t show the option to edit the JWT verifier id while the modal for creation of subverifier has it. I’ve attached a screenshot for reference to guide you through the creation of sub-verifiers accurately and assigning the JWT verifier ID to email.
For the best results, I recommend removing the existing sub-verifiers and creating new ones following the guidelines provided in our documentation. This will ensure your setup aligns with the intended functionality and offers the seamless experience we aim for.
Our documentation is a comprehensive resource designed to assist you through the setup process. If any part of it is unclear or if further questions arise, please don’t hesitate to reach out. We’re here to support you and ensure your success with our platform.
No, what I am trying to do is to use sub verifiers for multiple social logins without using Auth0. Your screenshot shows with Auth0 provider.
For other social logins beside JWT and Auth0, there is no option for me to select JWT verifier ID.
All I want to have is to login with either Google and Discord without Auth0 and get the same wallet.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.