Archived Content from Web3Auth Community
This topic was originally posted by shayg on 3/16/2023.
This content has been migrated from our previous community forum to preserve valuable discussions.
We are using @web3auth/core to trigger a login using our own modal, using an aggregate verifier with auth0 for social providers login.
We are using the latest SDK and adapters (getting the same results for the core and no-modal package:
"@web3auth/base": "4.6.0",
"@web3auth/core": "4.6.0",
"@web3auth/no-modal": "^5.0.1",
"@web3auth/openlogin-adapter": "5.0.1",
Our implementation is as follows (simplified for readability):
const openloginAdapter = new OpenloginAdapter({ clientId: process.env.NEXT_PUBLIC_WEB3_AUTH_CLIENT_ID || '', adapterSettings: { uxMode: 'redirect', loginConfig: { google: { name: 'google', typeOfLogin: 'jwt', verifier: 'grappa.xyz', verifierSubIdentifier: 'google', clientId: auth0ClientId, jwtParameters: { domain: auth0Domain, connection: 'google-oauth2', isVerifierIdCaseSensitive: false, }, },twitter: { name: 'twitter', typeOfLogin: 'jwt', verifier: 'grappa.xyz', verifierSubIdentifier: 'twitter', clientId: auth0ClientId, jwtParameters: { domain: auth0Domain, isVerifierIdCaseSensitive: false, }, }, linkedin: { name: 'linkedin', typeOfLogin: 'jwt', verifier: 'grappa.xyz', verifierSubIdentifier: 'linkedin', clientId: auth0ClientId, jwtParameters: { domain: auth0Domain, isVerifierIdCaseSensitive: false, }, }, }, },});
const web3Auth = new Web3AuthCore({
clientId: process.env.NEXT_PUBLIC_WEB3_AUTH_CLIENT_ID || ‘’,
web3AuthNetwork: ‘testnet’,
chainConfig: {
chainNamespace: CHAIN_NAMESPACES.EIP155,
chainId: ‘0x64’,
rpcTarget: process.env.NEXT_PUBLIC_WEB3_AUTH_RPC_TARGET,
displayName: ‘Gnosis Mainnet’,
blockExplorer: ‘https://gnosisscan.io’,
ticker: ‘xDai’,
tickerName: ‘xDai’,
},
});web3Auth.configureAdapter(openloginAdapter);
await web3Auth.connectTo(WALLET_ADAPTERS.OPENLOGIN, {
loginProvider: ‘google’,
sessionTime: ONE_WEEK,
mfaLevel: ‘none’,
extraLoginOptions: {
domain: auth0Domain,
verifierIdField: ‘email’,
},
})
Until now we have used a verifier named grappa without any issues. In preparation for our production deployment we’ve created new verifiers. The testnet verifiers are identical (grappa.xyz and grappa) and point to the same auth0 account.
Running the same local code, and performing one single change (changing the verifier we use) - we are able to login using grappa verifier, and unable to login at all using the other one.
The error we are getting is Could not get result from torus nodes Error occurred while verifying paramscould not verify identity. Failing on invoking the ShareRequest method on each of the 5 torus nodes.
Please advise, this is not even our production deployment and we are already encountering issues.
for all 3 sub verifiers, generating the same address).