Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-62874

dsidm: issue when renaming users

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Minor Minor
    • rhel-10.1
    • None
    • 389-ds-base
    • 389-ds-base-3.1.3-2.el10
    • No
    • Low
    • rhel-idm-ds
    • 0
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None

      Description of problem:
      When you rename a user, dsidm runs a search to get the DN of the entry to rename:
      [28/Apr/2021:12:51:30.545119227 +0200] conn=9 op=2 SRCH base="ou=people,dc=example,dc=com" scope=2 filter="(&(&(objectClass=nsPerson)(objectClass=nsAccount)(objectClass=nsOrgPerson)(objectClass=posixAccount))(|(uid=zzz)(displayName=zzz)(cn=zzz)))" attrs="distinguishedName"
      Once it gets it, it runs modrdn. The problem is that after rename other attributes like cn are still the same
      It should not look for cn or displayName

      How reproducible:
      Always

      Steps to Reproduce:
      1. Create a user:

      1. dsidm -D "cn=Directory manager" -w password instance_name -b "dc=example,dc=com" user create
        Enter value for uid : zzz
        Enter value for cn : zzz
        Enter value for displayName : zzz
        Enter value for uidNumber : 123
        Enter value for gidNumber : 123
        Enter value for homeDirectory : /home/zzz
        Successfully created zzz

      2. Rename the user:

      1. dsidm -D "cn=Directory manager" ldap://server.example.com -b "dc=example,dc=com" user rename zzz yyy
        Enter password for cn=Directory manager on ldap://server.example.com:
        Successfully renamed to uid=yyy,ou=people,dc=example,dc=com

      3. Run the same command command again:

      1. dsidm -D "cn=Directory manager" ldap://server.example.com -b "dc=example,dc=com" user rename zzz yyy
        Enter password for cn=Directory manager on ldap://server.example.com:
        Successfully renamed to uid=yyy,ou=people,dc=example,dc=com

      Actual results:
      The 2nd rename command is successful.

      Expected results:
      The 2nd rename command should fail, because the user is no longer named zzz at this point.

      Additional info:

      1. dsidm -D "cn=Directory manager" ldap://server.example.com -b "dc=example,dc=com" user rename zzz yyy
        Enter password for cn=Directory manager on ldap://server.example.com:
        Successfully renamed to uid=yyy,ou=people,dc=example,dc=com
      1. dsidm -D "cn=Directory manager" ldap://server.example.com -b "dc=example,dc=com" user rename zzz yyy
        Enter password for cn=Directory manager on ldap://server.example.com:
        Successfully renamed to uid=yyy,ou=people,dc=example,dc=com
      1. dsidm -D "cn=Directory manager" ldap://server.example.com -b "dc=example,dc=com" user rename zzz yyy
        Enter password for cn=Directory manager on ldap://server.example.com:
        Successfully renamed to uid=yyy,ou=people,dc=example,dc=com
      1. dsidm -D "cn=Directory manager" ldap://server.example.com -b "dc=example,dc=com" user rename yyy xxx
        Enter password for cn=Directory manager on ldap://server.example.com:
        Successfully renamed to uid=xxx,ou=people,dc=example,dc=com
      1. dsidm -D "cn=Directory manager" ldap://server.example.com -b "dc=example,dc=com" user rename yyy xxx
        Enter password for cn=Directory manager on ldap://server.example.com:
        Error: No object exists given the filter criteria yyy
      1. dsidm -D "cn=Directory manager" ldap://server.example.com -b "dc=example,dc=com" user rename zzz yyy
        Enter password for cn=Directory manager on ldap://server.example.com:
        Successfully renamed to uid=yyy,ou=people,dc=example,dc=com

              spichugi@redhat.com Simon Pichugin
              mmuehlfe@redhat.com Marc Muehlfeld
              IdM DS Dev IdM DS Dev
              IdM DS QE IdM DS QE
              Evgenia Martyniuk Evgenia Martyniuk
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: