Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

invalidate JWT with single non-empty string aud on empty bound audiences #295

Merged
merged 3 commits into from
Apr 12, 2024

Conversation

thyton
Copy link
Contributor

@thyton thyton commented Apr 12, 2024

Overview

Our JWT invalidation on empty bound audiences currently includes only the non-empty string array "aud" case. However, https://datatracker.ietf.org/doc/html/rfc7519#section-4.1.3 states

In the special case when the JWT has one audience, the "aud" value MAY be a single case-sensitive string containing a StringOrURI value.

Design of Change

@thyton thyton changed the title invalidate JWT with single non-empty string aud when bound audiences are empty invalidate JWT with single non-empty string aud on empty bound audiences Apr 12, 2024
@thyton thyton requested a review from a team April 12, 2024 00:01
@thyton thyton marked this pull request as draft April 12, 2024 00:03
@thyton thyton marked this pull request as ready for review April 12, 2024 00:08
@thyton thyton merged commit b8833ce into main Apr 12, 2024
4 checks passed
@thyton thyton deleted the VAULT-25183-increase-audience-validation branch April 12, 2024 16:57
thyton added a commit that referenced this pull request May 10, 2024
fairclothjm added a commit that referenced this pull request Jun 13, 2024
fairclothjm added a commit that referenced this pull request Jun 13, 2024
* Revert "invalidate JWT with single non-empty string aud on empty bound audiences (#295)"

This reverts commit b8833ce.

* use new go-jose repo and bump to v3

* add test and remove redundant test
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Audience claim validation required if token contains a list of audiences only
2 participants