-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Support RFC9449 - DPoP Authentication scheme #14915
Comments
Thanks for opening this @babisRoutis. I am marking this for consideration in a future release. |
Hi @sjohnr happy to hear that this is for consideration. With regards to DPoP there are two features that you can consider:
|
Thanks @babisRoutis.
For that, please feel free to open an issue over there since this issue tracker is just for the Spring Security side. |
I'd say this issue should also include DPoP support for the OAuth2 clients out there 😄 In fact, I'm struggling with implementing this right now, and I'm being stopped dead in my tracks due to the strictness of Spring Security. Would it be possible to introduce a new constant in public static final TokenType BEARER = new TokenType("Bearer");
public static final TokenType DPOP = new TokenType("DPoP"); // new I can't make this in my own code because the constructor is |
@ThomasKasene thanks for the input.
Absolutely, that makes sense to me. Would you be interested in opening a PR for this? If so, make sure to reference this issue in the commit comment as "Issue gh-14915". I think it also makes sense to open an issue to consider making the constructor |
Done via gh-16087 😄 |
RFC9449 introduces a way to constraint tokens (
access_token
,refresh_token
) to a client provided pub key.For a resource server (implemented using spring security) it would be really useful to implement in addition to bearer authentication the DPoP Authentication scheme
Note: Nimbus contains already support for producing DPoP JWT(s) & validating them
The text was updated successfully, but these errors were encountered: