Archived Content from Web3Auth Community
This topic was originally posted by a.potapov on 1/23/2025.
This content has been migrated from our previous community forum to preserve valuable discussions.
When asking for help in this category, please make sure to provide the following details:
- SDK Version: “@toruslabs/customauth”: “^20.3.0”
- Platform: web
We have been using a CustomAuth-based approach since 2021, as shown below:
import { CustomAuth } from '@toruslabs/customauth'; ... const web3CustomAuth = new CustomAuth({ baseUrl: `${window.location.origin}/serviceworker`, enableLogging: false, network: 'mainnet', web3AuthClientId, });await web3CustomAuth.init({ skipSw: false });
const {
userInfo: { idToken },
oAuthKeyData: { privKey: privateKey },
} = await web3CustomAuth.triggerLogin({
clientId: googleClientId,
verifier: ‘smarty-pay-v1-prod’,
typeOfLogin: ‘google’,
jwtParams: {
scope: ‘email’,
prompt: ‘login’,
},
});
We recently noticed on our dashboard that our verifier is deployed on “Legacy Mainnet”, which appears outdated, and we also see 0 products selected error on the project details page. We have a few questions regarding this:
- Is it still safe or recommended to continue using “Legacy Mainnet,” or should we consider migrating to Sapphire Mainnet?
- If migration is required, is there an official or recommended guide to help us migrate safely from Legacy Mainnet to Sapphire Mainnet?
- How do we select the appropriate product(s) from the product list in our dashboard to ensure our configuration is correct?
- Is there a recommended approach or best practice for migrating our existing CustomAuth-based setup to a newer SDK? We’d also appreciate any insights into the pros and cons of making such a switch.
Thank you in advance for your assistance. We look forward to your guidance on next steps to ensure our setup remains secure and up to date.
