Skip to content
This repository has been archived by the owner on Nov 16, 2022. It is now read-only.

KEYCLOAK-17096 Added Groups functionality #369

Closed
wants to merge 1 commit into from
Closed

KEYCLOAK-17096 Added Groups functionality #369

wants to merge 1 commit into from

Conversation

KaiReichart
Copy link

JIRA ID

KEYCLOAK-17096

Additional Information

This PR adds the functionality of creating and managing Keycloak Groups and assignment of Roles (Realm & Client) to Groups.

Checklist:

added role

edited test

added groups

changed subgroup

fixed subgroups

edited test

added roles

Signed-off-by: Kai Reichart <[email protected]>

fixed json naming

initialized array

bugfix

updated README & tests
@vmuzikar
Copy link
Contributor

vmuzikar commented Aug 17, 2021

@KaiReichart Thank you for your contribution! I'm afraid we do not want to represent each Keycloak resource as a CR. That way it'd soon became a bit chaotic and very hard to manage and implement (with all the dependencies of resources between each other). Therefore, I'm going to close this PR.

Please use keycloak-dev ML to discuss any implementation details. See also the contribution guide.

Thank you for your understanding.

@vmuzikar vmuzikar closed this Aug 17, 2021
@pingwin
Copy link

pingwin commented Apr 11, 2022

If managing a group CRD isn't happening, then what is the supported method for managing groups?

@vmuzikar
Copy link
Contributor

Hello, we're currently developing a new operator from scratch. The approach around CRDs will be different there. The operator won't be managing Keycloak resources directly through the REST API, but will leverage the static (read-only) configuration capabilities coming from the new Store.X. This should most probably include groups as well.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants