Many errors and continuation of closed ticket

[deanbiltup]

Checklist

• I have looked into the Readme (Quickstart sample/Standalone sample) and have not found a suitable solution or answer.
• I have searched the issues and have not found a suitable solution or answer.
• I have searched the Auth0 Community forums and have not found a suitable solution or answer.
• I agree to the terms within the Auth0 Code of Conduct.

Description

I found this ticket #469 which was for missing docs and those docs were never added to(it probably would have saved my life). Please do add links from sample to 'how to add audience'. you will see the steps I tried to fix it at the bottom of that ticket based on documentation but still not working. No idea if my steps were correct or WHY is audience even needed? (startup fails if I do not have an audience)

npm run build, npm run prod -> This fails and should be fixed or remove from README (I say just remove it so you don't have to support so many things ;) ). a very quick removal so no one hits that in the future.

npm run dev 'seems to at least give me a landing page'. perhaps remove the npm run build and npm run prod from docs?

My main error now is this

"""An error was returned from Auth0
Something went wrong when trying to authorize your application. Please inspect the error below and ensure auth_config.json is configured correctly.

Unauthorized"""

Reproduction

I tried two ways of getting standalone angular typescript w/express nodejs backend typescript where tried. Let us focus on the one mentioned in the above ticket/issue as https://auth0.com/docs/quickstart/spa/angular/ however it still did not fill in my audience and only filled in domain and client id. so I followed steps of

1. modify my settings to fill in http://localhost:4200 as it says after clicking 'download sample'
2. creating an api called basic, identifier https://basic.company.com/ and jwt profile auth0, signing rs256
3. in your client, click api tab and give access to this new api
4. modify config file to have identifier https://basic.company.com/
5. npm install
6. npm run build
7. npm run prod

SIDENOTE: It really bothers me we are not putting a client secret in the server somewhere to full cycle validate like we do with google oauth (we are looking at replacing our google oauth flow with auth0 and adding microsoft - OR adding microsoft ourselfs without auth0 - still evaluating right now).

Additional context

No response

Sample

Standalone

Which browsers have you tested in?

Chrome

[deanbiltup]

For anyone who runs across this ticket, I instead was able to get 'firebase authentication' with google and email/password working much faster (no dealing with authorization audience in first stages since only dealing with login as authorization only comes later when you need access to their gcalendar or some api). Though could technically add the web server origin as an api but our frontend is served from same server that it talks to over api (no CORS to reduce complexity of cross site calls). I wanted to try auth0, but every time I come back the examples do not work out of the box :( Hopefully that is fixed sometime.