Response: 403 Forbidden

[irfan]

It was normally working as expected and returning wallet provider and signer. But suddenly give error and signer could be created.

url: diplomade preview
Platform: web
Project Name: diplomade-test
Verifier Name: diplomade-root-dev
sampleEmail:irfankemal16@gmail.com
idtoken: eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJlbWFpbCI6ImlyZmFua2VtYWwxNkBnbWFpbC5jb20iLCJwdWJsaWNBZGRyZXNzIjoiMHg4ODFmNzdmRWFFNUZCOWVkODlFNUVmYUZCNmZkNjNkNjIzMDcyZDRCIiwidmFsaWQiOnRydWUsImVtYWlsSE1BQ0ZvckludGVyY29tIjoiNzBlZmU2NzM2MWFiNThjOTc2YTJjMGI1NTMwYzhmNjFkMDUyZTZiMmE4MTJjNDc2N2RiZjE4NjAzY2Q0ODBlNSIsImlhdCI6MTczMzMyMjIwNiwiZXhwIjoxNzMzMzI1ODA2LCJhdWQiOiJodHRwczovL2FwcC5kaXBsb21hZGUuY29tIiwiaXNzIjoiaHR0cHM6Ly9hcGkuZGlwbG9tYWRlLmNvbSIsInN1YiI6ImlyZmFua2VtYWwxNkBnbWFpbC5jb20ifQ.VC_6yvTcDTHG8QnWOdgaiG9xHcGN1WQ1I8de4NNnjSbBpGdzqeNKRp8IDb7ZudcxamGBjj69OLwmwyvgOn1MMQjF0I6fjx7gZumOvSetcqWlnVssE0nNVP66bCqYnJCIVipj3E7PFBjWcMg2D3dTvgIluj1_nY95OT_Ijd4zRt9YVGaEptiw3dAVjx0AngvImlvmkeJC5qapUhQFhhBfXFVGa1qUh-YkZlmo7OoDf3FTtEpaNwLeVl2YlBrlE_YVXkTzvCgCInAWecmq1zxKlZPgtzi-eHU9RufuIjN7NWT1Y6HRyZxcPDezwZXXEOhhWcsOO31_jrAQyC_WTM1Fcg

But “No verifiers found” says when i visit the dashboard.

packages:

    "react": "^18.2.0",
    "@tkey/default": "^7.3.0",
    "@tkey/security-questions": "^7.2.0",
    "@tkey/web-storage": "^7.2.0",
    "@web3auth/base": "^5.1.0",
    "@web3auth/ethereum-provider": "^4.3.0",
    "@web3auth/single-factor-auth": "^4.3.0",

Configuration and Instantiation of tKey:

import ThresholdKey from '@tkey/default';
import WebStorageModule from '@tkey/web-storage';

// Configuration of Service Provider
const customAuthArgs = {
  baseUrl: `${window.location.origin}/serviceworker`,
  network: 'cyan'
};
// Configuration of Modules
const webStorageModule = new WebStorageModule();

// Instantiation of tKey
export const tKey = new ThresholdKey({
  modules: {
    webStorage: webStorageModule
  },
  customAuthArgs: customAuthArgs as any
});

init:

    const init = async () => {
      // Initialization of Service Provider
      try {
        await (tKey.serviceProvider as any).init();
        setIsInitialized(true);
        checkLogin();

      } catch (error) {
        console.error(error);
      }
    };
    init();

usage:

      const customSubVerifierDetails = {
        typeOfLogin: 'jwt',
        verifier: ENV.WEB3AUTH_SUB_VERIFIER_SELF,
        clientId: clientId,
        jwtParams: {
          id_token: idToken,
          verifierIdField: 'email'
        }
      };
      const registerResponse = await (
        tKey.serviceProvider as any
      ).triggerAggregateLogin({
        aggregateVerifierType: 'single_id_verifier',
        verifierIdentifier: ENV.WEB3AUTH_VERIFIER,
        subVerifierDetailsArray: [customSubVerifierDetails]
      });

[w3abot]

Hi İrfan,

Thank you for sharing the details about your issue with the Single Factor Auth Web SDK. Let’s summarize the information for the support team:

Issue Summary:

• SDK Details: Single Factor Auth Web SDK
• SDK Version:
  • @tkey/default: ^7.3.0
  • @tkey/security-questions: ^7.2.0
  • @tkey/web-storage: ^7.2.0
  • @web3auth/base: ^5.1.0
  • @web3auth/ethereum-provider: ^4.3.0
  • @web3auth/single-factor-auth: ^4.3.0
• Platform: Not explicitly mentioned (please confirm if needed).
• Error Response: 403 Forbidden
• Details:
  • The app was working correctly but suddenly started returning an error. The signer could not be created.
  • Console log details/screenshots attached:
    
  • Verifier Name: diplomade-prod-root
  • Dashboard status: “No verifiers found”
    
    

Code Snippets Provided:

1. Initialization and configuration of the service provider.
2. TKey instantiation.
3. Error-handling during initialization.
4. Custom Sub Verifier details for triggering an aggregate login.

Could you please confirm the platform you are using? This will help us provide a more targeted support response.

Meanwhile, it’s worth checking if there have been any changes or updates on the dashboard that may have affected your verifiers. Sometimes re-adding the verifier can resolve such issues.

Looking forward to your response!

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.

[irfan]

hey. it is urgent. please take a look

[shannon]

I’m also experiencing the same thing, but I’m on the old deprecated @web3auth/node-sdk

[irfan]

this is the warning i got with current package version:

{
    "code": 1001,
    "error": "Invalid Web3Auth client id, You're using a very old version. Please upgrade to latest. Obtain a client ID at https://dashboard.web3auth.io",
    "success": false
}

and this is what i got after upgrade your packages:

{
    "code": 1003,
    "error": "The current subscription plan is Base and accessing custom authentication feature is not allowed on Base plan. Please upgrade to Growth or above plan at https://dashboard.web3auth.io to use this feature",
    "success": false
}

Until recently, the custom authentication feature was supported under your base plan, which is a critical component of my app’s functionality.

Without any prior communication or notice, I discovered through API responses that custom authentication is no longer supported in the base plan. This abrupt change has caused my application to crash, resulting in disruption to my users and significant downtime for my service.

As a customer, I find this lack of transparency highly unprofessional and detrimental to our partnership. Changes of such magnitude must be communicated well in advance, allowing developers to make necessary adjustments to avoid service interruptions.