Access Denied error after changing SPA application name

[viral]

I tried to rename an existing SPA application from XYZ to ABC.

Applications > XYZ (SPA) > Settings > Basic Information > Name
change it and click on Save.

Changes saved successfully.

Now when I try to login to my applcation from my SPA, its gives me an error which reads
“Access Denied: Unsupported client ABC”

Is there some dependency somewhere on this application name?

[tyf]

Hey there @viral welcome to the community!

@viral

Now when I try to login to my applcation from my SPA, its gives me an error which reads
“Access Denied: Unsupported client ABC”

Is there some dependency somewhere on this application name?

Hmm that’s pretty odd! I can’t think of anywhere where the application name is a dependency - Do you see the failed login attempt in your logs (monitoring → logs)? There might be some more helpful information there.

[viral]

Hi tyf, here is a masked screenshot. Please let me know if there is something else that is needed as well.

{
  "date": "2024-02-26T17:30:22.532Z",
  "type": "fsa",
  "description": "Access Denied: Unsupported client $$$",
  "client_id": "$$$",
  "client_name": "$$$",
  "ip": "$$$",
  "user_agent": "Chrome 121.0.0 / Mac OS X 10.15.7",
  "details": {
    "body": {},
    "qs": {
      "audience": "$$$",
      "client_id": "$$$",
      "redirect_uri": "$$$",
      "scope": "openid profile email offline_access",
      "response_type": "code",
      "response_mode": "web_message",
      "state": "$$$",
      "nonce": "$$$",
      "code_challenge": "$$$",
      "code_challenge_method": "S256",
      "prompt": "none",
      "auth0Client": "$$$"
    },
    "connection": null,
    "error": {
      "message": "Access Denied: Unsupported client $$$",
      "oauthError": "access_denied",
      "type": "oauth-authorization"
    },
    "session_id": "IiDpsj_Le0wuWfG8YtjQdPm6SwSbKNEn",
    "session_connection": "$$$",
    "actions": {
      "executions": [
        "d17aOuPORDisQoWlE2-YfzIwMjQwMjI2"
      ]
    },
    "stats": {
      "loginsCount": 19
    }
  },
  "hostname": "$$$",
  "user_id": "$$$",
  "user_name": "$$$",
  "audience": "$$$",
  "scope": [
    "openid",
    "profile",
    "email",
    "offline_access"
  ],
  "auth0_client": {
    "name": "auth0-react",
    "version": "1.9.0"
  },
  "$event_schema": {
    "version": "1.0.0"
  },
  "log_id": "90020240226173022577854000000000000001223372045532679513",
  "_id": "90020240226173022577854000000000000001223372045532679513",
  "isMobile": false,
  "id": "90020240226173022577854000000000000001223372045532679513"
}

[tyf]

Thanks for sharing! It’s still hard to know what the exact issue could be, but it does look to be a a failed silent auth (fsa) - In that case, was there a successful login initially? Do you experience the same behavior if you change the application name back to what it was?

[viral]

Yes! Changing the name back to it’s original name works fine! I’m quite baffled

[tyf]

Strange! I just tested in my own environment and was unable to reproduce - Do you mind DMing me the following:

• Tenant name
• SPA application in question
• Is this a database user or social (google, etc.) connection
• Auth0 SDK being utilized for the SPA

If you’re feeling ambitious, I would be super curious if you experience this issue in a Sample app - I tested using the auth0-react sample FWIW.

[tyf]

Resolved in a DM - For future reference there was an Action configured which was causing the issue