-
Notifications
You must be signed in to change notification settings - Fork 23
Group #1 / member #1: No matching user name found for group member attribute "member" #32
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
Comments
Are you sure you're using the right attributes for groupMemberAttribute? I've just checked on my own Active Directory instance. My "sMAAccountName" is "Adam Reece", but looking at the groups I'm in, "member" refers to my user's whole DN -- not just the username. I would expect that "memberUid" is necessary because that would match what I've got for "sAMAccountName" used by userUniqueAttribute. |
It likely works for me as I have the "Subsystem for UNIX-based Applications" feature installed, so POSIX attributes such as "uid" and "memberUid" are automatically present in my AD. The problem you've got here is that your user's "sMAAccountName" and group's "member" attributes simply don't match identically. You can overrule this behaviour with userMatchAttribute. Specifically this part:
|
Actually, I think it worked. But, the problem is my group has another group in it. So I have GitLab Admins (members -> SDMI Admins)... Is there a way to resolve that group to indiviudal members kind of how I did with my user filter? "memberOf:1.2.840.113556.1.4.1941" The group with just users synced fine. |
heya, have you been able to find out how to work the nesting out? |
When specifying a group DN, it fails to find members of the group. My guess is that the users are not included in the same OU as the GroupDN so it cant find them?
I've removed the groupdn query and it works, but I have a bunch of unwanted groups.
It also works if I specify the group dn to point to an OU with users, and groups that are assigned users.
My config for reference.

The text was updated successfully, but these errors were encountered: