# \[Archive\] Unable to login using newly created verifiers

**URL:** <https://builder.metamask.io/t/archive-unable-to-login-using-newly-created-verifiers/2026>\
**Category:** Embedded Wallets (Web3Auth)\
**Created:** [March 16, 2023, 6:07pm UTC](https://builder.metamask.io/t/archive-unable-to-login-using-newly-created-verifiers/2026 "2023-03-16T18:07:09Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![shayg](https://avatars.discourse-cdn.com/v4/letter/s/958977/32.png) [@shayg](https://builder.metamask.io/u/shayg)\
**Post date:** [March 16, 2023, 6:07pm UTC](https://builder.metamask.io/t/archive-unable-to-login-using-newly-created-verifiers/2026/1 "2023-03-16T18:07:09Z")

</div>

> **🏛 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:

```auto
    "@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):

```auto
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);

```

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.

---

<div class="post-metadata">

**Author:** ![shahbaz](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/shahbaz/32/1527_2.png) [@shahbaz](https://builder.metamask.io/u/shahbaz)\
**Post date:** [March 17, 2023, 3:44am UTC](https://builder.metamask.io/t/archive-unable-to-login-using-newly-created-verifiers/2026/2 "2023-03-17T03:44:44Z")

</div>

Hey @shayg

By looking at the verifier `grappa.xyz` details, I see that the verifier\_id\_feild is set to `sub`. Could you change that to `email`. Also, your other `verifier` is using `email` as the verifier\_id\_field.

Check out this video on how to do that.  
**Please note: to perform this action, you should have some testnet funds in your torus wallet account.**

---

<div class="post-metadata">

**Author:** ![shayg](https://avatars.discourse-cdn.com/v4/letter/s/958977/32.png) [@shayg](https://builder.metamask.io/u/shayg)\
**Post date:** [March 17, 2023, 7:10am UTC](https://builder.metamask.io/t/archive-unable-to-login-using-newly-created-verifiers/2026/3 "2023-03-17T07:10:27Z")

</div>

That would be weird then - what we see is all sub verifiers are set to email.  
Pardon me for not including a vid/image, but I checked that several times (even created a third verifier).

However, I did re-save it to rule out a bug caused during creation. That did not help. I can also see from the console that `subVerifierDetailsArray[].jwtParams.verifierIdField` is set to `email`

Also - we have the cyan verifier already set up so I assume it will suffer the same issue. **I can’t update the cyan network verifier** ([Updating a mainnet verifier](https://community.web3auth.io/t/updating-a-mainnet-verifier/2930))

---

<div class="post-metadata">

**Author:** ![shayg](https://avatars.discourse-cdn.com/v4/letter/s/958977/32.png) [@shayg](https://builder.metamask.io/u/shayg)\
**Post date:** [March 18, 2023, 7:42pm UTC](https://builder.metamask.io/t/archive-unable-to-login-using-newly-created-verifiers/2026/4 "2023-03-18T19:42:57Z")

</div>

Latest update is:

This morning we tried to use the `sub` as `verifiedIdField` in our code (even though we see the selected field as `email` in our dashboard) - and it worked.

That was around 12 hours ago, trying again now using `email` as `verifierIdField` - everything works on testnet (as we want it 🥳 for all 3 sub verifiers, generating the same address).

However - logging with `cyan` network doesn’t work at all for each of the sub verifiers. As mentioned above, I can’t see the details of the `cyan` network verifiers, let alone update them. From experience I know that if I try to delete the verifier, I won’t be able to recreate it.

The errors are:  
`linkedin` subverifier:

```auto
// no separator in address, i.e: auth0.com1234567
Error occurred while verifying paramsfailed to fetch remote JWK: Get https://.....auth0.com%AUTH0_CLIENT_ID%/.well-known/jwks.json

```

`twitter` subverifier: (looks like `verifierFieldId` is off here)

```auto
Error occurred while verifying paramscould not verify identity twitter|xxxxxx shayg@grappa.xyz

```

`google` subverifier: trying with `verifierFieldId` set to `sub` - I can verify that logging in works. This is the error when set to `email`

```auto
Error occurred while verifying paramscould not verify identity google-oauth2|xxxxxx shayg@grappa.xyz

```

At least it’s a step in the right direction, but as mentioned - we can’t update the `cyan` network verifier even if we wanted to.

Please advise

---

<div class="post-metadata">

**Author:** ![shahbaz](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/shahbaz/32/1527_2.png) [@shahbaz](https://builder.metamask.io/u/shahbaz)\
**Post date:** [March 20, 2023, 5:13am UTC](https://builder.metamask.io/t/archive-unable-to-login-using-newly-created-verifiers/2026/5 "2023-03-20T05:13:37Z")

</div>

> [@shayg](#):
>
> as we want it 🥳 for all 3 sub verifiers, generating the same address)

Thank you for confirming.

> [@shayg](#):
>
> The errors are:  
> `linkedin` subverifier:
> 
> ```auto
> // no separator in address, i.e: auth0.com1234567
> Error occurred while verifying paramsfailed to fetch remote JWK: Get https://.....auth0.com%AUTH0_CLIENT_ID%/.well-known/jwks.json
> 
> ```
> 
> `twitter` subverifier: (looks like `verifierFieldId` is off here)
> 
> ```auto
> Error occurred while verifying paramscould not verify identity twitter|xxxxxx shayg@grappa.xyz
> 
> ```
> 
> `google` subverifier: trying with `verifierFieldId` set to `sub` - I can verify that logging in works. This is the error when set to `email`
> 
> ```auto
> Error occurred while verifying paramscould not verify identity google-oauth2|xxxxxx shayg@grappa.xyz
> 
> ```

Looking at this, it is using `sub` as `verifierIdField`.

What’s the name of the cyan verifier? @shayg

---

<div class="post-metadata">

**Author:** ![shayg](https://avatars.discourse-cdn.com/v4/letter/s/958977/32.png) [@shayg](https://builder.metamask.io/u/shayg)\
**Post date:** [March 20, 2023, 6:38am UTC](https://builder.metamask.io/t/archive-unable-to-login-using-newly-created-verifiers/2026/6 "2023-03-20T06:38:12Z")

</div>

@shahbaz  
The name is `grappa.xyz` as well, I actually created another set of verifiers called `grappa-social-login` and experienced the same; during creation the `email` field is selected (and then displayed) but the actual field used is `sub`.

It seems there are 4 issues:

- Editing `testnet` verifiers has no effect
- Verifiers display wrong `verifierIdField`
- it is not possible to view or edit `cyan` network verifiers
- If deleted, verifiers with the same name cannot be re-created

---

<div class="post-metadata">

**Author:** ![shahbaz](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/shahbaz/32/1527_2.png) [@shahbaz](https://builder.metamask.io/u/shahbaz)\
**Post date:** [March 20, 2023, 8:35am UTC](https://builder.metamask.io/t/archive-unable-to-login-using-newly-created-verifiers/2026/7 "2023-03-20T08:35:14Z")

</div>

Hey @shayg

I have reported this to the product team. Will keep you posted on the updates.

---

<div class="post-metadata">

**Author:** ![shayg](https://avatars.discourse-cdn.com/v4/letter/s/958977/32.png) [@shayg](https://builder.metamask.io/u/shayg)\
**Post date:** [March 20, 2023, 9:02am UTC](https://builder.metamask.io/t/archive-unable-to-login-using-newly-created-verifiers/2026/8 "2023-03-20T09:02:42Z")

</div>

@shahbaz is it possible to help us with updating our cyan verifier manually? We keep pushing our timelines back because of this

---

<div class="post-metadata">

**Author:** ![shahbaz](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/shahbaz/32/1527_2.png) [@shahbaz](https://builder.metamask.io/u/shahbaz)\
**Post date:** [March 20, 2023, 4:56pm UTC](https://builder.metamask.io/t/archive-unable-to-login-using-newly-created-verifiers/2026/9 "2023-03-20T16:56:56Z")

</div>

Hey @shayg

We have updated our aggregate verifier creation process. Now you can select the verifier ID field while creating a sub-verifier. Please follow the [https://web3auth.io/docs/auth-provider-setup/aggregate-verifier](https://web3auth.io/docs/auth-provider-setup/aggregate-verifier) documentation page to create your new verifier.

Updating a mainnet verifier is not possible at the moment. **I will recommend creating a new verifier for now.**

---

<div class="post-metadata">

**Author:** ![shayg](https://avatars.discourse-cdn.com/v4/letter/s/958977/32.png) [@shayg](https://builder.metamask.io/u/shayg)\
**Post date:** [March 21, 2023, 1:32pm UTC](https://builder.metamask.io/t/archive-unable-to-login-using-newly-created-verifiers/2026/10 "2023-03-21T13:32:44Z")

</div>

@shahbaz that seems to have solved it, I can see the change made to the verifier creation modal too.

Will it be possible to update those verifiers in the future?

---

<div class="post-metadata">

**Author:** ![shahbaz](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/shahbaz/32/1527_2.png) [@shahbaz](https://builder.metamask.io/u/shahbaz)\
**Post date:** [March 21, 2023, 1:50pm UTC](https://builder.metamask.io/t/archive-unable-to-login-using-newly-created-verifiers/2026/11 "2023-03-21T13:50:58Z")

</div>

Glad it worked!

Editing mainnet verifiers are currently not possible. Let me share this with the product team and get back to you.

---

<div class="post-metadata">

**Author:** ![shayg](https://avatars.discourse-cdn.com/v4/letter/s/958977/32.png) [@shayg](https://builder.metamask.io/u/shayg)\
**Post date:** [March 21, 2023, 2:42pm UTC](https://builder.metamask.io/t/archive-unable-to-login-using-newly-created-verifiers/2026/12 "2023-03-21T14:42:27Z")

</div>

@shahbaz If there’s anything we can do to help (including meeting up with the product team for feedback) we’d be happy to help