Issue with Web3Auth MPC Core Kit using Auth0 verifier with verifierIdField as sub

Help - Core-Kit MPC Core Kit
,
1

I’ve encountered an issue while implementing the Web3Auth MPC Core Kit with the Auth0 verifier.

Setup:

I followed the documentation to set up the Auth0 verifier with verifierIdField set to sub. In my code, the verifier is configured as follows:

{
  typeOfLogin: LOGIN.JWT,
  verifier: 'google-verifier',
  clientId: 'my-auth0-client-id',
  jwtParams: {
    domain: 'https://example.eu.auth0.com',
    connection: 'google-oauth2',
    verifierIdField: 'sub',
    scope: 'read:current_user openid profile email',
  },
}

Issue:

Logging in works seamlessly. However, when I attempt to send a transaction, it fails during the precompute step, returning the error:
"Invalid verifierID found in session data, failed to authorize, expected: google-oauth2|101515641884063852395 found google-oauth2"

This error seems related to the sub field.

Additional Information:

  1. The standard Google verifier operates without any issues.
  2. Other Auth0 verifiers (e.g., apple) produce the same error.
  3. Switching verifierIdField to ‘email’ instead of ‘sub’ for both Google and Apple Auth0 verifiers works, but we want to retain sub as the verifierId instead of the email.
  4. The verifierId in the session data stored on the app appears correct (confirmed via debugging), and the login process seems unaffected. The error only arises during the precompute step while signing a transaction.

Any guidance on resolving this would be highly appreciated!

2

@narklm Welcome Aboard!

Your request has been forwarded to our Dev team and we will get back with updates.

3

hello @narklm
can you tell me which documentation you followed?

Also, can you try follow the example application’s guide?

the flow is like this:

  1. get the idToken
  2. parse the token
  3. fill out the verifierIDField with parsedToken.sub
4

Your suggestion doesnt exactly fit our needs.
We’ve been testing and the problem remains, we think its a problem on your side as it grabs all the signatures, and process all the steps correctly until the precompute step when signing a transaction. The login works flawlesly aswell but the session cannot sign transactions which is essential in our app.

5

@narklm Apologies for the delay.

I have forwarded your feedback to our Dev team and we will get back with further updates.