directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <>
Subject [jira] Closed: (DIREVE-46) Create DN Normalizer IBC
Date Tue, 29 Mar 2005 01:14:17 GMT
     [ ]
Alex Karasulu closed DIREVE-46:

     Resolution: Fixed
    Fix Version: 0.9

Committed new NormalizerService on revision 159316 here:

> Create DN Normalizer IBC
> ------------------------
>          Key: DIREVE-46
>          URL:
>      Project: Directory Server
>         Type: Task
>   Components: interceptors
>     Reporter: Alex Karasulu
>     Assignee: Alex Karasulu
>      Fix For: 0.9

> We need to normalize distinguished names while performing backend operations.  At this
point the nexus and context partitions presume this is already being done and we use specific
arguments when they would like unnormalized distinguished names.  The unnormalized name is
often referred to as the UPDN or User Provided Distinguished Name. 
> Basically we must store the UPDN and the Normalized DN (NDN) in order to correctly look
up and return values as they were given to us.  This is a result of possible variations in
case and whitespace within a distinguished name as it is given across operations and users.
> The DN Normalization IBS (interceptor based service) will need to depend upon the schema
subsystem to correctly normalized DNs.  Schema info is needed when normalizing the values
of individual name components.  For example some name component value might be a case sensitive
string.  If so we cannot normalize by reducing case as we would case insensitive attribute
values in the DN.  Hence we need to lookup attributeType information to determine the equality
matching rules hence normalizers to use for that attribute while normalizing values.
> The DN normalization IBS needs to alter Name and String arguments for distinguished names
provided to PartitionNexus methods.  This must be done within the before interceptor chain.
> The IBS can also serve as a centralized name cache so repeated normalization need not
occur.  This however may automatically be handled by the underlying attribute value normalizers
used by the DN normalizer.  We can figure all this out later after getting the baseline up.

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