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
{{ message }}
Repository navigation
Support JWT authorisation grants without persistent local users
#54088
Description
The JWT authorisation grant allows a confidential client to exchange a signed assertion from a trusted external issuer for a Keycloak access token. The current flow requires the external subject to resolve to an existing Keycloak user linked to the configured Identity Provider.
Some integrations need to accept externally authenticated actors without maintaining corresponding local accounts. The external issuer owns the user lifecycle, while Keycloak validates the assertion and issues a token under its own trust and authorisation configuration.
Value Proposition
This would allow Keycloak to act as a token issuer across trust domains without requiring local provisioning for every external actor. It would also avoid account synchronisation and cleanup where local account management provides no additional value.
The consuming resource server would validate the issued token and use its claims directly. It would not depend on a Keycloak Admin API lookup to resolve the actor.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Description
The JWT authorisation grant allows a confidential client to exchange a signed assertion from a trusted external issuer for a Keycloak access token. The current flow requires the external subject to resolve to an existing Keycloak user linked to the configured Identity Provider.
Some integrations need to accept externally authenticated actors without maintaining corresponding local accounts. The external issuer owns the user lifecycle, while Keycloak validates the assertion and issues a token under its own trust and authorisation configuration.
Value Proposition
This would allow Keycloak to act as a token issuer across trust domains without requiring local provisioning for every external actor. It would also avoid account synchronisation and cleanup where local account management provides no additional value.
The consuming resource server would validate the issued token and use its claims directly. It would not depend on a Keycloak Admin API lookup to resolve the actor.
See #54087
All reactions