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.

Description of problem:

Add password policy setting to IPA so it can enforce users to include certain string or a numbers in the password.

Customer has to abide by the standards defines for  Federal Information Systems
which are define in the following document.


https://nvd.nist.gov/800-53/Rev4/control/IA-5

IA-5 (1)(b) 	

Enforces at least the following number of changed characters when new passwords are created: [Assignment: organization-defined number];

Currently I do not see we can enforce this in IPA.  Customer would like this feature to be included in IPA so they can stay compliant.



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Hi,
If I understand correctly, the goal is to prevent the modification of a password when it is too similar to the previous one, for instance:
old password: MySecretPwd123
new password: MySecretPwd456
would be refused.

In this case, this RFE is a duplicate of BZ #1442413: IPA password policy has no password difference checking.

Can you confirm if my understanding is correct?

Hi,
thank you for the confirmation. In this case, I am closing this BZ as a duplicate of #1442413.

*** This bug has been marked as a duplicate of bug 1442413 ***