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:
Customer noticed a discrepancy between pam_ldap's handling of the account expiration date and shadow-utils.

pam_ldap blocks user from logging in _on_ the account expiration date itself, not just after that date. This appears to be consistent with chage(1)'s description 
       -E, --expiredate EXPIRE_DATE
           Set the date or number of days since January 1, 1970 on which the
           user´s account will no longer be accessible. The date may also be
           expressed in the format YYYY-MM-DD (or the format more commonly
           used in your area). A user whose account is locked must contact the
           system administrator before being able to use the system again.

           Passing the number -1 as the EXPIRE_DATE will remove an account
           expiration date.
but shadow-utils itself is not consistent with that description.

Version-Release number of selected component (if applicable):
shadow-utils-4.1.4.2-13.el6

How reproducible:
TBD

Steps to Reproduce:
TBD
  
Actual results:
TBD

Expected results:
shadow-utils considers an entry expired on the expire date.

Additional info:
Details here to be reviewed by GSS case owner and/or backup TAM.

Yes, there is a one day discrepancy between the chage manual page and the pam_unix behavior in RHEL-5 and RHEL-6. This is fixed in the current pam in Fedora and RHEL-7.

There is a slight risk in fixing this because some customers might expect the old behavior, but it seems to me this is rather theoretical and given clear discrepancy between the manual page and the actual behavior I'd expect the customers to not depend on this.

This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release.  Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.

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.

http://rhn.redhat.com/errata/RHBA-2014-1579.html