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):
Steps to Reproduce:
1. In the following domain section of sssd, ldap_access_order can be lockout of ppolicy
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
Only ppolicy works since it is stricter than lockout
This was fixed in 108a49f0e816d95cf75a1e964f63b397e53c8b56
Verified with sssd-1.14.0-36.el7.x86_64 # man sssd_ldap <snip>
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.
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.