Let OIDC users block the opaque tokens if only JWT tokens are expected #17471
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
|
@pedroigor indeed by default this property is enabled since |
|
Proposing for a backport as it is a low risk enhancement |
pedroigor
approved these changes
May 26, 2021
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.
Fixes #17457.
This PR introduces a new
quarkus.oidc.token.allow-opaque-token-introspectionproperty to support the secure deployments expecting JWT tokens only and wishing to avoid any potential slowing down of the endpoint when an opaque (possibly intentionally misformatted JWT sequence) token is sent to Quarkus - since the only way to verify the opaque token is to attempt to verify it remotely