Unable to verify OTP or Recovery phrase while on New Device Detected page of MFA

Help - Plug n Play PnP Web SDKs
1

When asking for help in this category, please make sure to provide the following details:

Hello, I am trying to login using MFA but always get this error using both Autheticator / Recovery phrase (which i have in my email).

I noticed that it works ok on your example app - https://pnp-modal-playground.vercel.app/, both the methods, and from the screenshot for OTP verification I can see a client_id going out, which is the same ID I noticed on your example app too. I am wondering if this could be an issue for the reason I am getting a 401? Or do I have to add some setting in my app on https://dashboard.web3auth.io/ ?

For recovery phrase, I get the following error -

index-BjsGvyRR.js:1 Error: Share doesn't exist : traceId: undefined - spanId: undefined
    at f (index-cqWneRRW.js:1:1876)
    at w.error (index-cqWneRRW.js:1:2439)
Caused by: CoreError: Share doesn't exist 
    at T.fromCode (tkey-B4NzNTGc.js:1:3787)
    at Proxy.shareToShareStore (tkey-B4NzNTGc.js:3:515)
    at Proxy.inputShare (tkey-B4NzNTGc.js:8:3776)
    at Object.inputBackupShare (tkey-B4NzNTGc.js:8:51931)
    at async ar.d (index-BGM19B3o.js:94:681)
 'input backup share'

Hope we can solve this one quickly as I feel its do with some config since your example app is working. Thanks!

2

Hi Amin,

Thank you for providing detailed information. Let’s see if we can figure this out together.

Summary of the Issue:

  • SDK: Web3Auth PnP Web SDK
  • Version: 9.7.0
  • Platforms: Mac, Linux, Windows
  • Error: Failure in MFA recovery phrase and OTP verification, possibly due to misconfiguration, resulting in a 401 error and a “Share doesn’t exist” message.

Given that the example app works, there might indeed be a discrepancy in your configuration. Here are a few steps and checks you can perform:

  1. Client ID Configuration:

    • Double-check your client_id in the Web3Auth dashboard. It should match the one you are using in your app.
    • Ensure that all settings in your Web3Auth dashboard are correctly configured for your environment.

  2. Check your Configuration:

    • Ensure that your app registration in the Web3Auth dashboard includes the correct domain and redirect URIs.

  3. MFA Settings:

    • Verify that your MFA settings are correctly configured and that your method of handling OTP and recovery phrases is properly implemented.

  4. Error Handling:

    • The error "Share doesn't exist" suggests there might be an issue with the storage or retrieval of recovery shares. Please revisit your logic for storing and retrieving these shares.

  5. Cross-Reference with Working Example:

    • Compare your integration code with the working example to ensure there are no discrepancies.

Here’s a relevant documentation link that might be useful for double-checking your implementation: Web3Auth MFA Implementation

If everything appears correctly configured in the dashboard and your implementation is accurate, but the issue persists, it might be helpful to provide:

  • Web3Auth Initialization and Login Code Snippets
  • Console logs and any network request screenshots not already shared

Please, revisit your configurations following the pointers above, and if you need further assistance, don’t hesitate to reach out. We’re here to help!

Note: This response was generated by an AI bot and may require further verification. The Web3Auth support 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. Web3Auth Developer Office Hours

3

Hey @amin1

Kindly share the web3auth network and the email you’re using to log in. Check DM to share your email with me.

4

Shared in DM with you

5

Setting up the auth codes based on the default config but using the custom authenticator to verify it was causing the issue.

Let me know your findings