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

Using different keys for sender constrained tokens #99

Open
PieterKas opened this issue Nov 4, 2024 · 0 comments
Open

Using different keys for sender constrained tokens #99

PieterKas opened this issue Nov 4, 2024 · 0 comments

Comments

@PieterKas
Copy link
Contributor

PieterKas commented Nov 4, 2024

Add text, possibly as a security consideration, but also as part of the main text to make it clear the key of an OAuth client presenting a sender constrained token cannot be used for proof of possession by a resource server acting as a client when requesting an assertion from the authorisation server. Instead the resource server will use their own key to perform PoP and obtain an assertion with a requested_cnf claim.

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

1 participant