Issue #209 has been updated by Jonathan Clarke. Status changed from Feedback to Assigned % Done changed from 100 to 50
Jonathan Clarke wrote: > I had another look at this issue, in light of #252 (Error deleting entry with > a suffix containing a space). I've written a fix that allows to write a LDAP > URL in lsc.properties containing a space or accents (just committed). Just found a problem with my fix: it no longer allows you to use serveral URLs (to have server redundancy). This would be a regression, so needs more work I guess ! ---------------------------------------- Bug #209: Bad URL parsing http://tools.lsc-project.org/issues/209 Author: Raphaël Ouazana Status: Assigned Priority: Normal Assigned to: Jonathan Clarke Category: Core Target version: 1.2.1 Problem in 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
