directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] [Commented] (DIRSERVER-1974) Rename Operation Issue - ApacheDS
Date Thu, 01 May 2014 14:36:18 GMT


Emmanuel Lecharny commented on DIRSERVER-1974:

No matter what your images are showing, cn *is* a multi-valued attribute. It's clearly explicited
in RFC 4519 : :

"2.3. 'cn'
   The 'cn' ('commonName' in X.500) attribute type contains names of an
   object.  Each name is one value of this *multi-valued* attribute."

A single-value attribute will contain the SINGLE-VALUE flag in its description, like :

attributetype ( 
	NAME 'entryUUID' 
	DESC 'UUID of the entry' 
	EQUALITY uuidMatch 
	ORDERING uuidOrderingMatch 
	SINGLE-VALUE                          <-----
	USAGE directoryOperation 

cn description is : 

attributetype ( 
	NAME ( 'cn' 'commonName' ) 
	DESC 'RFC2256: common name(s) for which the entity is known by' 
	SUP name 
	EQUALITY caseIgnoreMatch 
	SUBSTR caseIgnoreSubstringsMatch 

Now, you'd better follow Kiran's advice about the deleteOldRdn.

And it's not our fault if LdapADMIN GUI expose the cn as a single-value attribute type. Just
switch to Apache Directory Studio to have a decent LDAP GUI... (

> Rename Operation Issue - ApacheDS
> ---------------------------------
>                 Key: DIRSERVER-1974
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: ldap
>    Affects Versions: 2.0.0-M15
>         Environment: Window server 2008 R2
>            Reporter: Mohd Usman
>            Assignee: Kiran Ayyagari
>              Labels: build, features, patch
>         Attachments: CNAttributeInSchema.png, PostRename.png, PreRename.png, SchemaViewerLDAPAdminTool.png
>   Original Estimate: 168h
>  Remaining Estimate: 168h
> Whenever we perform Rename operation on an object entry (let’s say Person object),
the person gets renamed successfully but the issue is that the old value of the person object
still remains.
> The ‘cn’ attribute contains two values now - old value and also the new value.
> Example:
> I have created a person object with DN "cn=person,ou=Apache,dc=example,dc=com" and I
want to rename this entry to "cn=person_Rename,ou=Apache,dc=example,dc=com".
> The rename operation executes successfully and the person is renamed to "cn=person_Rename,ou=Apache,dc=example,dc=com".

> But, the ‘cn’ attribute now contains 
> “person”
> “person_Rename”.
> When verified the schema, ‘cn’ attribute show as ‘single valued’ but after performing
the rename operation – the ‘cn’ becomes ‘multi-valued’ and contains two values.
> This an issue with Apache directory which needs to be resolved. Also find the screenshots
attached for your reference. Please look into the same.

This message was sent by Atlassian JIRA

View raw message