Web3auth v10 breaks MFA setup on v9

Embedded Wallets (Web3Auth)
1

Hi,
There is a problem of MFA when upgrading from web3auth v9 to web3auth v10.

In v9 we was using custom provider for social logins: discord, google, X and facebook.

We recently switched to web3auth v10 and now our users are blocked on MFA, the page is loading indefinitively.
When checking in console, errors are:

  • Google: invalid scope
  • Discord: incorrect anwser

The problem seems to be this one:
In v9 custom providers passed to web3auth was also used for MFA.
So our users have validated their MFA with our own custom provider.

But now with v10 custom providers are not used anymore for MFA, so when our users are trying to connect to their wallet and validate MFA they got an error because provider use is web3auth provider.

We are using the last version of web3auth: 10.15.0

Thank you.

4

Hi @jeanbenoit You can just ask your questions here and we will follow up.

Didi you check with the migration guide here?

Kindly let us know the details if your issue still exists.

5

Hi,
The problem is only when users has a MFA setup that protected their account.
Users without MFA are able to connect to their accounts and the right AA address.

6

May I know if you have configured the social logins on the Web3Auth Dashboard?

  1. Log into your Web3Auth Dashboard and select your project.

  2. Navigate to the Authentication tab.

  3. Under Social Logins, click the gear icons to create custom connections for Discord, Google, etc.

  4. Input the Connection ID and the Client ID.

7

Yes as stated in my message, users without MF are able to connect to their account and they are connected to the right address.

8

Understood. I have passed your case to our team, and we will reply you as soon as we can.

1 Like
9

Hey @jeanbenoit

As I looked into our previous SDKs as well, the custom authentication you use for logging in, is not used by our MFA system. This is because the second login is triggered by our own domain auth.web3auth.io and we cannot get access to the token that you are getting in your domain directly.

Hence this particularly is not the issue over here. The issue is related to something else which we will be able to determine after seeing the exact console logs. Is it possible for you to share the exact console information when this error is happening? Additionally any screen recording/ live demo of the app will also help us test further.

10

Hi @yashovardhan,
How can I send you the 2 videos of v9 and v10 ?
There is personal informations i would like not to share on public forum.

Thanks you.

11

Hi @jeanbenoit ! So sorry for the late reply. If you have concerns about sending videos here, you can DM to @yashovardhan on telegram: t.me/yashweb3

1 Like
12

@holyyy Thanks ! I have contacted him.

1 Like
13

I have raised the issue with the engineering team, we will get back to you after verifying this.