Repository navigation
Separation of use:
#15318
Replies: 1 comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
In the new interface, and the documentation that goes with it, several operations have been removed from the console and require disk access.
the import of provider for example.
But this is not always possible.
In large structures, the Keycloak platform is shared.
the platform administrator has access to the disk but does not take care of the contents of the realms.
application or service managers have access to their realms but not to the disk.
In this mode of operation when an application manager wants to use keycloak he makes a request, the platform administrator creates a realm with access for the application manager and it is the latter who must configure his realm accordingly of his needs. but it cannot import (as in previous versions) some elements. for that he would have to have access to the machine.
This regression in usage is particularly restrictive because the manager of a realm must systematically ask the keycloak host to do the work.
All reactions