# Error: No verifier returned from client

**URL:** <https://community.auth0.com/t/error-no-verifier-returned-from-client/87727>\
**Category:** Get Help\
**Tags:** auth0js, login, auth0\
**Created:** [July 27, 2022, 8:40am UTC](https://community.auth0.com/t/error-no-verifier-returned-from-client/87727 "2022-07-27T08:40:12Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tobias.walter](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/tobias.walter/32/13728_2.png) [@tobias.walter](https://community.auth0.com/u/tobias.walter)\
**Post date:** [July 27, 2022, 8:40am UTC](https://community.auth0.com/t/error-no-verifier-returned-from-client/87727/1 "2022-07-27T08:40:12Z")

</div>

Hi there,

we are trying to use auth0.js for login. With Chrome it’s not a problem, but Firefox or Chrome incognito mode yields `No verifier returned from client`.

Here is our simple test setup:

index.html:

```auto
<html>
  <head>
    <script src="https://cdn.auth0.com/js/auth0/9.19.0/auth0.min.js"></script>
  </head>
  <body>
    <script>
      const auth = new auth0.WebAuth({
        domain: domain,
        clientID: clientId,
        redirectUri: `http://localhost:4200/callback`,
        audience: audience,
        scope: 'openid email profile',
        responseType: 'token id_token'
      });

      const state = JSON.stringify({
        redirectUrl: '/'
      });
      const nonce = "random";

      auth.login({
          realm: 'Username-Password-Authentication',
          username: username,
          password: password,
          redirectUri: `http://localhost:4200/callback`,
          state: state,
          nonce: nonce
        },
        err => {
          console.log(err);
        });
    </script>
  </body>
</html>

```

callback.html:

```auto
<html>
  <head>
    <script src="https://cdn.auth0.com/js/auth0/9.19.0/auth0.min.js"></script>
  </head>
  <body>
    <script>
      const auth = new auth0.WebAuth({
        domain: domain,
        clientID: clientId,
        redirectUri: `http://localhost:4200/callback`,
        audience: audience,
        scope: 'openid email profile',
        responseType: 'token id_token'
      });

      const state = JSON.stringify({
        redirectUrl: '/'
      });
      const nonce = "random";

      auth.parseHash({
        hash: window.location.hash,
        nonce: nonce,
        state: localStorage.getItem('state')
      }, (err, authResult) => {
        console.log(err);
        console.log(authResult);
      });
    </script>
  </body>
</html>

```

`auth.parseHash` returns the error:

```auto
{
    "error": "invalid_request",
    "errorDescription": "No verifier returned from client.",
    "state": "{\"redirectUrl\":\"/\"}"
}

```

We’ve set up a Cross-Origin Verification Fallback like this:

```auto
<!DOCTYPE html>
<html>

<head>
  <script src="https://cdn.auth0.com/js/auth0/9.0.0/auth0.min.js"></script>
  <script type="text/javascript">
    var auth0Client = new auth0.WebAuth({
      domain: domain,
      redirectUri: redirectUri,
      clientID: clientId,
      responseType: 'token'
    });
    auth0Client.crossOriginVerification();
  </script>
</head>

<body></body>

</html>

```

Anything we’re doing wrong? It not only happens on `localhost`, also on staging environment.

---

<div class="post-metadata">

**Author:** ![radko.lyutskanov](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/radko.lyutskanov/32/13366_2.png) [@radko.lyutskanov](https://community.auth0.com/u/radko.lyutskanov)\
**Post date:** [December 15, 2022, 3:16pm UTC](https://community.auth0.com/t/error-no-verifier-returned-from-client/87727/2 "2022-12-15T15:16:01Z")

</div>

Hello, We do have exactly the same problem. Even though we do have custom domain set, we do have cross origin verification file hosted on the same location as the embedded sign up lock form. for example

```auto
(https://3d24-78-130-209-11.ngrok.io/auth0/index.html) contains the Cross-Origin Verification Fallback
(https://3d24-78-130-209-11.ngrok.io/register) contains the embedded lock form.

```

And still if you try to perform operation login / sign up via the form you get redirected with

```auto
authorize/resume?state=XXXX with header location
/register#error=invalid_request&error_description=No verifier returned from client

```

---

<div class="post-metadata">

**Author:** ![vadzim.vashchanka](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/vadzim.vashchanka/32/45316_2.png) [@vadzim.vashchanka](https://community.auth0.com/u/vadzim.vashchanka)\
**Post date:** [August 20, 2024, 7:36am UTC](https://community.auth0.com/t/error-no-verifier-returned-from-client/87727/3 "2024-08-20T07:36:26Z")

</div>

Hey, the same issue here, have anyone found a solution?

---

<div class="post-metadata">

**Author:** ![sabina96clerk](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/sabina96clerk/32/72768_2.png) [@sabina96clerk](https://community.auth0.com/u/sabina96clerk)\
**Post date:** [August 4, 2025, 12:30pm UTC](https://community.auth0.com/t/error-no-verifier-returned-from-client/87727/4 "2025-08-04T12:30:04Z")

</div>

Did you have a fix on this issue?

---

<div class="post-metadata">

**Author:** ![teodor.andrei](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/teodor.andrei/32/75320_2.png) [@teodor.andrei](https://community.auth0.com/u/teodor.andrei)\
**Post date:** [August 4, 2025, 1:13pm UTC](https://community.auth0.com/t/error-no-verifier-returned-from-client/87727/6 "2025-08-04T13:13:15Z")

</div>

Hi @sabina96clerk, and thank you for bringing this subject back to light so we can provide a solution!

The root cause of the “No verifier returned from client” error is that the method uses `auth.login()` with a username and password and relies on **cross-origin authentication using third-party cookies**.

Modern browsers, particularly Firefox (with Enhanced Tracking Protection) and Chrome Incognito mode, **block third-party cookies by default** for privacy reasons. This breaks the communication channel that `auth0.js` uses to complete the login, leading to the error you’re seeing. The “Cross-Origin Verification Fallback” is a legacy mechanism that also struggles with these modern privacy restrictions and cannot fix this underlying issue.

To fix this reliably across all browsers, you must switch from the cross-origin `auth.login()` method to the redirect-based **Authorization Code Flow**. This flow does not depend on third-party cookies and is the current best practice.

The change is straightforward: instead of logging the user in behind the scenes, you will redirect them to the Auth0 Universal Login page to enter their credentials. So you need to replace the `webAuth.login()` call with `webAuth.authorize()`. This method will handle redirecting the user to your Auth0 login page.

Please take a look at our [docs](https://auth0.com/docs/libraries/auth0js#webauth-authorize-:~:text=in%20your%20application.-,webAuth.authorize(),-The%20authorize()) for an example.

I hope this helps you!  
Teodor.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [August 18, 2025, 1:14pm UTC](https://community.auth0.com/t/error-no-verifier-returned-from-client/87727/7 "2025-08-18T13:14:17Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
