-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
False
-
-
False
Customer has successfully configured users and groups using Keycloak, and they are appearing correctly in the Backstage catalog. However, both users and groups are currently being placed under the default namespace.
Customer would like to configure the setup so that:
1) Users should remain in the default namespace.
2) Groups should be created under a custom, organization-based namespace.
Is there a supported way to achieve this behaviour through configuration? If so, could you please provide guidance or an example?
BUSINESS IMPACT: Customer has multiple sources of groups configured (git, keycloak, catalog provider), which helps provide clarity, reduce the risk of conflicts, and enables the implementation of RBAC based on group structures.
Customer's latest request:
We have a requirement to support catalog groups and user management from both GitHub and Keycloak. Relying solely on GitHub, especially across multiple organizations, does not meet our needs.