radiatejava wrote: > I am using openldap client library 2.4.44 on Centos 7.3, LDAP v3 > setting. I am having an issue with LDAP bind when the DN has encoded > representation of special characters like é (e acute). Actual DN is > CN=mithun,OU=Groupes de Sécurité,DC=mytest,DC=net and when it is sent > by the app (frontend) to our backend, it is coming as > CN=mithun,OU=Groupes de S\u00e9curit\u00e9,DC=insaaadev,DC=net. > Basically, é comes encoded as \u00e9 which is as per the encoding > mentioned here https://www.fileformat.info/info/unicode/char/e9/index.htm
That is not a valid encoding for LDAP. Read RFC4511. > > To further try out, I directly hardcoded the DN to > CN=mithun,OU=Groupes de S\u00e9curit\u00e9,DC=mytest,DC=net and that > worked fine. I want to understand why it fails when the DN in the same > format comes from the frontend app. Appreciate your help, thanks. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/
