Is my Web3Auth social login (Google) permanently locked due to MFA on the Development Network?

Developer Discussions
1

I’m running into an issue with Web3Auth on the development network related to MFA for my Google social login.

A while back, I enabled MFA during testing. Since then, I’ve lost access to the additional MFA devices/keys. I had assumed that MFA settings were tied to a specific project in Web3Auth, but now I’m wondering if they’re actually tied to the network (devnet) as a whole.

Right now, whenever I try to log in with the same Google account on any project that uses the Web3Auth development network, it still prompts for MFA—which I can no longer complete.

So my question is:

Is my social login on Web3Auth devnet effectively bricked?
In other words, is MFA tied to the development network identity (per user), not per project, meaning I can never log in again with this Google account on devnet unless MFA is recovered/reset?

Any guidance or clarification on how Web3Auth handles MFA state across projects on devnet would be greatly appreciated.

2

Hi Jerry — thanks for the clear description, and sorry you’re stuck here. This looks like an account/MFA issue (not a code bug). I’ve summarized what I see and listed the minimal details the support team will need plus some next steps you can try now.

Summary (what you’ve said)

  • SDK / product: Web3Auth (development network / devnet)
  • Issue: After enabling MFA during testing, you lost access to your additional MFA devices/keys. Now every project on the Web3Auth devnet that tries to sign in with the same Google account prompts for MFA which you can no longer complete.
  • Question: Is MFA state tied to devnet (global per-user) rather than per project, meaning you’re effectively locked out on devnet unless MFA is reset/recovered?

What’s likely

  • If the MFA prompt is coming from Google (i.e., it says Google or shows Google’s 2‑step verification UI), then it’s Google-side 2FA and you’ll need to recover the Google account (Google account recovery flow). That behavior would be independent of Web3Auth projects.
  • If the prompt is coming from Web3Auth’s MFA feature (the UI/label mentions Web3Auth or shows a Web3Auth flow), then the MFA state is stored by Web3Auth for that identity on the devnet and can apply across projects that use the same devnet environment. In that case you’ll need Web3Auth support or a dashboard action to reset/remove MFA for that user on devnet.

What will help Support diagnose and act (please provide any of these if you can)

  • Does the MFA prompt explicitly reference Google or Web3Auth? (A short screenshot is ideal.)
  • Web3Auth project/client_id (if you have it) and whether you’re definitely on devnet (not testnet/mainnet).
  • The email address used with the Google login (or the user identifier you used with Web3Auth) — needed by support to find the account. If you prefer not to post it publicly, say you’ll DM it or include it in a private support ticket.
  • A screenshot of the MFA prompt and any error text.
  • Approximate timestamp(s) of the failed login attempts.
  • Any browser console logs or network errors (optional) if you see error codes.

Immediate steps you can try

  • Check whether the prompt is Google’s 2‑step verification. If so, try Google’s account recovery: https://accounts.google.com/signin/recovery
  • If the prompt is Web3Auth MFA, contact Web3Auth support or open a ticket from the Web3Auth dashboard asking for an MFA reset on devnet for that user. Include project/client_id, user identifier (email), screenshots, and timestamps.
  • Short-term workaround: use a different Google account (or a new test account) on devnet while you get this resolved, or move to a private testnet/project that’s not sharing the devnet MFA state.

Helpful links

If you want, I can: (a) file a support summary for the team including the info above, or (b) wait for you to share a screenshot and the client_id so I can attach them to the support ticket. Which would you prefer? If you’d rather not post sensitive details publicly, let me know and I’ll tell you how to share them privately.

Note: This response was generated by an AI bot and may require further verification. The MetaMask Community Team has tracked this issue and will be responding as soon as possible.

Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. MetaMask Developer Office Hours