Fix audience #9
Merged
Fix audience #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wparad
approved these changes
Nov 23, 2017
added 3 commits
November 23, 2017 16:47
… token from the lock widget might not include the audience, depending on the application settings. Consult the auth0 lock's oidcConformant and audience settings documentation.
…ents can call this in their client code before a call to this auth library.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The auth0 lock doesn't return the audience with the token unless the
oidcConformanceflag is enabled with the application. In order to do so, Cross-Origin Authentication must also be enabled with a single callback URL.Webauth however isn't restricted by the auth0 lock. The solution taken here is to call webauth directly after a successful auth0 lock login.