Add an unverified audience reader for routing and diagnostics#7
Merged
Conversation
Expose a way to read a JWT-SVID's aud claim without verifying the signature, for routing and diagnostics — e.g. choosing which trust context to verify under before an expected audience is known: unverified_audience (Python), unverifiedAudience (TypeScript), UnverifiedAudience (Go). All three reject an array aud rather than silently coercing a multi-audience token, and report a missing aud as empty (None/null/""). The result is attacker-controlled and must always be followed by verify.
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
1 participant
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.
Expose a way to read a JWT-SVID's
audclaim without verifying the signature, for routing and diagnostics — e.g. choosing which trust context to verify under before an expected audience is known.unverified_audience→str | NoneunverifiedAudience→string | nullUnverifiedAudience→(string, error)All three implementations behave identically:
aud→ reported as empty (None/null/""), no error.aud→ rejected, never silently coerced to a single audience.The result is attacker-controlled and must always be followed by
verify; the docstrings and CHANGELOG say so explicitly.Verification
go vet,tsc --noEmit,ruff checkall cleancheck-parityskill and the[Unreleased]CHANGELOG entry updated