Getting Oops... Unauthorized after signup

Downloaded the sample and did npm i and npm start. Was able to sign up and sign in successfully according to the logs.

However, after clicking on the green tick when prompted to grant permission, it kept display a blank page with Oops... Unauthorized.

Log type Failed Exchange

Log as below:

{
  "date": "2020-07-25T17:37:08.413Z",
  "type": "feacft",
  "description": "Unauthorized",
  "connection_id": "",
  "client_id": "--removed--
  "client_name": null,
  "ip": "101.127.6.165",
  "user_agent": "Chrome 84.0.4147 / Mac OS X 10.15.5",
  "details": {
    "code": "*************BA6"
  },
  "hostname": "--removed--",
  "user_id": "",
  "user_name": "",
  "log_id": "90020200725173713598000178280607258323126144419732914178",
  "_id": "90020200725173713598000178280607258323126144419732914178",
  "isMobile": false
}

[mrquincle]

I would recommend to create a new account and run your own example. This is my on-boarding experience till now:

1. As a new user I have of course the “Default App”.
2. Start at https://auth0.com/docs/quickstart/spa/react downloading the code. The site works fine locally, but the login feature doesn’t work. It’s complaining about the default value in the audience field. Okay, figuring out on the next page https://auth0.com/docs/quickstart/spa/react/02-calling-an-api what to fill in there.
3. After logging in with two different methods (because I read somewhere that the social login with Google might not work) I still get Oops... Unauthorized.
4. Quite a lot of the code is not the same as with the example app I have downloaded. Weird, why is it not updated? I see ProfileComponent rather than Profile, etc.
5. Start hunting down the above cryptic message on the internet and ending up here. It doesn’t work with “Default App”… Mmm… That’s not the on-boarding experience you want to have. If that’s the case, make sure someone first creates a new app and disallow the “Default App” from the drop-down box in the beginning.

I have now solved it by indeed changing the settings in “Default App” as described:

• Token Endpoint Authentication Method is disabled
• Change Application Type to Regular Web Application, this enables the above option
• Change Token Endpoint Authentication Method to None.
• Change Application Type to Single Page Application, don’t forget to save.

I have the feeling auth0 was really good in the onboarding experience, but there are no resources anymore for this. Please, use my extended comment as hopefully constructive feedback. I’m not a disgruntled user. I’m honestly just a bit surprised (also on this issue just being closed).

[ouchxp]

Hey all,

We do have a known issue when you’re using the Default App as supplied with a new tenant. Please could you try the following.

Either:

* Create a new application, ensure it is a Single Page Application type and that the Token Endpoint Authentication Mode setting is "None"

* Modify your existing Default App so that Token Endpoint Authentication Mode is set to "None". For SPAs, this option is normally disabled, so you may need to change to a different application type, change this setting and then set it back to SPA again.

Let me know if that works or doesn’t make sense.

This worked for me! Thanks!