Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Audience #52

Closed
felipeleusin opened this issue Aug 30, 2019 · 2 comments
Closed

Audience #52

felipeleusin opened this issue Aug 30, 2019 · 2 comments

Comments

@felipeleusin
Copy link

Hi,

We we're integrating a NodeJS app and we got stuck for a while because the token being returned by Auth0 wasn't a JWT (and we needed it to be one to call other APIs) and instead an opaque token.

This was only solved when we included in the login passport call (https://github.com/auth0-samples/auth0-nodejs-webapp-sample/blob/master/01-Login/routes/auth.js#L13) the audience of our API.

I believe this should be included in the documentation, but I'm not entirely sure where so I'm opening this ticket to bring this to attention.

@lbalmaceda
Copy link
Contributor

Hi @felipeleusin. The samples used to include the "userinfo audience" which triggered that format change as well. But it was removed in favor of verifying the ID Token and reading the user data from its contents.
The different access token formats is already documented here.

@felipeleusin
Copy link
Author

Ok. Thanks. This was something that me and my team missed and we kind of got it right by luck. Might be worthy to add some documentation in the quickstart.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants