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.
Cloned from upstream: https://pagure.io/freeipa/issue/7114
In some situations the deployments want to tie the expiration of the password to its length and strength.
See section 7 https://www.faa.gov/documentLibrary/media/Order/1370.92A.pdf
Especially item "j" calls for ability to make the password not expire if it is sufficiently long and strong. While it is questionable how to make a decision whether the password is strong enough it might be assumed that if the password is of requested complexity it is in fact strong enough.
Base on this the request is to allow to define a policy that is great or equal than min password length and less or equal max password length. If the password length is equal or longer than the policy value the password expiration should be set to never expire.
User stories:
- As an administrator in public sector organization I want to be able to define a policy in IPA that would make passwords of the certain length never expire.
- As a user in the public sector organization familiar with password policies of my organization I want to be able to choose a long and strong password that I can remember that I do not need to change again and stay compliant for the lifetime of my employment.
Implementation notes:
- To preserve backward compatibility and current behavior I suggest the default for this policy should be "unset" which will be treated as equal to "respect current policies". Only if the value is explicitly set and length of the password is longer or equal to provided value the default password expiration policy should be set to 0 which would mean the password never expires.
- The changes would need to be implemented in https://github.com/freeipa/freeipa/blob/master/daemons/ipa-slapi-plugins/ipa-pwd-extop/common.c probably close to the end of function int ipapwd_CheckPolicy(struct ipapwd_data *data)