It didn’t work and after long struggling, I figured out that I had to put https://auth.web3auth.io/auth in the “Allowed Callback URLs” section on Auth0’s application settings.
It makes sense once you understand but it was quite time consuming since there are too wide configuration areas to check (Frontend web3Auth config, web3Auth dashboard, Auth0 dashboard).
My first question is: it’s mandatory to set https://auth.web3auth.io/auth in the “Allowed Callback URLs” section on Auth0’s application settings in order to implemented aggregate-verifier with Github?
If yes, where could I find this information?
And second question is: Can I do aggregate-verifier with Github with Web3Auth modal?
I hope you’re doing well, and thank you for giving Web3Auth a try!
Absolutely, to successfully complete the flow, it’s indeed necessary to add the callback URL. You can find more detailed instructions and guidance on this in our guide: https://web3auth.io/docs/guides/auth0. This should help you set things up correctly.
Regarding your second question, unfortunately, that’s not possible. However, I highly recommend checking out our documentation for both modal and no-modal custom authentication. These resources will give you a comprehensive understanding:
Additionally, you can explore our custom-auth examples for both modal and no-modal setups here: GitHub - Web3Auth/web3auth-pnp-examples. These examples should provide you with practical insights and help in implementing your solution.
If you have any more questions or need further assistance, please don’t hesitate to reach out. I’m here to help!