Issue #209 has been updated by Raphaël Ouazana.
Jonathan Clarke wrote: > Regarding spaces in the search base, this is documented :-) > http://lsc-project.org/wiki/documentation/1.2/configuration/service#src_dst_.java.naming.provider.url Wow... ok :) > Regarding the URL encoding, does this change if your lsc.properties file is > encoded in UTF8 or iso8859-1? My lsc.properties (as all my system) is in UTF8. If I convert my lsc.properties to iso8859-1, the bind is rejected... And finally if I force the bind to be correct, the search is still refused. ---------------------------------------- Bug #209: Bad URL parsing http://tools.lsc-project.org/issues/show/209 Author: Raphaël Ouazana Status: New Priority: Normal Assigned to: Category: Target version: Hi, When LSC try to parse an LDAP URL, there are at least two errors: - spaces are misinterpreted; - URL is encoded in iso8859-1 instead of UTF8. Eg. .url = ldap://localhost/o=Mon Père will try to take the base DN "o=Mon" Then if I replace the space by the matching LDAP encoding: .url = ldap://localhost/o=Mon\\20Père I can see in the log of my LDAP server that the accent has been sent in iso8859-1. Workaround: .url = ldap://localhost/o=Mon\\20P\\c3\\a8re But that's not there user-friendly... Note that I had no similar problem with .principal. Regards, Raphaël Ouazana. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
