Improve support for Azure AD OAuth 2.0 #630
Merged
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
- use well-known claims for user name - support content types with encodings - support scope parameter -
sijie
approved these changes
Oct 5, 2021
merlimat
approved these changes
Oct 5, 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.
Motivation
This PR improves support for Azure AD and other OAuth 2.0 authorization servers.
Modifications
nameandsubclaims to provide a user name hint to the application. It is for informational purposes only.Content-Typeheaders that contain extra parameters. Use the golang mime parser for this.Verifying this change
This change is partly covered by tests; more tests will be contributed in a follow-up.
Does this pull request potentially affect one of the following parts:
no
Documentation