Issue #224 has been updated by Jonathan Clarke.

Target version set to 1.2.1
Version set to 1.

Raphaël Ouazana wrote:
> Ok, so here is a patch.

Great, thanks!

> Finally I have modified the code only where it is important for me, but I 
> think similar modifications must be done at many places (each time a call to 
> ctx.search/ctx.lookup/etc. is done).

Yes, I've written some tests and found some more places where a patch was 
needed.

My latest work is committed in branches 1.2, 1.3 and trunk, including some new 
tests to detect this problem. You can test 

----------------------------------------
Bug #224: Bad handling of / character in RDN
http://tools.lsc-project.org/issues/224

Author: Raphaël Ouazana
Status: New
Priority: Normal
Assigned to: 
Category: 
Target version: 1.2.1
Version: 1.


Hi,

LSC seems to handle incorrectly the slash character (/). In some cases I get 
the following message:
Error while reading entry "ou=bla / bla",o=bla: 
javax.naming.InvalidNameException: "ou=bla / bla",o=bla: close quote appears 
before end of component

Note the oddly added quotes.

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

Reply via email to