Skip to content

dsidm role rename-by-dn does not rename a role #6501

Closed

Description

@mirielka

Version-Release number of the selected component
389-ds-base-3.0.5-2.el10.x86_64

Steps to reproduce

  1. Create a role (e.g. managed)
  2. Try to rename a role using "dsidm role rename-by-dn"
  3. Check for original/renamed role

Actual results

Message about successful rename is produced but with the original dn, and the entry still exists only under the original dn.

# dsidm localhost -b dc=example,dc=com role create-managed
Enter value for cn : test_role
Successfully created test_role

# dsidm localhost -b dc=example,dc=com role list
test_role

# dsidm localhost -b dc=example,dc=com role get test_role
dn: cn=test_role,dc=example,dc=com
cn: test_role
description: test
objectClass: nsSimpleRoleDefinition
objectClass: nsManagedRoleDefinition
objectClass: nsRoleDefinition
objectClass: ldapSubEntry
objectClass: top

# dsidm localhost -b dc=example,dc=com role rename-by-dn cn=test_role,dc=example,dc=com cn=renamed,dc=example,dc=com
Successfully renamed to cn=test_role,dc=example,dc=com 

# dsidm localhost -b dc=example,dc=com role list
test_role

# dsidm localhost -b dc=example,dc=com role get test_role
dn: cn=test_role,dc=example,dc=com
cn: test_role
description: test
objectClass: nsSimpleRoleDefinition
objectClass: nsManagedRoleDefinition
objectClass: nsRoleDefinition
objectClass: ldapSubEntry
objectClass: top

# dsidm localhost -b dc=example,dc=com role get-by-dn cn=renamed,dc=example,dc=com
Error: No such object

Expected results
Role should have new cn and dn.

Additional information
Output is the same when using the keep-old-rdn option - no changes are made.

Activity

  1. self-assigned this
    on Apr 14, 2025
  2. mreynolds389 commented on Apr 15, 2025

    @mreynolds389
    Contributor

    3e211e4..9c2b4f1 389-ds-base-3.0 -> 389-ds-base-3.0
    672e92e..dbe991f 389-ds-base-2.6 -> 389-ds-base-2.6
    e8381f1..d3a1052 389-ds-base-2.5 -> 389-ds-base-2.5
    00527c4..550d0d7 389-ds-base-2.4 -> 389-ds-base-2.4
    a9626e3..ae7a76c 389-ds-base-2.3 -> 389-ds-base-2.3
    e25be4b..750ae7b 389-ds-base-2.2 -> 389-ds-base-2.2
    fdd419a..ff2651a 389-ds-base-1.4.3 -> 389-ds-base-1.4.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

needs triageThe issue will be triaged during scrum

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions