Reduce Options in socialBackupFactor

Help - Plug n Play
1 
import { Web3Auth } from '@web3auth/modal';
import { CHAIN_NAMESPACES, WALLET_ADAPTERS } from "@web3auth/base";
import { OpenloginAdapter } from "@web3auth/openlogin-adapter";

I have this as my setting

const openloginAdapter = new OpenloginAdapter({
      loginSettings: {
        mfaLevel: "mandatory",
      },
      adapterSettings: {
        mfaSettings: {
          deviceShareFactor: {
            enable: false,
          },
          backUpShareFactor: {
            enable: false,
          },
          socialBackupFactor: {
            enable: true,
          },
          passwordFactor: {
            enable: false,
          },
        }
      }
    });

My users are using Google auth only to sign in, as 2FA is mandatory, they are prompted to the 2FA social backup screen with lot of options, even an option to input email / phone in which they use email that they use previously which should not be the case. I want to disable everything and keep just sms verification in 2FA.

2

Hey @coolatmusic
Other than the parameter enable other two non compulsory parameters are also available.

enable: boolean;
priority?: number;
mandatory?: boolean;

Mark mandatory as false for the factors you do not wish to be enforced.

3

Thanks for that but would really love to know the solution of the issue i raised.

4

I understand your concern, @coolatmusic. While for the main login modal you can use showOnModal: false to cherry pick your social login options but social recovery options do not have such a level of fine-grained control yet.

5

The issue with this is, the users that are using google login if they use the same email for 2FA as well, it doesnt make sense. And it lets you do that without and error. It gets stuck in a loop, which make our user feels that onboarding is broken.

6

Okay, that’s interesting, @coolatmusic. You mean to say that let’s say I logged in through Google with email A and then used email passwordless as a recovery factor(because Google login gets disabled in recovery factor setting) for the same email A. Does this flow make the users get stuck in a loop?
Please confirm if this what’s happening and I’ll try to re-create this behaviour on my side before raising this to the product team.

7

Hey yes just use the same email id that you used for google auth to do 2FA and it ll get stuck.

1 Like
8

Thanks a ton for reporting this, @coolatmusic. I am surprised how this went unnoticed till now. I have raised it to the product team. Unfortunately, I do not have an ETA immediately, but will let you know more if I have something. Thanks for your patience.

9

Hey @coolatmusic,
I have an update for the issue you raised. The fix is on the way and I will let you know once it’s released. Once again, thanks for highlighting and keeping web3auth bug-free.

10

No worries, thanks for resolving. Hope in future we get more control over 2FA

1 Like
11

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

12
13

@coolatmusic This has been fixed. Please confirm if you are still facing the issue.

1 Like
14