Issue Description dsidm fails when users or groups are not in the hardcoded locations "ou=people,SUFFIX" and "ou=groups,SUFFIX" Create a suffix with no "orgnaizationalunits" and try and create a user # dsidm instance_name -b "dc=example,dc=com" user create Enter value for uid : example Enter value for cn : example Enter value for displayName : example Enter value for uidNumber : 1234 Enter value for gidNumber : 1234 Enter value for homeDirectory : /home/example Actual results Error: No such object Expected results Successfully created example
Upstream ticket: https://github.com/389ds/389-ds-base/issues/4293
Build tested: 389-ds-base-2.2.7-2.module+el9dsrv+18726+78959e84.x86_64 I specified people_rdn and groups_rdn in dsrc file: # cat .dsrc [localhost] uri = ldapi://%%2fvar%%2frun%%2fslapd-localhost.socket people_rdn = ou=users groups_rdn = ou=grp Adding user works: # dsidm localhost -b "dc=example,dc=com" user create --uid example --cn example --displayName example --homeDirectory /home/example --uidNumber 1000 --gidNumber 1000 Successfully created example # ldapsearch -xLLL -D "cn=Directory Manager" -w password uid=example dn: uid=example,ou=users,dc=example,dc=com objectClass: top objectClass: nsPerson objectClass: nsAccount objectClass: nsOrgPerson objectClass: posixAccount uid: example cn: example displayName: example uidNumber: 1000 gidNumber: 1000 homeDirectory: /home/example Adding group works: # dsidm localhost -b "dc=example,dc=com" group create --cn example_grp Successfully created example_grp # ldapsearch -xLLL -D "cn=Directory Manager" -w password cn=example_grp dn: cn=example_grp,ou=grp,dc=example,dc=com objectClass: top objectClass: groupOfNames objectClass: nsMemberOf cn: example_grp Marking as VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (redhat-ds:12 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:3344