You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: