Hide Forgot
This bug is created as a clone of upstream ticket: https://fedorahosted.org/389/ticket/47900 root DN, aka "cn=directory manager", should not be restricted by password policy. During ADD operations the root DN is incorrectly restricted by password policy. Updating an existing entry, doing a MOD, works as expected.
Fixed upstream.
Test case: dirsrvtests/tickets/ticket47900_test.py
Checked out the lib389 framework and executed the test case - ticket47900_test.py. The results shows the test case is passed. Hence, marking the bug as Verified. [root@cloud-qe-14 PY.TEST]# rpm -qa |grep -i 389-ds-base 389-ds-base-1.2.11.15-52.el6.x86_64 % (passwd, e.message['desc'])) INFO:lib389:Password update failed as expected: password (2_Short) result (Constraint violation) INFO:lib389:Password update failed as expected: password (No_Number) result (Constraint violation) INFO:lib389:Password update failed as expected: password (N0Special) result (Constraint violation) INFO:lib389:Password update failed as expected: password ({SSHA}bBy8UdtPZwu8uZna9QOYG3Pr41RpIRVDl8wddw==) result (Constraint violation) INFO:lib389:Activate Password Administator and try updates again... INFO:lib389:Password update succeeded (2_Short) INFO:lib389:Password update succeeded (No_Number) INFO:lib389:Password update succeeded (N0Special) INFO:lib389:Password update succeeded ({SSHA}bBy8UdtPZwu8uZna9QOYG3Pr41RpIRVDl8wddw==) PASSED
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/RHBA-2015-1326.html