Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHEA-2011-0533.html
Hi, Tested this bug, steps are as below : 1. ldapmodify -x -h localhost -p 389 -D "cn=Directory Manager" -w Secret123 << EOF > dn: cn=config > changetype: modify > replace: nsslapd-entryusn-global > nsslapd-entryusn-global: on > EOF modifying entry "cn=config" 2.ldapsearch -x -h localhost -p 389 -D "cn=Directory Manager" -w Secret123 -b "cn=config" | grep -i ENTRYUSN nsslapd-entryusn-global: on 3. Added one entry : ldapmodify -x -h localhost -p 1389 -D "cn=Directory Manager" -w Secret123 << EOF dn: uid=amita,ou=people,dc=example,dc=com changetype: add objectClass: top objectClass: person objectClass: inetorgperson sn: testkrbuser cn: kkk testkrbuser userPassword: redhat EOF adding new entry "uid=amita,ou=people,dc=example,dc=com" 4. Added another entry which will be used for deletion - dn: uid=test11,dc=example,dc=com mail: test11 uid: test11 givenName: test11 objectClass: top objectClass: person objectClass: inetorgperson objectClass: ntUser objectClass: inetuser objectClass: organizationalPerson sn: test11 cn: rrr test11 ntUserCreateNewAccount: true ntUserDomainId: test11 ntUserDeleteAccount: true userPassword:: e1NTSEF9UUdFc29jcEJ6QlZjcG5RaUFrbHgzd3l4MUl2RWZRWXJpVnVaMEE9PQ= = telephoneNumber: 989898191 5. ldapdelete -x -h localhost -p 1389 -D "uid=amita,ou=people,dc=example,dc=com" -w redhat uid=test11,dc=example,dc=com ldap_delete: Insufficient access (50) additional info: Insufficient 'delete' privilege to delete the entry 'uid=test11,dc=example,dc=com'. 6. ldapsearch -x -h localhost -p 1389 -D "cn=Directory Manager" -w Secret123 -b "dc=example,dc=com" # test11, example.com dn: uid=test11,dc=example,dc=com mail: test11 uid: test11 givenName: test11 objectClass: top objectClass: person objectClass: inetorgperson objectClass: ntUser objectClass: inetuser objectClass: organizationalPerson sn: test11 cn: rrr test11 ntUserCreateNewAccount: true ntUserDomainId: test11 ntUserDeleteAccount: true userPassword:: e1NTSEF9UUdFc29jcEJ6QlZjcG5RaUFrbHgzd3l4MUl2RWZRWXJpVnVaMEE9PQ= = telephoneNumber: 989898191 preventryusn is not added. Hence bug is tested OK. Marking it as VERIFIED. -Amita Sharma