Support the injection of OIDC introspection response #17896
Merged
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
approved these changes
Jun 15, 2021
|
@sberyozkin Would make sense to allow forcing introspection on a per-invocation basis? The use case I have in mind is an application that is using JWT but for some endpoints (perhaps due to protecting high sensitive info) it should be required validation from the OP in order to force automatic invalidation after revocation. |
|
@pedroigor sure, let me open an issue |
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 #15866
This PR adds a
TokenIntrospectionbean, aligns it withUserInfo, adds the docs and test support.I'm planning to follow up with another PR which will support the optional caching of the introspection and user info responses...