auth: immediately reject JWTs with mismatched azp or aud claims#1804
Open
jedisct1 wants to merge 3 commits into
Open
auth: immediately reject JWTs with mismatched azp or aud claims#1804jedisct1 wants to merge 3 commits into
jedisct1 wants to merge 3 commits into
Conversation
A JWT with the wrong authorized party or audience was previously silently falling through to the token exchange instead of being rejected. Not critical since signature verification would then fail, but but we should return the error directly on mismatch.
anthony-gomez-fastly
approved these changes
May 28, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Change summary
A JWT with the wrong authorized party or audience was previously silently falling through to the token exchange instead of being rejected.
Not critical since signature verification would then fail, but we can return the error directly on mismatch, so we should do it.
All Submissions:
Changes to Core Features:
User Impact
None for legitimate users. JWTs minted for a different
azporaudwill now be rejected at validation time with a clear error, instead of being passed on to the token exchange step.Are there any considerations that need to be addressed for release?
No breaking changes.