directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-638) Searches with escaped characters in the base DN fail.
Date Sun, 06 Aug 2006 04:09:14 GMT
    [ ] 
Alex Karasulu commented on DIRSERVER-638:

I was handling this before with DN normalization without issue when we were using the old
DN parser.  Antlr productions were handling the conversion of these forms into a normalized
(canonical value).  I'll have to dive into the new normalization code which is hand woven
to add this normalization. 

> Searches with escaped characters in the base DN fail.
> -----------------------------------------------------
>                 Key: DIRSERVER-638
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.0-RC3
>         Environment: ApacheDS 1.0 RC 3
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
> Microsoft Windows XP version 5.1 Service Pack 1
>            Reporter: Stefan Zoerner
>         Assigned To: Alex Karasulu
>         Attachments:
> Searches with escaped characters in the base DN fail. I have created a test entry like
> dn: sn=Ferry,dc=example,dc=com
> objectclass: top
> objectclass: person
> sn: Ferry
> cn: Bryan Ferry
> and perform searches with the following parameters
> 1)
> BASE DN: sn=\46\65\72\72\79,dc=example,dc=com
> Filter: (cn=Bryan Ferry)
> Scope: BASE
> 2)
> BASE DN: sn=#4665727279,dc=example,dc=com
> Filter: (cn=Bryan Ferry)
> Scope: BASE
> In both cases the entry is not found, although it should (see examples in Chapter 5 of
RFC 2253). In example 1 the search base is the DN of the example with "Ferry" escaped with
backslashes. The second example is the same search base, but with the value BER encoded (octet
> An attached JUnit test creates the entry and performs both search ops. It passes with
Sun Java System Directory Server 5.2 but fails with ApacheDS.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message