Summary | complex ldap filter does not work |
Queue | Turba |
Queue Version | 2.0.1 |
Type | Bug |
State | Not A Bug |
Priority | 1. Low |
Owners | Horde Developers (at) |
Requester | max-4004 (at) terragate (dot) net |
Created | 02/27/2005 (7452 days ago) |
Due | |
Updated | 03/03/2009 (5987 days ago) |
Assigned | 03/05/2005 (7446 days ago) |
Resolved | 03/06/2005 (7445 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
Please reopen this ticket as a bug because something like
objectClass=top)(objectClass=person)(objectClass=organizationalPerson
(which works) is really not a filter (as described by RFC2254).
By the way, someone may say "use objectClass array instead". The
problem is that this array is ORed by the function
_buildObjectclassFilter (in lib/Driver/ldap.php) which is really
counter-intuitive.
State ⇒ Not A Bug
it'll work fine then. There was an error when the filter was bad that
we weren't handling; it's fixed now. So with your filter unchanged
you'll see an error message now.
with filter (|(cn=*)(mail=*)) I get just one result with name "AA" and
email "A"
with filter xyz (nosens) I get the same "A" result
The "A" result does not exist in LDAP and cannot be edit or viewed
I am using openldap 2.2.23 maybe the ldapd is the problem, I dont know.
I change my ldap schema, so I dont need the complex filter anymore.
THX for great work and support
State ⇒ Feedback
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ complex ldap filter does not work
Queue ⇒ Turba