Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure does not sync member users from nested ad groups if source is not cloud #317

Open
of-vincentvandam opened this issue May 16, 2024 · 3 comments

Comments

@of-vincentvandam
Copy link

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.

@sabre1041
Copy link
Collaborator

@of-vincentvandam is this an issue related to Group Sync Operator or a does it affect how users are allocated to groups within Entra ID?

@of-vincentvandam
Copy link
Author

The problem is with the syncing. The groups work fine with other integrations (that do not rely on retrieving the groups). My guess (since Entra ID itself is a black box), is that the member requests for these groups are federated and therefor they don't end up when doing a ItemTransitiveMembersRequest.

@sabre1041
Copy link
Collaborator

@of-vincentvandam i do not know offhand

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

No branches or pull requests

2 participants