Fri, 10 Apr 2026 19:28:25 +0000 https://bugs.horde.org/ticket/1448 complex ldap filter does not work a ldap filter like " 'filter' => '(|(cn=*)(mail=*))' " does not work. Sun, 27 Feb 2005 17:23:23 +0000 https://bugs.horde.org/ticket/1448#t5851 Please define "does not work" Sat, 05 Mar 2005 03:34:48 +0000 https://bugs.horde.org/ticket/1448#t6034 With filter "cn=*" I get normal results 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 Sun, 06 Mar 2005 11:09:21 +0000 https://bugs.horde.org/ticket/1448#t6066 You need to remove the outer set of parentheses from your filter - 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. Sun, 06 Mar 2005 22:29:25 +0000 https://bugs.horde.org/ticket/1448#t6118 Hello, 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. Tue, 03 Mar 2009 15:56:34 +0000 https://bugs.horde.org/ticket/1448#t52864