Identification Problem in TEA PROTOCOL

Help - Plug n Play
1

Hello, help me with this problem, as I should have the password recovery option, which I do not have, in TEA PROTOCOL.

ayuda
ayuda1144×518 14.1 KB

2

Hello Tecno Rex,

Thanks for reaching out to the Web3Auth community! It sounds like you’re encountering an issue with the “Plug n Play” SDK, specifically regarding a password recovery option in the TEA Protocol.

Unfortunately, as of now, Web3Auth doesn’t offer a direct password recovery feature because it is designed to be a passwordless login solution, emphasizing security and ease of use. The TEA Protocol may have its specific requirements or configurations that could be affecting your experience.

I recommend checking the Web3Auth Plug and Play documentation to ensure you’re aligning with its intended functionality: Web3Auth Plug and Play Documentation.

If the TEA Protocol needs to handle password recovery, you may need to reach out to them directly, as it may not be controlled by Web3Auth. If there’s any customization in your setup related to authentication, please provide further details, such as:

  • Any custom authentication setups?
  • Are there any errors in the console you can share?

This information will help us assist you better. In the meantime, if you have any more questions or if there’s something else you need help with, feel free to ask! :blush:

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

I understand but Web3Auth Plug and Play Documentation, I do not get the page and then what do you recommend me to do?

4

Hey @tecnorexpro03,

Thanks for sharing the screenshot — what you’re seeing is the MFA screen asking you to verify using one of the recovery options.

If you don’t have access to the original device, or didn’t set a recovery factor or password during initial setup, there’s unfortunately nothing we can do to recover your access. Web3Auth is non-custodial, which means we don’t store any part of your key or recovery data — even if we wanted to help, we technically can’t.

Also, for security reasons, we do not send the recovery phrase to the same email used for login, to prevent attackers from bypassing MFA if they gain access to your inbox.

If you found a recovery phrase in your login email inbox, it’s likely from a different dApp where that email was used as a fallback or alternate contact. It won’t work here unless the dApp was configured to associate it properly during your original login.

If you’re locked out of all the factors, the only option left is to create a new account using a new email or login method.

5