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.
When using a global password policy for syntax checking, there are some default
settings that will be used (such as a minimum length of 8) if the config
attributes don't exist in cn=config. This doesn't seem to work with the
fine-grained policies.
Here are some steps to reproduce the problem:
1. - Enable global syntax checking, setting the minLength to 6.
2. - Enable fine-grained password policies.
3. - Create a subtree-level policy on "ou=People", enabling syntax checking
with the default values (minLength will be displayed as 8 in Console).
4. - Attempt to change a password of a user outside of "ou=People" with a
password of 5 characters long. This should be rejected with an err=19.
5. - Try step 4 again, but with a password length of 6 characters. This
should work.
6. - Try step 4 again, but with a user inside of "ou=People". This should
fail with an err=19, but it will succeed!
To work around the problem, you can add the password syntax attributes to the
fine-grained policy entry explicitly. This can be done via the Console UI by
setting each of the syntax settings to a non-default value, saving it, then
setting them to what you want (even if you want the defaults) and saving again.
Once this is documented, we either need to move this bug to DS9.0 and FDS1.3.0 or close this and open a new bug. This falls under the category of "expose password policy to plug-ins"
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-2016-2594.html
When using a global password policy for syntax checking, there are some default settings that will be used (such as a minimum length of 8) if the config attributes don't exist in cn=config. This doesn't seem to work with the fine-grained policies. Here are some steps to reproduce the problem: 1. - Enable global syntax checking, setting the minLength to 6. 2. - Enable fine-grained password policies. 3. - Create a subtree-level policy on "ou=People", enabling syntax checking with the default values (minLength will be displayed as 8 in Console). 4. - Attempt to change a password of a user outside of "ou=People" with a password of 5 characters long. This should be rejected with an err=19. 5. - Try step 4 again, but with a password length of 6 characters. This should work. 6. - Try step 4 again, but with a user inside of "ou=People". This should fail with an err=19, but it will succeed! To work around the problem, you can add the password syntax attributes to the fine-grained policy entry explicitly. This can be done via the Console UI by setting each of the syntax settings to a non-default value, saving it, then setting them to what you want (even if you want the defaults) and saving again.