When first running some tests with the web3auth plug’n’play framework I still had MFA enabled and signed up through a Social login on my desktop browser. I later turned MFA off.
Now when I wanna run some tests from my phone it asks me to verify my login either through a recovery code or by visiting auth.web3auth.io in my authenticated browser.
However, when trying to follow this step in the desktop browser the page stays empty and I am getting the following errors in the console.
I didn’t write down my recovery code because I didn’t intend to have any MFA activated. But now even with MFA disabled it prompts me to complete these steps because I created this account with MFA enabled.
Could you please help figure out how I can gain access in this case? Like I said my desktop browser is still authenticated and I can login properly there, so it should be possible to verify my mobile login through it?
Thanks for your answer. I understand that this is not possible. However, the auth interface says I can verify my mobile device by logging in via my other device and granting access (see screenshot)
However, when I visit this page on my authenticated desktop Firefox I just see an empty page. I would really appreciate some assistance in this regard because I need to verify my mobile device for on-device testing.
This is not working. @TomTom
I am still locked out on my mobile. Following your url just leads me to a site where I can see authorize apps or assign 2FA factors, however, when I try these on my mobile they don’t work.
Can you please tell me why it’s not working as indicated on your UI. Following that I should be able to approve my mobile device by following auth.web3auth.io
I don’t understand why it’s so complex to simply approve my mobile device when I am successfully logged in on desktop and it’s really starting to become frustrating.
This particular feature is still not available in the Sapphire networks, the feature you’re looking to was available in our legacy networks, where app.openlogin.com is where someone can login and authenticate their device from another device where they had previously logged in.
The Auth Dashboard ie. auth.web3auth.io is still not out and we’re working towards rolling it out as soon as possible. In the meantime, you can verify using other factors you had created while enabling MFA for your account, similar to how you might login to another website and put in the second factor to get access.
Just click on “Verify with other factors” and put in whatever factor you created while enabling MFA.
I trust all is going great on your end. Just touching base to see how you got on with the solution provided by @yashovardhan. Has it worked out for you? If it has, we can consider this thread resolved. But if you’re still facing hurdles, feel free to share - we’re all ears and ready to assist!
No, unfortunately this did not resolve my issue. I don’t have another recovery factor available as I explained before. This happened because I assumed that I was just testing the set up. I did not anticipate that my login stays congruent across testing phases.
Your method to approve my login through the authenticated device is definitely dysfunctional and not working as indicated here
When visiting auth.web3auth.io from my approved device I see a blank page. Could you please fix this on your end and make the recovery option available from this page?
