Is there a plan to implement RFC 9449 (DPoP: Demonstrating Proof of Possession) #829
Description
Preflight checklist
- I could not find a solution in the existing issues, docs, nor discussions.
- I agree to follow this project's Code of Conduct.
- I have read and am following this repository's Contribution Guidelines.
- I have joined the Ory Community Slack.
- I am signed up to the Ory Security Patch Newsletter.
Ory Network Project
No response
Describe your problem
Right now, the OIDC system doesn’t have a way to prove that a token is being used by the person who owns it. Since RFC 9449 (DPoP) is now a standard, adding it to OIDC would make the system more secure by preventing token misuse.
Describe your ideal solution
The ideal solution is to implement RFC 9449 (DPoP) in OIDC. This would allow the client to prove they own the token by signing each request with a key. It adds an extra layer of security by making sure tokens can’t be reused or stolen easily.
Workarounds or alternatives
Right now, we use other methods like Mutual TLS or token binding, but these are more complicated and less flexible than DPoP. Adding DPoP would simplify things and improve security.
Version
Latest
Additional Context
No response