Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Wrong "aud" (Audience) claim validation #1234

Closed
3 tasks done
dadrus opened this issue Mar 12, 2024 · 0 comments · Fixed by #1237
Closed
3 tasks done

Wrong "aud" (Audience) claim validation #1234

dadrus opened this issue Mar 12, 2024 · 0 comments · Fixed by #1237
Labels
bug Something isn't working
Milestone

Comments

@dadrus
Copy link
Owner

dadrus commented Mar 12, 2024

Preflight checklist

  • I agree to follow this project's Code of Conduct.
  • I have read and am following this repository's Contribution Guidelines."
  • I could not find a solution in the existing issues, docs, nor discussions.

Describe the bug

Citing RFC-7519, section 4.1.3:

the audience claim identifies the recipients that the JWT is intended for. Each principal intended to process the JWT MUST identify itself with a value in the audience claim.

The same is also true for the "aud" claim from the introspection endpoint response (see RFC-7662).

Since the aforementioned principals do not need to know each other, the principal must not reject the token if it encounters further audience references, it does not understand. Heimdall currently expects however all audiences to be known.

So if a token contains an "aud" claim with the values foo, bar and heimdall is configured to expect bar, the assertion will fail leading to failed authentication.

The implementation should adhere to the requirements from the RFCs referenced above.

How can the bug be reproduced

See example given above

Relevant log output

No response

Relevant configuration

No response

Version

v0.13.0-alpha

On which operating system are you observing this issue?

None

In which environment are you deploying?

None

Additional Context

No response

@dadrus dadrus added the bug Something isn't working label Mar 12, 2024
@dadrus dadrus added this to the v0.14.0-alpha milestone Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant