Description[[BR]] With native ldap configured domain and auth-module = ldap, authentications are failing. Password is correct, I have validated with ldap binds and proxy ldap tests.[[BR]] [[BR]]
sssd.conf[[BR]]
[services] description = Local Service Configuration activeServices = nss, dp, pam [services/nss] description = NSS Responder Configuration # the following prevents sssd for searching for the root user/group in # all domains (you can add here a comma separated list of system accounts are # always going to be /etc/passwd users, or that you want to filter out) filterGroups = root filterUsers = root [services/dp] description = Data Provider Configuration [services/pam] description = PAM Responder Configuration [services/monitor] description = Service Monitor Configuration #if a backend is particularly slow you can raise this timeout here sbusTimeout = 30 [domains] description = Domains served by SSSD domains = LDAP [domains/LDAP] description = Proxy request to our LDAP server enumerate = TRUE minId = 1000 maxId = 1010 useFullyQualifiedNames = TRUE cache-credentials = TRUE provider = ldap auth-module = ldap ldapUri = ldap://ldap.example.com (your ldap server) userSearchBase = ou=People,dc=example,dc=com groupSearchBase = ou=Groups,dc=example,dc=com
pam.d/system-auth[[BR]]
#%PAM-1.0 auth required pam_env.so auth sufficient pam_fprintd.so auth sufficient pam_unix.so nullok auth sufficient pam_sss.so use_first_pass auth requisite pam_succeed_if.so uid >= 500 quiet auth required pam_deny.so account required pam_unix.so broken_shadow account sufficient pam_sss.so account sufficient pam_localuser.so account sufficient pam_succeed_if.so uid < 500 quiet account required pam_permit.so password requisite pam_cracklib.so try_first_pass retry=3 password sufficient pam_unix.so sha512 shadow nullok try_first_pass use_authtok password sufficient pam_sss.so use_authtok password required pam_deny.so session optional pam_keyinit.so revoke session required pam_limits.so session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid session sufficient pam_unix.so session required pam_sss.so
Steps to Reproduce[[BR]]
Version[[BR]] sssd-0.6.0-0.2009092314git2d12249.fc11.i586
Lowering priority because authentications with native LDAP are working when directory server is SSSL secured. It needs to be documented that this is required for SSSD LDAP authentication. It also needs to be documented where the CA certificate needs to be if tls_reqcert = hard or demand.
doc: 0 => 1 priority: blocker => major tests: 0 => 1
Fixed in e8eb42bb51de9392b0bc7e43a53ad3cd88913073
resolution: => fixed status: new => closed
added automated tests for tls_reqcrt never and hard. hard using ldap_tls_cacertdir and ldap_tls_cacert.
tests: 1 => 0 testsupdated: 0 => 1
Fields changed
resolution: fixed => status: closed => reopened
owner: somebody => sbose status: reopened => new
fixedin: => 0.7.0 resolution: => fixed status: new => closed
ldap_tls_cacert and ldap_tls_cacertdir are described in the sssd-ldap man page and should be mentioend in the documentation. The documentation should underline that sssd only supports LDAP authentication if SSL/TLS is enabled and working. A pointer to a documentation which explains how openLDAP handles certificates on the client side might be useful.
rhbz: => 0
Metadata Update from @jgalipea: - Issue assigned to sbose - Issue set to the milestone: SSSD 0.6.0
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/1243
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.