# \[Archive\] Removed Custom Auth Verifier, Getting error on login

**URL:** <https://builder.metamask.io/t/archive-removed-custom-auth-verifier-getting-error-on-login/1787>\
**Category:** Embedded Wallets (Web3Auth)\
**Created:** [September 5, 2023, 7:06pm UTC](https://builder.metamask.io/t/archive-removed-custom-auth-verifier-getting-error-on-login/1787 "2023-09-05T19:06:13Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![garrett](https://avatars.discourse-cdn.com/v4/letter/g/3e96dc/32.png) [@garrett](https://builder.metamask.io/u/garrett)\
**Post date:** [September 5, 2023, 7:06pm UTC](https://builder.metamask.io/t/archive-removed-custom-auth-verifier-getting-error-on-login/1787/1 "2023-09-05T19:06:13Z")

</div>

> **🏛 Archived Content from Web3Auth Community**
> 
> This topic was originally posted by **garrett** on 9/5/2023.  
> This content has been migrated from our previous community forum to preserve valuable discussions.

* * *

Added a Custom Auth Verifier for Google OAuth to our Team workspace account in the dashboard to see if that would enhance the whitelabel capabilities. I then deleted the OAuth credentials and removed the Custom Verifier from the Web3Auth dashboard.

It seems like Web3Auth is still trying to use my old Verifier instead of the default OpenLogin one

**Please provide the following details too when asking for help in this category:**

- SDK Version: 6.1.0

- Platform: Web

- Browser Console Screenshots:  

- Related to Custom Authentication? Please provide the following info too: **(Optional)**

**Please provide the Web3Auth initialization and login code snippet below:**

```auto

    const chainConfig = {
      chainNamespace: 'eip155' as const,
      chainId: toHex(chains[0].id),
      rpcTarget: `${chains[0].rpcUrls['alchemy'].http[0]}/${options.alchemyApiKey}`,
      displayName: chains[0].name,
      blockExplorer: chains[0].blockExplorers!.default.url,
      tickerName: chains[0].nativeCurrency.name,
      ticker: chains[0].nativeCurrency.symbol,
    };
const web3Auth = new Web3AuthNoModal({
  clientId: options.clientId,
  web3AuthNetwork: options.web3AuthNetwork,
  chainConfig: chainConfig,
  sessionTime: options.sessionTime,
});
const privateKeyProvider = new EthereumPrivateKeyProvider({
  config: { chainConfig },
});
const adapter = new OpenloginAdapter({
  adapterSettings: {
    whiteLabel: {
      name: 'Masterfile',
      dark: true,
      theme: { primary: '#7544E0' },
    },
    uxMode: 'popup',
  },
  loginSettings: { mfaLevel: 'none' },
  privateKeyProvider,
});

web3Auth.configureAdapter(adapter);

```

---

<div class="post-metadata">

**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\
**Post date:** [September 5, 2023, 11:18pm UTC](https://builder.metamask.io/t/archive-removed-custom-auth-verifier-getting-error-on-login/1787/2 "2023-09-05T23:18:01Z")

</div>

@garrett Welcome Aboard!

Your request has been forwarded to our team and we will get back with further updates once more information becomes available.

---

<div class="post-metadata">

**Author:** ![yashovardhan](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/yashovardhan/32/1526_2.png) [@yashovardhan](https://builder.metamask.io/u/yashovardhan)\
**Post date:** [September 6, 2023, 3:09am UTC](https://builder.metamask.io/t/archive-removed-custom-auth-verifier-getting-error-on-login/1787/3 "2023-09-06T03:09:20Z")

</div>

Can you show us the code for your `connectTo` function for logging in?

---

<div class="post-metadata">

**Author:** ![garrett](https://avatars.discourse-cdn.com/v4/letter/g/3e96dc/32.png) [@garrett](https://builder.metamask.io/u/garrett)\
**Post date:** [September 6, 2023, 4:23am UTC](https://builder.metamask.io/t/archive-removed-custom-auth-verifier-getting-error-on-login/1787/4 "2023-09-06T04:23:20Z")

</div>

```auto
import {
  WALLET_ADAPTERS,
} from '@web3auth/base';

....

      await this.web3Auth.connectTo(WALLET_ADAPTERS.OPENLOGIN, {
          loginProvider: "google"
        });

```

---

<div class="post-metadata">

**Author:** ![garrett](https://avatars.discourse-cdn.com/v4/letter/g/3e96dc/32.png) [@garrett](https://builder.metamask.io/u/garrett)\
**Post date:** [September 6, 2023, 4:24am UTC](https://builder.metamask.io/t/archive-removed-custom-auth-verifier-getting-error-on-login/1787/5 "2023-09-06T04:24:27Z")

</div>

This is also inside our own custom WAGMI connector but I dont think that should have any effect on things

---

<div class="post-metadata">

**Author:** ![garrett](https://avatars.discourse-cdn.com/v4/letter/g/3e96dc/32.png) [@garrett](https://builder.metamask.io/u/garrett)\
**Post date:** [September 7, 2023, 9:37pm UTC](https://builder.metamask.io/t/archive-removed-custom-auth-verifier-getting-error-on-login/1787/6 "2023-09-07T21:37:05Z")

</div>

Any updates on this? Still broken for us

---

<div class="post-metadata">

**Author:** ![garrett](https://avatars.discourse-cdn.com/v4/letter/g/3e96dc/32.png) [@garrett](https://builder.metamask.io/u/garrett)\
**Post date:** [September 11, 2023, 11:16pm UTC](https://builder.metamask.io/t/archive-removed-custom-auth-verifier-getting-error-on-login/1787/7 "2023-09-11T23:16:21Z")

</div>

Hey, any updates? Would like to get this fixed ASAP

---

<div class="post-metadata">

**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 14, 2023, 1:23pm UTC](https://builder.metamask.io/t/archive-removed-custom-auth-verifier-getting-error-on-login/1787/8 "2023-09-14T13:23:56Z")

</div>

Please note that you’ll have to be on atleast the Growth plan for customauth. And try changing the client id by creating a new project and see if this issue persists. And I would encourage you to update to the v7 SDK since the end-of-life for v6 is Dec 2023.