[Archive] Different wallets from (Google SSO) and (torus Google SSO)

Embedded Wallets (Web3Auth)
1

:classical_building: Archived Content from Web3Auth Community

This topic was originally posted by githubdiscussions on 9/20/2022.
This content has been migrated from our previous community forum to preserve valuable discussions.

Hello,
We are struggling to get Web3Auth to behave the way we “think” it should. Can you help us?

What we want is:

  1. Login to Web3Auth with Google SSO (Identity 1), and get Wallet (1).
  2. Login to Web3Auth with "Connect Wallet” + Google SSO (Identity 1) and get Wallet (1).

What we are experiencing is:

Scenario 1:

  1. In the config we enable “Allow user’s private keys usage in given wallet”.
  2. We login directly with Web3Auth / Google SSO (Identity 1). We get a Wallet (1).
  3. We login with the “Connect Wallet” option, Select Torus, and the Google SSO (Identity 1).
    We get a prompt to login with either:
  • Wallet (1)
  • Wallet (SiteWallet) an Application specific Wallet for our website site

Scenario 2:

  1. In the config we disable “Allow user’s private keys usage in given wallet”.
  2. We login directly with Web3Auth / Google SSO (Identity 1). We get a Wallet (1).
  3. We login with the “Connect Wallet” option, Select Torus, and the Google SSO (Identity 1). We get Wallet (2).


Originally posted by: softcheetah

Check the discussion at: https://github.com/orgs/Web3Auth/discussions/624
2

Hey, In scenario 1, you can achieve what you desire. The prompt is always there after login if you have dapp scoped priv keys.
For scenario 2, You get wallet1 in first case and wallet2 in second because the verifiers which are used at the backend are different and they will generated different priv keys and wallets for same social login if Allow user’s private keys usage in given wallet” is disabled.



Originally posted by: rinzler99