You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
unless other LDAP servers, Active Directory supports nested groups and a way to query them using regular LDAP clients by entering special "OID" strings in the LDAP filter. I.e. an ldapsearch query like this against an Active Directory would return a list of users that are either directly members of the group testgroup or are member of a group that is nested into testgroup (directly or indirectly):
Is it possible to somehow use such an LDAP filter in auth-ldap.cnf? I'm confused how the combination of RequireGroup, Group -> BaseDN, Group -> Search Filter and Group -> MemberAttribute lead to the actual LDAP query. Is there any setting where I could enter the memberof:1.2.840.113556.1.4.1941:=<groupname> string?
unless other LDAP servers, Active Directory supports nested groups and a way to query them using regular LDAP clients by entering special "OID" strings in the LDAP filter. I.e. an
ldapsearch
query like this against an Active Directory would return a list of users that are either directly members of the grouptestgroup
or are member of a group that is nested intotestgroup
(directly or indirectly):ldapsearch -h mydomaincontroller.mydomain.local -x -b "DC=mydomain,DC=local" -D "CN=myauthuser,OU=USERS,DC=mydomain,DC=local" -w mypassword "(&(objectCategory=user)(memberof:1.2.840.113556.1.4.1941:=CN=testgroup,OU=GROUPS,DC=mydomain,DC=local))"
Is it possible to somehow use such an LDAP filter in
auth-ldap.cnf
? I'm confused how the combination ofRequireGroup
,Group -> BaseDN
,Group -> Search Filter
andGroup -> MemberAttribute
lead to the actual LDAP query. Is there any setting where I could enter thememberof:1.2.840.113556.1.4.1941:=<groupname>
string?See here for the AD search syntax specs:
https://msdn.microsoft.com/en-us/library/windows/desktop/aa746475(v=vs.85).aspx
Many thanks in advance.
The text was updated successfully, but these errors were encountered: