Hi - we have a Custom JWT Verifier login process that doesn’t use a login popup / modal (we pass our auth0 id_token directly upon triggerLogin), but we are now getting this error “Error occurred while verifying params verifier mural-auth0-tkey not found for account id: 5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY”. Nothing has changed about our implementation code but we are now starting to see this. Do you know why this might be occurring?
Code below:
const oidcLogin = async () => {
if (!tKey) {
console.log('tKey not initialized yet');
return;
}
// Initialization of Service Provider
try {
await (tKey.serviceProvider as any).init({ skipSw: true });
} catch (error) {
console.error(error);
}
try {
// Triggering Login using Service Provider
const claims = await getIdTokenClaims();
const idToken = claims?.__raw;
const jwtParams = {
id_token: idToken,
verifierIdField: 'sub',
};
const loginResponse = await (tKey.serviceProvider as any).triggerLogin({
typeOfLogin: 'jwt',
verifier: 'mural-auth0-tkey',
clientId: CLIENT_ID,
jwtParams: jwtParams,
});
setWeb3AuthUser(loginResponse.userInfo);
} catch (error) {
console.error('got an error when calling triggerLogin: ', error);
}
};
I’ve also double checked the configuration of that verifier to ensure it is correct. We updated the “iss” and JWK endpoint because we are now using a custom Auth0 domain, but everything looks good (confirming matches in data from the JWT).
Let me know if there is any other information I can provide or if you want to jump on a call to debug. This is currently blocking as we cannot retrieve / create any socials key shares.
Been digging in a little more here. I have two code branches now, and the social login works on one branch, but not the other (with the code between branches being nearly identical). One thing I notices is that on the branch that is working correctly, the torusNodeEndpoints are:
This version of the SDK looks like it uses the Sapphire network, which does not work properly with verifiers registered via the dashboard. Pinning to 7.2.0 (the latest non-alpha version) uses the teal network and works as expected. @shahbaz@tai.nguyen - is 8.0.0.alpha supposed to be the current latest version? Also what is the difference with the sapphire network?
v7.2.0 is the latest for tKey. 8.0.0-alpha is related to MPC SDK, and the team is testing it. Currently, it will have breaking changes, and it’s highly unstable at the moment.
Got it, thanks. You might want to update the latest version of the npm registry to not be 8.0.0.alpha so that people who don’t specify an install version don’t accidentally get the unstable version (which is what happened to us).
I agree. Reverting the SDK to v7.2.0 resolved the issue I had too (same issue with Sapphire network and verifier) after spending a couple of days on it. If the npm registry had the stable version instead of the unstable one, it would have saved a bunch of time.
I was in the same camp. +1 for pinning NPM to a stable release. Thanks to @chris for sharing his insights with us. I was feeling pretty lost, but now pinning back down to 7.2 has things working!
