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.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47389

Steps:
. Using default password policy: stored in SSHA
. Give ACI to update all attributes including userpassword.
 aci: (targetattr ="*")(version 3.0;acl "allow all";allow (all) userdn="ldap:///anyone";)
.Let uid=tuser0 replace other user uid=tuser1's userpassword as follows:
{{{
 $ldapmodify ... -D "uid=tuser0,dc=example,dc=com" -w password << EOF
 dn: uid=Nuser1,dc=example,dc=com
 changetype: modify
 replace: userpassword
 userpassword: {CLEAR}newuser1
 EOF
}}}
Then, the tuser1's password is stored as a clear text.
{{{
 $ldapsearch ... userpassword
 dn: uid=Nuser1,dc=example,dc=com
 userpassword: newuser1
}}}
Expected result: Ordinary user should not be allowed to override the password policy.

Thanks Nathan, I am marking bug 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, 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://rhn.redhat.com/errata/RHSA-2015-0416.html