I have a aggregate verifier setup with verifier ID field “email”, the google sign here seems to be working but the openlogin isn’t able to construct a key
I also have a verifier with login provider as “custom” instead of "aggregate just for testing purpose and it seems to be constructing the keys but doesn’t seem to be providing a user info once logged in
Can you share a sample idToken here? Because looking at your verifiers, I see a space in the iss value of the JWT validation.
Also, why have you just used jwt in the loginConfig and not the other, like google to aggregate between?
const web3auth = new Web3Auth(WebBrowser, {
clientId,
network: OPENLOGIN_NETWORK.TESTNET, // or other networks
loginConfig: {
google: {
verifier: "agg-google-emailpswd-github",
verifierSubIdentifier: "w3a-google",
typeOfLogin: "google",
clientId:
"774338308167-q463s7kpvja16l4l0kko3nb925ikds2p.apps.googleusercontent.com",
},
auth0github: {
verifier: "agg-google-emailpswd-github",
verifierSubIdentifier: "w3a-github",
typeOfLogin: "jwt",
clientId: "TcuxIlWeaexIhVzsyc4sShzHJxwJ7nsO",
jwtParameters: {
domain: "https://shahbaz-torus.us.auth0.com",
// this corresponds to the field inside jwt which must be used to uniquely
// identify the user. This is mapped b/w google and github logins
verifierIdField: "email",
isVerifierIdCaseSensitive: false,
},
},
},
});
This guide has documented the config for custom auth so I tried to do the same for aggregate verifier but it didn’t seem to work, will share the idToken in a few mins here