Repository navigation
Replies: 1 comment
|
Kind reminder? :) Still having this issue, 1.5 years later |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8000
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Uh oh!
There was an error while loading. Please reload this page.
Hi. This is a simplified version of the configuration I'm trying to make.
We have 2 resource servers, each with its own clients configured in Keycloak:
FIRSTandSECOND, each owned by a different teamWe would like each team to configure own client settings and authorization rules using the service account.
We would like that teams cannot change settings belonging to other teams' clients
In order to satisfy these requirements we have enabled fine grained permissions on each client.
This has created some permissions inside
realm-managementclient which I can edit to suit my needs.By creating and adding
Is first clientpolicy to the following permissions:and
Is second clienttoi am able to get to 50% of where I want: Each team can use client credentials grant and the client service account to modify settings in their clients, without being able to change clients belonging to other teams
The problem is that these settings do not control the Authorization tab: Service accounts can create resources and scopes, but NOT policies and permissions
In order for service accounts to be able to edit policies and permissions, the closest I got was to map the role:
realm-management->manage-authorizationto the service accounts.But the problem is this enables service accounts to edit ANY client authorization settings, not just own so it is a no-go for us
I think there should be a fine grained permission for "configure authorization" or the authorization should be covered by the "manage" and potentially "configure" permissions.
I do not know if this is a bug, lack of feature or I just understand the system wrong, but I believe my use case is genuine: I jut want teams inside my company have full control over their clients.
Additional considerations:
Why I'm using the service account instead of some user: We want to use client credentials because the settings will never be updated by hand. Instead they will be created programmatically via migration-like scripts which will ensure 100 reproducibility of configuration
We do not want configuration to be centralized under a single ADMIN team for security reasons
Teams are defensive with their clients which may include sensitive data such as voucher codes.
All reactions