redhat-cop / redhat-cop/group-sync-operator
Azure does not sync member users from nested ad groups if source is not cloud
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 132
- Forks
- 71
- PR merge metrics
- No merged PRs in 30d
Description
We have a Entra ID setup where we have nested groups. For example:
aggregated = group1 + group2
Where group1 and group2 have member users, while aggregated doesn't.
The expectation is that the resulted sync towards OpenShift has all three groups available and that the aggregated group would have the members of both group1 and group2 assigned.
However, we observe that for the aggregated group this only works when its source is 'Cloud'. If the aggregated group source is 'Windows Server AD', it will have no memberships at all.
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 nested Entra ID group setup with the aggregated group's source set to Windows Server AD, then compare it with the Cloud source behavior described in the report. No files or tests are identified in the issue; done means the OpenShift sync includes all three groups and assigns the members of group1 and group2 to aggregated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go, kubernetes
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100