-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Support OAuth RFC - JWT for Client Authentication and Authorization Grants #1768
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
Comments
The "correct" place for this would be in doorkeeper-openid_connect, but it doesn't yet support them: https://github.com/doorkeeper-gem/doorkeeper-openid_connect/blob/v1.8.11/app/controllers/doorkeeper/openid_connect/discovery_controller.rb |
Oh, actually, that's the client assertions spec, |
@ThisIsMissEm Thanks for the quick reply! Yeah as you said that's in the token endpoint. |
We'd need support somewhere for OAuth Assertion Framework RFC7521 for this to be possible — I don't think this spec is currently implemented in any maintained doorkeeper code or plugins. There was this & its forks, but they haven't been maintained in a decade: https://github.com/kiorux/doorkeeper-jwt_assertion/ |
This would be enabled by #1772, which allows registering additional client authentication methods. |
Are there any plans to support JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants?
RFC 7523
From the Abstract:
The text was updated successfully, but these errors were encountered: