Description of problem:
For modifiersName/internalModifiersName feature, internalModifiersname is not
The internalModifersname or internalCreatorsname is NOT supposed to be a
bind DN, like "cn=directory manager", but either the DNA plugin or the
the ldbm database plugin.
But we are seeing "cn=directory manager" for internalModifersname in DNA plugin.
/usr/lib64/mozldap/ldapsearch -1 -h dhcp201-134.englab.pnq.redhat.com -p 7512 -D "cn=directory manager" -w Secret123 -b uid=amsharma1,dc=example,dc=com objectClass=* internalModifiersname
internalModifiersname: cn=directory manager
So this is a bug.
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
grep the internalModifiersname in the user entry
/usr/lib64/mozldap/ldapsearch -1 -T -h dell-pe2800-01.rhts.eng.bos.redhat.com -p 8086 -D cn=directory manager -w Secret123 -b cn=Posix User1,dc=example,dc=com objectClass=* internalModifiersname | grep -i cn=Distributed Numeric Assignment Plugin,cn=plugins,cn=config
internalModifiersname: cn=Distributed Numeric Assignment Plugin,cn=plugins,cn=config
internalModifiersname is plugin DN
cn=ldbm database,cn=plugins,cn=config is the expected result when a plugin does not interfere. Since no plugins add entries, this is the value that should always be expected for internalCreatorsname.
The internalModifersname and internalCreatorsname are always going to be plugin names. They will never be bind DN's.
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.