Repository navigation
Replies: 1 comment 2 replies
|
As a starting point, I would like to know which use cases from https://datatracker.ietf.org/doc/html/rfc7642#section-3 you are interested in. The initial scope being defined for this feature will focus on I can also see interest in |
|
Spot on - the "Migration of the Identities" use cases are exactly what we need. It would be incredibly valuable if KC enabled these use cases natively, eliminating the need for third-party libraries. They serve their purpose, and I have great respect for the power of these extensions, but in large projects/enterprises, there is always discussion about risk assessment, maintenance, and reliability of these extensions, which prevent or at least complicate widespread adoption. |
|
At lasuite.coop we have interest in the most basic use case, which is the centralized management of users at Keycloak, and the creations, updates and deletions being broadcasted instantly among the services plugged to Keycloak. I think the referenced use case which is the most comparable would be "Provisioning of User Accounts for a Community of Interest". |
Uh oh!
There was an error while loading. Please reload this page.
The team is starting work on a new feature to enable federating users from a SCIM provider. For an overview of our goals, use cases, and requirements, please refer to the following issue:
We've received significant interest in SCIM support for Keycloak, and our first step will be to enable realms as SCIM Clients. This will allow various resource types to be synced with a SCIM Service Provider (CSP).
This initiative is linked to important community discussions and contributions. Please check the References section in the issue for more details. We encourage you to share any additional issues or discussions you believe are relevant, as these will be crucial for gathering further use cases and requirements, and will help us define the design and roadmap for this feature.
All reactions