[Tickets #2563] RESOLVED: ldap searches with * don't work after horde upgrade to 3.0.5

Wed Sep 7 06:54:42 PDT 2005

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=2563
-----------------------------------------------------------------------
 Ticket             | 2563
 Updated By         | colonel.flagg at hushmail.com
 Summary            | ldap searches with * don't work after horde upgrade to 3.0.5
 Queue              | Turba
 Version            | 2.0.3
 State              | Bogus
 Priority           | 2. Medium
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------

colonel.flagg at hushmail.com (2005-09-07 06:54) wrote:

> That was inadvertant behavior. To correctly match * and other special 
> characters we need to encode them.
We have cn (name) with middle initials in them in our ldap database.  A
search for 'cn=colonel flagg' fails and 'cn=colonel*flagg' succeeds if my cn
is 'colonel p. flagg.'  We have an existing install of horde-2.1 and
turba-1.1 which also behaves this way and a large user base used to this
behavior.  In the new order, is there a way for users to specify a * in the
search box and mean 'wildcard?'  I can't find a way to escape it.