Oidc userinfo #677
Merged
Oidc userinfo #677
Conversation
This file contains hidden or 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
Merged
tribals
approved these changes
Jul 31, 2019
This was referenced Oct 22, 2019
This was referenced Mar 12, 2021
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.
Add the UserInfo endpoint for the OIDC Provider side. For simple use-cases, the goal is to use the RequestValidator:
validate_bearer_tokenis called withopenidscope to validate the tokenget_userinfo_claimsis called to return a list of claims as a dictFor more complex use-cases, the
get_userinfo_claimscan return a JWT/JWS/JWE and the framework will adapt accordingly.