redhat-cop / redhat-cop/group-sync-operator
Keycloak recursive subgroup sync problem
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 132
- Forks
- 71
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
Since 0.017, and the "Update dependencies" modification, we observe some problem with sync between group-sync and our Keyclock.
Here our Keyclock group definition :
- group1
-- group1subgroup1
-- group1subgroup2
-- group1subgroup3 - group2
-- group2subgroup1
-- group2subgroup2
-- group2subgroup3
So before 0.0.17 all group and subgroup was correctly sync in Openshift.
After 0.0.17, only 1 subgroup of each group are update, and it seems to always be the last in hierarchy_children annotation.
Example :
group1's annotation -> hierarchy_children: group1subgroup1,group1subgroup2,group1subgroup3
Only group1subgroup3 is updated.
group1subgroup1, group1subgroup2 and group1 are not anymore.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the sync with the shown group1/group2 hierarchy and hierarchy_children annotation, comparing behavior before and after 0.0.17. Trace the recursive group synchronization entry point and determine why only the last child is updated. Done means all listed groups and subgroups synchronize into OpenShift as they did before 0.0.17, with a regression test covering multiple children.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authorization, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100