Affects Version/s: 2.6.0
Fix Version/s: 3.0.0
Component/s: core server
Environment:This is seen both when sending queries over the LDAP protocol and when using ldapsearch on the command line (running under Bash/Ubuntu).
This was seen in version 2.6.0, but not 2.5.1. I have not verified against newer versions.
When using a target string in a VLV search that contains compound characters (eg. ü or ñ), the result does not match the request unless the string is normalized by the client to Unicode NFKD form.
Some output from a small test program, which searched among usernames in our database:
Finding ä (not normalized)
Finding ä (NFKD)
Finding ã (not normalized)
Finding ã (NFKD)
Disregarding the normalization or lack of it, the ldapsearch parameters equivalent to the program above would be:
ldapsearch -b "ou=users,dc=mydomain,dc=com" -s one -S cn -G 0:1:ä "objectclass=myUserClass" cn