directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mohd Usman (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DIRSERVER-1974) Rename Operation Issue - ApacheDS
Date Thu, 01 May 2014 13:56:19 GMT

     [ https://issues.apache.org/jira/browse/DIRSERVER-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mohd Usman updated DIRSERVER-1974:
----------------------------------

    Attachment: CNAttributeInSchema.png

CN attribute configuration in Schema

> 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
>
>   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)

Mime
View raw message