Legacy Mainnet Verifier & Migration to Sapphire Mainnet for CustomAuth

[a.potapov]

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:

1. Is it still safe or recommended to continue using “Legacy Mainnet,” or should we consider migrating to Sapphire Mainnet?
2. If migration is required, is there an official or recommended guide to help us migrate safely from Legacy Mainnet to Sapphire Mainnet?
3. How do we select the appropriate product(s) from the product list in our dashboard to ensure our configuration is correct?
4. 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.

[w3abot]

Hello Aleksey Potapov,

Thank you for reaching out with your questions regarding migrating from Legacy Mainnet to Sapphire Mainnet for your CustomAuth setup. I’ll provide some guidance on the actions you can take:

1. Safety of Using Legacy Mainnet: It is generally recommended to migrate to newer platforms, like Sapphire Mainnet, as they offer better support, security, and features. Staying on outdated infrastructure might lead to vulnerabilities and compatibility issues in the future.

2. Migration Guide: While I don’t have a direct link, I would recommend checking Web3Auth’s official documentation or their GitHub repository for any migration guides. Also, contacting Web3Auth support directly for a step-by-step migration guide would be a good approach.

3. Selecting Products: In your Web3Auth dashboard, there should be an option under project settings to select products. Ensure that the necessary products you’re using as part of your integration are selected. If you’re unsure, Web3Auth support can clarify any required configurations.

4. Migrating Existing CustomAuth Setup: When considering migration, keep these points in mind:

   • Pros: Improved security, better support for newer features, and enhancements in performance and stability.
   • Cons: Initial setup time and testing the migration thoroughly to ensure no disruption in service.
   • Best practice would be to set up a testing environment where you perform the migration and test all functionalities before doing so in the production environment.

Here is a reminder of the details of your setup, should you need to discuss this with Web3Auth support:

• SDK Version: “@toruslabs/customauth”: “^20.3.0”
• Platform: Web
• Verifier: ‘smarty-pay-v1-prod’
• Method of Login: Google

I hope this helps, and please feel free to reach out if you have any more questions!

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.

[a.potapov]

Hi! Could you please confirm if we can safely remain on Legacy Mainnet without taking any additional steps right now? Also, since the settings form requires us to select a product, which one should we choose for our CustomAuth setup?

[shahbaz]

Hey @a.potapov

@a.potapov

Is it still safe or recommended to continue using “Legacy Mainnet,” or should we consider migrating to Sapphire Mainnet?

Yes, it’s safe to continue using the same project on Legacy Mainnet.

@a.potapov

How do we select the appropriate product(s) from the product list in our dashboard to ensure our configuration is correct?

Please share the screenshot of your dashboard with that error. I will ask the team to take a look at this.

@a.potapov

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.

No migration is needed, unless you want to try our newer SDK, let me know, i will help with the necessary steps.

[a.potapov]

Please share the screenshot of your dashboard with that error. I will ask the team to take a look at this.

[shahbaz]

Hey @a.potapov

Can you confirm which pricing plan it is showing you on your dashboard?
Also, does your dashboard have any card attached to it?
And what happens when you select a product and try to sav ite?