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

Better to return tokenBindingId as cnf in the jwt token for client-request binding type #19331

Closed
VivekVinushanth opened this issue Feb 1, 2024 · 2 comments

Comments

@VivekVinushanth
Copy link
Contributor

Is your suggestion related to an experience ? Please describe.

With this change, for the client-request token binding type, users will be able to obtain the tokenBindingId value they have sent in the token request. Though the JWT token returns a tokenBinding reference which is a hashed value, for this binding type, applications might be interested in knowing the value itself.

Describe the improvement
Return tokenBindingId as CNF in the jwt token for client-request binding type

Additional context

@VivekVinushanth
Copy link
Contributor Author

@VivekVinushanth VivekVinushanth removed their assignment Feb 1, 2024
@VivekVinushanth
Copy link
Contributor Author

Need to consider Introspection as well.

@janakamarasena janakamarasena removed their assignment Feb 6, 2024
@VivekVinushanth VivekVinushanth closed this as not planned Won't fix, can't repro, duplicate, stale Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants