redhat-cop / redhat-cop/group-sync-operator
Name collision when synchronizing sub groups from Keycloak
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 132
- Forks
- 71
- PR merge metrics
- No merged PRs in 30d
Description
Keycloak does not ensure uniqe group names for sub groups.
When synchronized to OpenShift the behaviour is random.
Preconditions
Given the following group strucutre in Keyckloak:
"""
* group-a
** sub-group
* group-b
** sub-group
"""
And a user named "user-a" asigned to group "group-a/sub-group"
And a user named "user-b" asigned to group "group-b/sub-group"
When the groups are sync with the option "scope" set to "sub"
Observation
Then there are the following groups:
"""
* group-a
* group-b
* sub-group
"""
And the user list of "sub-group" contains "user-a"
Or the user list of "sub-group" contains "user-b"
Note that the bahaviour is random. Depending on unknown conditions, users are synced from either "group-a/sub-group" or "group-b/sub-group".
Expectations
Then there are the following groups:
"""
* group-a
* group-b
* group-a-sub-group
* group-b-sub-group
"""
And the user list of "group-a-sub-group" contains "user-a"
And the user list of "group-b-sub-group" contains "user-b"
In the above - got used as a separator to prepend the parents group name. I suggest to have this configurable.
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
Start by reproducing the Keycloak synchronization scenario with the option "scope" set to "sub", using duplicate subgroup names under different parents. Trace the group-name generation and configuration entry points, then verify that parent-qualified names preserve both users and that the separator is configurable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100