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.

Description of problem:
Currently ldap_access_order can be set to either ppolicy or lockout, both of which are used for the same purpose.

Version-Release number of selected component (if applicable):
sssd-1.12.4-11.el6

How reproducible:
Always

Steps to Reproduce:
1. In the following domain section of sssd, ldap_access_order can be lockout of ppolicy
[domain/LDAP]
id_provider = ldap
ldap_uri = ldaps://<ldapserver>
ldap_search_base = dc=example,dc=com
ldap_tls_cacert = /etc/openldap/certs/cert.pem
access_provider = ldap
ldap_access_order = ppolicy
#ldap_access_order = lockout
ldap_pwdlockout_dn = cn=pwdconfig,ou=ppolicy,dc=example,dc=com

2.
3.

Actual results:


Expected results:
Only ppolicy works since it is stricter than lockout

Additional info:

Upstream ticket:
https://fedorahosted.org/sssd/ticket/2610

This was fixed in 108a49f0e816d95cf75a1e964f63b397e53c8b56

Verified with sssd-1.14.0-36.el7.x86_64 # man sssd_ldap <snip>
<snip>
    ldap_access_order (string)

        lockout: use account locking. If set, this option denies access in case that ldap attribute 'pwdAccountLockedTime' is present and has value of '000001010000Z'. Please see the option ldap_pwdlockout_dn. Please note that 'access_provider = ldap' must be set for this feature to work.

            Please note that this option is superseded by the “ppolicy” option and might be removed in a future release.

</snip>

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/RHEA-2016-2476.html