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: ldap bind occurs when admin user changes password with  gracelimit=0

Version-Release number of selected component (if applicable):
ipa-server-4.9.10-4.module+el8.7.0+15926+daa9f08b.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. ipa user-add user1 --first=user1 --last=s
2. ipa passwd user1
3. ipa pwpolicy-mod --gracelimit=0
4. Now run ldap bind.

Actual results:
When password for the ipa user is changed by an administrator the grace period is set to 0.
It allows bind.
[root@server ~]# ldapsearch -LLL -x -D 'uid=user1,cn=users,cn=accounts,dc=rhel87,dc=test' -W -e ppolicy -b uid=user1,cn=users,cn=accounts,dc=rhel87,dc=test dn  -v
ldap_initialize( <DEFAULT> )
Enter LDAP Password: 
filter: (objectclass=*)
requesting: dn 
dn: uid=user1,cn=users,cn=accounts,dc=rhel87,dc=test

Expected results:
With Grace Period Value=0 All LDAP BIND on expired passwords are denied
Basically -1 and 0 values are behaving the same.

Additional info:

Cloned upstream to https://pagure.io/freeipa/issue/9206

Fixed upstream
master:
https://pagure.io/freeipa/c/4105fee2cf9db4deddbdfd6b2058e077364aa679

Fixed upstream
ipa-4-10:
https://pagure.io/freeipa/c/1bb4ff9ed2313fb3c2bd1418258c5bcec557b6a5

Fixed upstream
ipa-4-9:
https://pagure.io/freeipa/c/1316cd8b2252c2543cf2ef2186956a8833037b1e

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 (idm:client and idm:DL1 bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2022:7540

FWIW https://bugzilla.redhat.com/show_bug.cgi?id=782917 introduced the graceperiod feature in within the same release. It controls the number of times an LDAP bind is allowed post-expiration.

This BZ is related to a bug in the implementation of that feature identified by QE.