[Archive] Migrating from PnP social login(google) to Single factor auth using firebase

Embedded Wallets (Web3Auth)
1

:classical_building: Archived Content from Web3Auth Community

This topic was originally posted by vishnu.rk on 5/23/2023.
This content has been migrated from our previous community forum to preserve valuable discussions.

  • SDK Version: “@web3auth/single-factor-auth”: “^6.0.0”

Is it possible to get the same wallet created using PnP social login(verifier A - open login) if we start using single factor auth(verifier B - using firebase as jwt provider) from now on?

The wallet addresses didn’t match in the above case.

I also tried using the old verifier name(verifier A) and passed the idToken from firebase authentication, but it threw an error saying

Unhandled Runtime Error

Error: Error occurred while verifying paramsCould not get timesignedint from

Call Stack

eval


node_modules/@toruslabs/customauth/node_modules/@toruslabs/torus.js/dist/torusUtils.esm.js (78:0)

For SFA to work alongside the old login method, what should be done?

2

Hello @vishnu.rk,

In order to provide you with the best assistance possible, could you kindly provide the following information:

  • Is Verifier A a custom verifier or is it provided with @web3auth/modal?
3

Hey @shahbaz, it’s not a custom verifier. Btw the issue got solved, we were referring the article on SFA using firebase authentication for the migration(Using Web3Auth without MFA with future compatibility | Web3Auth). We figured out now that the verifier has to be the same(that you don’t need to create a new verifier) and idToken issued by firebase would not work for the old verifier