[DIRSERVER-297] NormalizationService is failing to parse escaped names

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Assignee: Alex Karasulu
• Reporter: Giamma
• Created: 06/Jul/05 07:37
• Updated: 21/Apr/07 11:13
• Resolved: 25/Aug/05 06:35

Description

I wrote a custom partition to extract data from our oracle database.
Some of the names returned from out db needs to be escaped because they have special chars like: "," "/" and "="
This is done using LdapName.escapeAttributeValue().

Unfortunately the DnParser (in NormalizationService) is not doing the right thing when processing these escaped names.

I had to change the code in NormalizationService to still call the parser (to check invalid DN syntax) but I skipped
using the text returned by the parser because it would remove spaces after an escaped ","

Let's say I have a RDN like this:
"ou=some test, something else"

After I escaped it it wil be like this:
"ou=some test
, something else"

The parser will remove the space after the escaped ","
"ou=some test
,something else"

And that breaks the code in my custom partition because it's not finding the right object.

Here is the fix I made.
But it's just an hack. I think the problem is in the DnParser. But I do not have the source for that.

protected void process( NextInterceptor nextInterceptor, Delete call ) throws NamingException
{
synchronized( parser )

{ // call.getName( parser.parse( call.getName().toString() ) ); // call it anyway to catch invalid DN syntax parser.parse( call.getName().toString() ); }

super.process( nextInterceptor, call );
}