On Fri, Jun 10, 2016 at 11:45:43AM -0000, ahkaplan@partners.org wrote:
I checked the auth.log file, and the following entries were present:
Jun 10 07:10:50 rorecovery1 sshd[7419]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=<fqdn> user=<username>@<domainname> Jun 10 07:10:51 rorecovery1 sshd[7419]: pam_winbind(sshd:auth): getting password (0x00000388) Jun 10 07:10:51 rorecovery1 sshd[7419]: pam_winbind(sshd:auth): pam_get_item returned a password Jun 10 07:10:51 rorecovery1 sshd[7419]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=<fqdn> user=username>@<domainname> Jun 10 07:10:51 rorecovery1 sshd[7419]: pam_sss(sshd:auth): received for user username>@<domainname> 17 (Failure setting user credentials) Jun 10 07:10:51 rorecovery1 sshd[7419]: pam_ldap: could not open secret file /etc/ldap.secret (No such file or directory) Jun 10 07:10:51 rorecovery1 sshd[7419]: pam_ldap: ldap_simple_bind Can't contact LDAP server Jun 10 07:10:51 rorecovery1 sshd[7419]: pam_ldap: reconnecting to LDAP server... Jun 10 07:10:51 rorecovery1 sshd[7419]: pam_ldap: ldap_simple_bind Can't contact LDAP server Jun 10 07:10:53 rorecovery1 sshd[7419]: Failed password for invalid user username>@<domainname>from <ip address> port 49847 ssh2 Jun 10 07:10:55 r
Not without logs: https://fedorahosted.org/sssd/wiki/Troubleshooting but my guess is that the client can't reach the server.
Also I would discourage mixing pam_ldap and pam_sss in a single PAM stack.