POC Introspection endpoint RFC 7662 #590
Open
+423
−0
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
jdeniau
force-pushed
the
jd-feat-introspectionEndpoint
branch
from
975066c
to
53e9199
Compare
jdeniau
force-pushed
the
jd-feat-introspectionEndpoint
branch
from
2dea4a6
to
3306c81
Compare
|
ping @dkarlovi maybe ? |
jdeniau
force-pushed
the
jd-feat-introspectionEndpoint
branch
from
901c775
to
9788ea6
Compare
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.
This is a work in progress but I would like your opinion about implementing the RFC 7662: OAuth 2.0 Token Introspection.
There are no tests for now but it opens the discussion. 📢
A point to discuss that I see is how to handle security.
I implemented this using a list of oauth authorized client, but it's really opinionated as the security might be managed by any possible firewall (you can "just" put the endpoint behind a
Bearerauthorization 🤷♂️ ).