Secret Key changed?

Hello —

Our app is no longer working when you try to social login. I believe the issue the deprecated Torus package but I wanted to ask if the KEY is also changed?

I am not a dev – so forgive me if I don’t provide a detail you’d need to evaluate this.

-Adam

Hi Adam, thanks for reaching out and providing context!

Summary of your issue:

  • You’re using Web3Auth Plug n Play (PnP) for social login.
  • Your app’s social login is no longer working.
  • You suspect the issue is due to the deprecated Torus package.
  • You’re asking if your Web3Auth “key” (likely meaning your Client ID or secret key) has changed.

Clarification & Guidance:

  1. Key/Client ID Change:

    • Web3Auth does not automatically change your Client ID or secret key. You can always check your current Client ID in the Web3Auth Dashboard.
    • If you (or a teammate) did not manually change or regenerate your keys, they should remain the same.
  2. Deprecated Torus Package:

    • If your app is still using the old Torus packages or an outdated Web3Auth SDK (pre-v10), social login may break due to deprecation.
    • Web3Auth v10 and above have moved to a new architecture (MIPD) and require removing old adapter packages and updating your integration.
  3. Next Steps (for your dev team):

    • Check SDK Version: Make sure you are on the latest Web3Auth SDK (v10+).
    • Update Integration: Follow the v7 to v10 migration guide to update your code and dependencies.
    • Remove Deprecated Packages: Uninstall any old Torus or wallet adapter packages as per the guide.
    • Verify Client ID: Double-check your Client ID in the dashboard and ensure it matches what’s in your code.

If you need to share this with your developer:

  • Ask them to check the SDK version and update as needed.
  • Have them review the migration guide linked above.
  • If they encounter errors, please have them provide:
    • The SDK version in use
    • Platform (React, Vue, etc.)
    • Any error messages or browser console screenshots

Helpful Links:

If you need more help or if your developer has specific errors, let us know and we’ll guide you further!

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.

Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. Web3Auth Developer Office Hours