Uploaded image for project: 'Directory ApacheDS'
  1. Directory ApacheDS
  2. DIRSERVER-1974

Rename Operation Issue - ApacheDS

Attach filesAttach ScreenshotWatch issueCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • 2.0.0-M15
    • 2.0.0.AM26
    • jdbm, ldap
    • Window server 2008 R2

    Description

      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.

      Attachments

        1. ApacheDSSchemaBrowser.png
          95 kB
          Mohd Usman
        2. CNAttributeInSchema.png
          98 kB
          Mohd Usman
        3. PostRename.png
          106 kB
          Mohd Usman
        4. PreRename.png
          103 kB
          Mohd Usman
        5. SchemaViewerLDAPAdminTool.png
          59 kB
          Mohd Usman

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            mdusman Mohd Usman
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 168h
                168h
                Remaining:
                Remaining Estimate - 168h
                168h
                Logged:
                Time Spent - Not Specified
                Not Specified

                Slack

                  Issue deployment