8000
Separate capability for each of the service account under one client is there any way to achieve this? · keycloak keycloak · Discussion #41555 · GitHub
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
Separate capability for each of the service account under one client is there any way to achieve this?
#41555
We’re exploring a setup where we would like to define multiple service accounts within a single client. The goal is to assign separate capabilities or permissions to each service account under the same client, rather than creating a new client for each service.
I understand that enabling Service Accounts on a client creates a single corresponding user (e.g., service-account-<client_id>). Is there any supported way to have more than one service account tied to the same client, or perhaps an alternative approach to achieve this kind of capability separation?
Any suggestions or best practices to achieve this kind of multi-identity design under a single client would be greatly appreciated.
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.
We’re exploring a setup where we would like to define multiple service accounts within a single client. The goal is to assign separate capabilities or permissions to each service account under the same client, rather than creating a new client for each service.
I understand that enabling Service Accounts on a client creates a single corresponding user (e.g.,
service-account-<client_id>). Is there any supported way to have more than one service account tied to the same client, or perhaps an alternative approach to achieve this kind of capability separation?Any suggestions or best practices to achieve this kind of multi-identity design under a single client would be greatly appreciated.
All reactions