# \[Archive\] Verifier not supported error **URL:** \ **Category:** Embedded Wallets (Web3Auth)\ **Created:** [September 21, 2023, 9:24am UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774 "2023-09-21T09:24:05Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![taaaaho](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/taaaaho/32/302_2.png) [@taaaaho](https://builder.metamask.io/u/taaaaho)\ **Post date:** [September 21, 2023, 9:24am UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/1 "2023-09-21T09:24:05Z")
> **🏛 Archived Content from Web3Auth Community** > > This topic was originally posted by **taaaaho** on 9/21/2023. > This content has been migrated from our previous community forum to preserve valuable discussions. * * * I had previously implemented SFA with Custom Auth and it was working fine. When I created a new Custom Verifier on the new Dashboard, the new Verifier did not pass authentication and gave me an error. Error: Verifier not supported When I had a similar error before, it was due to a different web3AuthNetwork in the new Web3Auth parameter, so I am wondering if this is the cause of the error again. At first, I was able to create it with mainnet, but from the middle of the process, I was only able to select Aqua, and this time it is Sapphire. Does anyone have any idea what the cause might be? **Please provide the following details too when asking for help in this category:** - SDK Version: 7.0.1 - Verifier Details: - Verifier Name: p-0001 - JWKS Endpoint: [https://api.line.me/oauth2/v2.1/certs](https://api.line.me/oauth2/v2.1/certs) - Sample idToken(JWT): paste decoded information because JWT include my personal profile. { “iss”: “[https://access.line.me](https://access.line.me)”, “sub”: “U5e8175906325241eb3001d2b159742b4”, “aud”: “2000310947”, “exp”: 1695291362, “iat”: 1695287762, “amr”: [ “linesso” ] } ---
**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\ **Post date:** [September 21, 2023, 12:05pm UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/2 "2023-09-21T12:05:51Z")
@taaaaho Thanks for your patience. Did you create the verifier from the same organization from your Dashboard? Is the verifier linked to same project? ---
**Author:** ![taaaaho](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/taaaaho/32/302_2.png) [@taaaaho](https://builder.metamask.io/u/taaaaho)\ **Post date:** [September 21, 2023, 12:16pm UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/3 "2023-09-21T12:16:57Z")
Yes. I created a new Project, where I also created a Custom Verifier. One thing I am wondering is that the Env is set to `Sapphire Devnet`, does web3AuthNetwork work with testnet when initializing Web3Auth? ```auto const web3auth = new Web3Auth({ clientId: process.env.NEXT_PUBLIC_WEB3AUTH_CLIENT_ID as string, web3AuthNetwork: 'testnet', enableLogging: true, usePnPKey: false, }) ``` This is a confirmation of a similar error I had before, where the specification here was different. ---
**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\ **Post date:** [September 21, 2023, 12:23pm UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/4 "2023-09-21T12:23:08Z")
The web3AuthNetwork should be `'sapphire_devnet' ` ![](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/1X/4bea15d5fdfd372b2e7fae21263c61fab3da9379.png) ``` web3auth.io ``` ### [Different Private Keys/ Wallet Address across Integrations | Documentation |...](https://web3auth.io/docs/troubleshooting/different-private-key#environment) Different Private Keys across Integrations | Documentation - Web3Auth ---
**Author:** ![taaaaho](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/taaaaho/32/302_2.png) [@taaaaho](https://builder.metamask.io/u/taaaaho)\ **Post date:** [September 21, 2023, 12:41pm UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/5 "2023-09-21T12:41:01Z")
Thank you very much. When I fixed that, I got another error the next time. Custom. Unable to get private key from torus nodes. ---
**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\ **Post date:** [September 21, 2023, 12:48pm UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/6 "2023-09-21T12:48:31Z")
> [@vjgee](#): > > sapphire\_devnet Are you able to crate the verifier with environment as ‘Testnet’ instead of sapphire\_devnet and the web3AuthNetwork to the same to check the behavior? ---
**Author:** ![taaaaho](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/taaaaho/32/302_2.png) [@taaaaho](https://builder.metamask.io/u/taaaaho)\ **Post date:** [September 21, 2023, 12:51pm UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/7 "2023-09-21T12:51:14Z")
you mean testnet is `Legacy Testnet` ? I’l try. ---
**Author:** ![taaaaho](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/taaaaho/32/302_2.png) [@taaaaho](https://builder.metamask.io/u/taaaaho)\ **Post date:** [September 21, 2023, 1:02pm UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/8 "2023-09-21T13:02:22Z")
I created a project with Legacy Testnet and Verifier and checked it. The result is the same as sapphire\_devnet. In case of web3AuthNetwork: ‘sapphire\_devnet’, Verifier not supported error is displayed, and in case of web3AuthNetwork: ‘testnet’, wallet generation itself works fine. The error seems to be in the part of my application where the private key is retrieved after the wallet is generated, but I wonder if the method of retrieving the private key has changed. ---
**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\ **Post date:** [September 21, 2023, 1:08pm UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/9 "2023-09-21T13:08:29Z")
If the user has not enabled MFA, we use the `@web3auth/single-factor-auth` sdk to retrieve the private key shares from the Web3Auth auth network nodes and reconstruct the private key. ![](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/1X/4bea15d5fdfd372b2e7fae21263c61fab3da9379.png) ``` Web3Auth ``` ![](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/5/55d95253edc84065d7e7429de7d89e353b2d2944.png) ### [Using Web3Auth without MFA with future compatibility](https://web3auth.io/docs/content-hub/guides/single-factor-auth) Learn how to customize the authentication flow to allow users to authenticate without redirecting to the openlogin hosted screens. ---
**Author:** ![taaaaho](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/taaaaho/32/302_2.png) [@taaaaho](https://builder.metamask.io/u/taaaaho)\ **Post date:** [September 21, 2023, 1:20pm UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/10 "2023-09-21T13:20:29Z")
My account is not MFA enabled, but it doesn’t seem to work. I stated earlier that the wallet was created, but it seems to be an error in the connect portion of the process. Is there any other perspective to check? ```auto const web3authProvider = await web3auth.connect({ verifier: verifier, verifierId: sub, idToken: idToken! }) ``` ---
**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\ **Post date:** [September 21, 2023, 1:45pm UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/11 "2023-09-21T13:45:54Z")
> [@taaaaho](#): > > ```auto > const web3authProvider = await web3auth.connect({ > verifier: verifier, > verifierId: sub, > idToken: > > ``` What is the response you receive? Is there any error? Can you share console logs? ---
**Author:** ![taaaaho](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/taaaaho/32/302_2.png) [@taaaaho](https://builder.metamask.io/u/taaaaho)\ **Post date:** [September 21, 2023, 3:10pm UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/12 "2023-09-21T15:10:14Z")
Error occured, and message is `Custom. Unable to get private key from torus nodes.` ---
**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\ **Post date:** [September 21, 2023, 5:54pm UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/13 "2023-09-21T17:54:23Z")
I have forwarded your issue to our Dev team and we will get back further updates. ---
**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\ **Post date:** [September 22, 2023, 3:05am UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/14 "2023-09-22T03:05:17Z")
It is possible that you might be using different client id. So, testnet verifier should use testnet project id and same for all network ---
**Author:** ![taaaaho](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/taaaaho/32/302_2.png) [@taaaaho](https://builder.metamask.io/u/taaaaho)\ **Post date:** [September 22, 2023, 9:49am UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/15 "2023-09-22T09:49:11Z")
> [@vjgee](#): > > t is possible that you might be using different client id. > > So, testnet verifier should use testnet project id and same for all network I use this project client id and custom authentication. so I think project and network is correct. [![image](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/4/4c47f2fb438ca17829fa738900154b44c51f44eb.png) image2438×816 74.8 KB ](https://web3auth.io/community/uploads/default/original/2X/d/de1782c8c51ab0eb30ec251428688dfebb7ea64d.png "image") [![image](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/2/29a1f860c0a782640f929366092821ff1cb04893.png) image1846×904 63.9 KB ](https://web3auth.io/community/uploads/default/original/2X/5/51df23b11a0d63d510a3a011dcdc8759d6de2b3a.png "image") ---
**Author:** ![taaaaho](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/taaaaho/32/302_2.png) [@taaaaho](https://builder.metamask.io/u/taaaaho)\ **Post date:** [September 22, 2023, 9:53am UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/16 "2023-09-22T09:53:44Z")
@vjgee I send you error logs. [![image](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/5/54a289d273cca06880d59c3b5bcbbfaebf06dac4.jpeg) image980×194 58.3 KB ](https://web3auth.io/community/uploads/default/original/2X/1/134b24ca030e8a3b423297a71fb9ce822198913a.jpeg "image") ---
**Author:** ![taaaaho](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/taaaaho/32/302_2.png) [@taaaaho](https://builder.metamask.io/u/taaaaho)\ **Post date:** [September 23, 2023, 9:51am UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/17 "2023-09-23T09:51:38Z")
@vjgee Additional Information Looking at the contents of the log in the above capture (presumably the log produced by Lib), it seems that privkey corresponds to the private key, and I was able to actually load the wallet by importing this one. Therefore, it seems that torus is able to generate the pkey, but an error is occurring when it gets the pkey to the web3auth side. [![image](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/5/504e8311c6dc26dcff6c62615ed65d04b154f357.png) image2230×830 127 KB ](https://web3auth.io/community/uploads/default/original/2X/2/27af9b02bf697234736ff783edc69f701891f278.png "image") ---
**Author:** ![maharshi](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/maharshi/32/1525_2.png) [@maharshi](https://builder.metamask.io/u/maharshi)\ **Post date:** [September 25, 2023, 2:33pm UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/18 "2023-09-25T14:33:45Z")
Hi @taaaaho, could you please create a new custom verifier using [this](https://web3auth.io/docs/auth-provider-setup/byo-jwt-providers) guide. This has been our go-to guide which has solved a lot of issues with custom verifiers. Please don’t forget to change the client id if you create the verifier with another project. And also the network you’re creating the verifiers on. ---
**Author:** ![taaaaho](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/taaaaho/32/302_2.png) [@taaaaho](https://builder.metamask.io/u/taaaaho)\ **Post date:** [September 25, 2023, 3:39pm UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/19 "2023-09-25T15:39:24Z")
Hi @maharshi , thank you for your advice. In the case of custom authentication, does single-factor-auth not work? It would be helpful for existing customers to be able to use the same code that worked with single-factor-auth before the change to the new structure. I have also tried the code you mentioned, but I get the following error ```auto WalletInitializationError: Wallet is not found, Please add wallet adapter for openlogin wallet, before connecting at WalletInitializationError.fromCode (base.esm.js:242:1) at WalletInitializationError.notFound (base.esm.js:248:1) at Web3AuthNoModal.connectTo (noModal.esm.js:117:77) at initWeb3Auth (useWeb3Auth.ts:111:47) at startWeb3AuthForCreateWallet (_app.tsx:64:31) ``` The sample code does not use an openLoginAdapter instance after it is created, is this correct? ```auto const openloginAdapter = new OpenloginAdapter({ adapterSettings: { uxMode: "redirect", // redirect or popup loginConfig: { jwt: { verifier: "verifier-name", // name of the verifier created on Web3Auth Dashboard typeOfLogin: "jwt", clientId: "", // Web3Auth Client ID }, }, }, privateKeyProvider, }); ``` ---
**Author:** ![maharshi](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/maharshi/32/1525_2.png) [@maharshi](https://builder.metamask.io/u/maharshi)\ **Post date:** [September 25, 2023, 4:43pm UTC](https://builder.metamask.io/t/archive-verifier-not-supported-error/1774/20 "2023-09-25T16:43:10Z")
Hi @taaaaho, custom authentication works like a breeze with SFA web. I’ll link an example [here](https://github.com/Web3Auth/web3auth-core-kit-examples/tree/main/single-factor-auth-web%2Fsfa-next-jwt-example) that I have personally created.