Issue #224 has been updated by Raphaël Ouazana.
File fixSlashInDn.diff added
% Done changed from 0 to 50
Ok, so here is a patch. Note that I had to handle explicitly the empty DN case,
else tests are not passing and LSC can't run. An alternate method is to use a
NameParser like that:
<pre>
NameParser ldapParser = ctx.getNameParser("");
Name nBase = ldapParser.parse(rewriteBase(base));
</pre>
But that doesn't work for the dn I get from JNDI. To be more consistent I use
CompositeName everywhere.
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).
Regards,
Raphaël Ouazana.
----------------------------------------
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:
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
