Skip to content
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

Feature Request: DPoP #419

Open
gtrak opened this issue Feb 17, 2025 · 3 comments
Open

Feature Request: DPoP #419

gtrak opened this issue Feb 17, 2025 · 3 comments

Comments

@gtrak
Copy link

gtrak commented Feb 17, 2025

I haven't found an off the shelf rust solution for validating DPoP proofs, although it seems relatively simple to implement on top of this library. Is it something you would consider?

@rimutaka
Copy link

@gtrak , I'm not a maintainer, but would happily help you implement it. One of my projects is always at risk of XSS and having DPOP validation will help.

@Keats
Copy link
Owner

Keats commented Feb 18, 2025

I had never heard of DPoP before. How big of a change are we talking about?

@gtrak
Copy link
Author

gtrak commented Feb 18, 2025

I'll get to it within my own codebase this week, and will see how it looks on top of this lib, but then the next question is if it should be in the library.

Dpop isn't a big change to implement, I hope. It reuses jwt/jwk machinery to check an extra signature on the access token that guarantees the client requested it. I think generating dpop proofs is a little more complex, but I just need to validate them on access tokens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants