| Summary | ldap searches with * don't work after horde upgrade to 3.0.5 |
| Queue | Turba |
| Queue Version | 2.0.3 |
| Type | Bug |
| State | Not A Bug |
| Priority | 2. Medium |
| Owners | |
| Requester | colonel.flagg (at) hushmail (dot) com |
| Created | 09/06/2005 (7275 days ago) |
| Due | |
| Updated | 09/07/2005 (7274 days ago) |
| Assigned | 09/06/2005 (7275 days ago) |
| Resolved | 09/07/2005 (7274 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
characters we need to encode them.
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.
State ⇒ Not A Bug
characters we need to encode them.
name, or are you expecting it to work as a wildcard?
State ⇒ Feedback
name, or are you expecting it to work as a wildcard?
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ ldap searches with * don't work after horde upgrade to 3.0.5
Queue ⇒ Turba
changed the behavior of ldap searches with a * in the search string.
3.0.5 replaces the * in the search string with the hex \2A.
colonel*flagg becomes colonel\2Aflagg.
WORKS: turba-h3-2.0.3 + horde-3.0.4
Aug 15 12:27:06 ldapserver slapd[25691]: [ID 902418 local4.debug]
conn=145864
op=2 SRCH base="o=example.com" scope=2
filter="(&(cn=*colonel*flagg*))"
Aug 15 12:27:06 ldapserver slapd[25691]: [ID 902418 local4.debug]
conn=145865
op=1 SRCH base="uid=cflagg,ou=People,o=example.com" scope=0
filter="(|(objectClass=top)(objectClass=person)(objectClass=organiza
tionalPerson)(objectClass=inetOrgPerson))"
BROKEN: turba-h3-2.0.3 + horde-3.0.5
Aug 15 12:26:42 ldapserver slapd[25691]: [ID 902418 local4.debug]
conn=145860
op=1 SRCH base="o=example.com" scope=2
filter="(&(cn=*colonel\2Aflagg*))"