Description of problem: Sample entry: dn: CN=Lu\C4\8Di\C4\87, dc=bug199923,dc=com objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetOrgPerson sn: I18n uid: I18n userPassword: I18n seeAlso: CN=Lu\C4\8Di\C4\87, dc=bug199923,dc=com If the value in the filter is made from real characters, it returns the expected entry: ldapsearch -b "CN=Lu\C4\8Di\C4\87, dc=bug199923,dc=com" -e 'seeAlso=CN=Lučić,dc=bug199923,dc=com' seeAlso dn: CN=Lučić,dc=bug199923,dc=com seeAlso: CN=Lučić,dc=bug199923,dc=com On the other hand, if it contains the escaped representation as follows, it returns none: ldapsearch -1 -h kiki.usersys.redhat.com -p 10389 -D 'cn=directory manager' -w Secret123 -b "CN=Lu\C4\8Di\C4\87, dc=bug199923,dc=com" -e 'seeAlso=CN=Luči\\C4\\87, dc=bug199923,dc=com'
It's a test problem. Not a bug...