Reject tokens when claims has an aud, none expected #332
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
From the RFC: > Each principal intended to process the JWT MUST > identify itself with a value in the audience claim. If the principal > processing the claim does not identify itself with a value in the > "aud" claim when this claim is present, then the JWT MUST be >rejected. Closes Keats#329
Keats
reviewed
Oct 10, 2023
|
Thanks. That's a breaking change so that would be released as v9 |
|
Thanks, @Keats! Do you have a timeline or process for these sorts of things, or is it something that "just happens" from time to time? Just curious to set my own expectations. |
|
Probably this week if i don't forget about it in the meantime |
|
Thank you greatly! |
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.
From the RFC:
Closes #329