directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <>
Subject [jira] Commented: (DIREVE-137) Problems with mixed-case in suffix
Date Wed, 02 Mar 2005 14:16:49 GMT
     [ ]
Alex Karasulu commented on DIREVE-137:

Good catch - I've been working on trying to figure out how we can fix this for good.  Looks
like we're really exposed in several ways.  I was going to fix this with a Normalization interceptor
service but I backed out for some reason.  I'll take another look at doing this later ....

For the time being I fixed the first point you have made about the normalizated mismatch by
adding the normalized name to the JdbmDatabase constructor.


> Problems with mixed-case in suffix
> ----------------------------------
>          Key: DIREVE-137
>          URL:
>      Project: Directory Server
>         Type: Bug
>   Components: jdbm database, jndi-provider, server main
>     Versions: 0.8
>     Reporter: Endi S. Dewata
>     Assignee: Alex Karasulu
>     Priority: Minor
>  Attachments: mixed-case.patch
> The server currently has some problems with suffixes that contain mixed cases, e.g. dc=VergeNet,
> 1. Add
> ------
> In line #630, JdbmDatabase is initialized with un-normalized
>     Database db = new JdbmDatabase( upSuffix, wkdir );
> But in line #673, when adding an entry to the database, the suffix
is compared with the normalized dn of the new entry.
>     if ( dn.equals( suffix ) )
> This is causing the add operation to fail.
> 2. Search
> ---------
> In line #203, the suffix is being normalized during registration.
>     backends.put( backend.getSuffix( true ).toString(), backend );
> However, in line #556, the dn used to look up the backend is not normalized.
>     return ( ContextPartition ) backends.get( clonedDn.toString() );
> This is causing the search operation to fail.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message