[GH-ISSUE #872] [BUG] Ldap query to filter user present in two groups is always empty #315

Closed
opened 2026-02-27 08:16:36 +03:00 by kerem · 0 comments
Owner

Originally created by @nitnelave on GitHub (Mar 18, 2024).
Original GitHub issue: https://github.com/lldap/lldap/issues/872

Discussed in https://github.com/lldap/lldap/discussions/868

Originally posted by Celedhrim March 16, 2024
Hello ,

My users are on different groups , correponding level access , but I also want an "enable user" group

The purpose is simple , however is the user groups or level , I can enable / disable them simple by entering them or remove them from this groups.

With an ldap query , It should be something like that :

(&(objectClass=person)(&(memberOf=cn=some_group,ou=groups,dc=my,dc=org)(memberOf=cn=enable_users,ou=groups,dc=my,dc=org)))"

It's work on openldap , but not on lldap , is it a limitation on how lldap handle ldap filter ?

Also I use that to be sure admin , my rw bind user and my ro bind user are not listed has "users that can connect to my app"

thank you

Originally created by @nitnelave on GitHub (Mar 18, 2024). Original GitHub issue: https://github.com/lldap/lldap/issues/872 ### Discussed in https://github.com/lldap/lldap/discussions/868 <div type='discussions-op-text'> <sup>Originally posted by **Celedhrim** March 16, 2024</sup> Hello , My users are on different groups , correponding level access , but I also want an "enable user" group The purpose is simple , however is the user groups or level , I can enable / disable them simple by entering them or remove them from this groups. With an ldap query , It should be something like that : ``` (&(objectClass=person)(&(memberOf=cn=some_group,ou=groups,dc=my,dc=org)(memberOf=cn=enable_users,ou=groups,dc=my,dc=org)))" ``` It's work on openldap , but not on lldap , is it a limitation on how lldap handle ldap filter ? Also I use that to be sure admin , my rw bind user and my ro bind user are not listed has "users that can connect to my app" thank you </div>
kerem closed this issue 2026-02-27 08:16:36 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/lldap-lldap#315
No description provided.