-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Implement Token introspection endpoint
onto Dex
#3387
Labels
Comments
Seconding this as a feature. This would be incredibly useful to use Dex as a bridge between older Oauth implementations that may not see new RFCs being added. |
Great idea for a contribution! I'd really like to take this in. |
I can work on that :) Hopefully It will be an easy first issue 🙏 |
supercairos
pushed a commit
to supercairos/dex
that referenced
this issue
Mar 7, 2024
supercairos
pushed a commit
to supercairos/dex
that referenced
this issue
Mar 7, 2024
…n. See issue dexidp#3387 Signed-off-by: Romain Caire <[email protected]>
supercairos
added a commit
to supercairos/dex
that referenced
this issue
Mar 7, 2024
…n. See issue dexidp#3387 Signed-off-by: Romain Caire <[email protected]>
supercairos
added a commit
to supercairos/dex
that referenced
this issue
Mar 8, 2024
…n. See issue dexidp#3387 Signed-off-by: Romain Caire <[email protected]>
supercairos
added a commit
to supercairos/dex
that referenced
this issue
Mar 8, 2024
…n. See issue dexidp#3387 Signed-off-by: Romain Caire <[email protected]>
Closed by #3404 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Preflight Checklist
Problem Description
I'm trying to integrate Dex with Ory/Oathkeeper that use the introspect endpoint in order to validate the token.
And I'm realizing that Dex doesn't support the token introspection endpoint.
Proposed Solution
Implement the
Token introspection endpoint
onto Dex:https://www.oauth.com/oauth2-servers/token-introspection-endpoint
https://datatracker.ietf.org/doc/html/rfc7662
Alternatives Considered
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: