Auth0 Home Blog Docs

Getting all kinds of configuration errors while trying to login


#1

I’ve been trying to migrate to auth0 lock 11, but am having issues with logging in. I’ve also tried switching to a completely auth0-js approach by following the basic vanilla JS guide in the quickstart guide for setting up a single page application. Each time I’m getting some weird configuration error that I have no idea how to fix. Here are the errors I’m getting with the auth0-js attempt:

{
  "date": "2018-04-05T23:34:43.223Z",
  "type": "f",
  "description": "Unable to validate session-bound result token.",
  "connection": "Username-Password-Authentication",
  "connection_id": "secret",
  "client_id": "secret",
  "ip": "secret",
  "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36",
  "details": {
    "body": {
      "wa": "wsignin1.0",
      "wresult": "secret",
      "wctx": "{secret}"
    },
    "qs": {},
    "connection": "Username-Password-Authentication",
    "error": {
      "message": "Unable to validate session-bound result token.",
      "oauthError": "invalid_request",
      "type": "request-error"
    }
  },
  "hostname": "secret",
  "log_id": "secret"
}

And this is the error I’ve been getting when trying to login with the lock widget:

{
  "date": "2018-04-05T22:48:47.185Z",
  "type": "fcoa",
  "description": "Unable to configure verification page.",
  "connection": null,
  "connection_id": "",
  "ip": "secret",
  "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36",
  "details": {
    "body": {},
    "qs": {
      "client_id": "secret",
      "response_type": "code token id_token",
      "redirect_uri": "http://localhost:5000",
      "nonce": "secret",
      "state": "secret",
      "scope": "app_metadata profile email openid user_metadata",
      "realm": "Username-Password-Authentication",
      "login_ticket": "secret",
      "response_mode": "web_message",
      "prompt": "none",
      "auth0Client": "secret"
    },
    "error": {
      "message": "Unable to configure verification page.",
      "oauthError": "server_error",
      "type": "oauth-authorization"
    }
  },
  "hostname": "secret",
  "log_id": "secret"
}

The weird thing is that I setup a test tenant and client and didn’t have these issues at all. I checked to make sure all settings I could think of were the same and could not reproduce the error in the new tenant/client. What is wrong with my existing tenant/client? What am I doing wrong? What do these error messages mean and how would I even fix these things?


#2

I cleared my browsing history and now everything is working. Weird.


#3

Interesting! I must say I am glad it is resolved though! Please let us know if you experience this issue again and we can look into it together.