Revert to 6x behavior with GetPayloadClaim<object>("aud") #2331
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
…s a simple string.
jennyf19
approved these changes
Sep 26, 2023
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.
In 6x, GetPayloadClaim("aud") will return a single string when aud was a single value.
The changes in 7 resulted in a List with one value, which broke some users.
This change returns to the same behavior as 6x.
Note: GetPayloadClaim("aud") would return a string.
JsonWebToken.Audiences is a better approach to access the 'aud' values as during the deserialization of the JWT, the audience values are deserialized.
Addresses: #2328