[ 
https://issues.apache.org/jira/browse/DIRSERVER-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986645#comment-13986645
 ] 

Stefan Seelmann commented on DIRSERVER-1974:
--------------------------------------------

Can you please also check the cn attribute with the Apache Directory Studio 
Schema Browser (right-click on the connection, choose "Open Schema Browser")?

But beside of that, I can confirm that there is an issue when using the Studio 
"Rename Entry..." function. If the choosen network provider is the Apache LDAP 
API then the old cn value is kept. Whereas when using JNDI the old cn value is 
deleted. IIRC we automatically set the deleteoldrdn flag, but it seems the flag 
is not sent when the Apache LDAP API is used. I'll investigate that issue.


> Rename Operation Issue - ApacheDS
> ---------------------------------
>
>                 Key: DIRSERVER-1974
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1974
>             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
(v6.2#6252)

Reply via email to