Repository navigation
|
I have been trying out the "OAuth 2.0 Mutual TLS Certificate Bound Access Tokens Enabled" feature. When this is enabled, a browser based login flow with mTLS correctly adds the I have setup keycloak to use a login flow which does an X509/Validate Username. I have "OAuth 2.0 Mutual TLS Certificate Bound Access Tokens Enabled" selected in the client configuration. curl --cert <path-to-user-cert> --key <path-to-user-key> -X POST 'https://<keycloak-url>/protocol/openid-connect/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'client_id=<client-id>' \
--data-urlencode 'grant_type=password' |
Replies: 3 comments 5 replies
|
Hello @bw512, The current keycloak (kc19) support this holder-of-key bound token for the following grant:
The current keycloak (kc19) does not support the holder-of-key bound token for resource owner password credentials grant (direct grant in keycloak). |
|
@bw512 It is not 100% sure that this issue be treated but could you create a corresponding issue on the issue tab? |
|
@bw512 It seems that you intended to bind a user (a user's private key) with an access token. Could you tell me which kind of use cases this user-bound token is used in? |
Hello @bw512,
The current keycloak (kc19) support this holder-of-key bound token for the following grant:
The current keycloak (kc19) does not support the holder-of-key bound token for resource owner password credentials grant (direct grant in keycloak).