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
Add support for client authentication via "client_assertion_type": "urn:ietf:params:oauth:client-assertion-type:jwt-bearer" and a proper client JWT send as "client_assertion".
To improve security we could also support for authentication via private key JWT via "client_assertion_type": "urn:ietf:params:oauth:client-assertion-type:jwt-bearer" and a proper client JWT send as "client_assertion".
We would then configure "private key jwt" as auth method for the client and add configure the client certificate in the client JWKS configuration.
Details
client_assertion_type, private key and certificate should be provided as configuration parameters.
The text was updated successfully, but these errors were encountered:
thomasdarimont
changed the title
Support authentication via private key jwt
Support client authentication via private key jwt
Nov 28, 2024
Description
Add support for client authentication via "client_assertion_type": "urn:ietf:params:oauth:client-assertion-type:jwt-bearer" and a proper client JWT send as "client_assertion".
Discussion
No response
Motivation
IMHO using a dedicated client with
client_credentials
grant and proper service account roles for managing the realm configurations is the best way to go. Unfortunately the current version of the terraform provider only supports client authentication viaclient secret
, as shown here: https://github.com/keycloak/terraform-provider-keycloak/blob/master/keycloak/keycloak_client.go#L261To improve security we could also support for authentication via private key JWT via "client_assertion_type": "urn:ietf:params:oauth:client-assertion-type:jwt-bearer" and a proper client JWT send as "client_assertion".
We would then configure "private key jwt" as auth method for the client and add configure the client certificate in the client JWKS configuration.
Details
client_assertion_type, private key and certificate should be provided as configuration parameters.
The text was updated successfully, but these errors were encountered: