On Tue, Dec 06, 2016 at 04:47:04PM -0000, E. Clapton wrote:
BY using jurnalctl, i have found the following errors:
Dec 06 16:35:04 localhost systemd[1]: Started OpenSSH per-connection server daemon
(x.x.x.x:60759).
Dec 06 16:35:04 localhost sshd[1637]: PAM unable to dlopen(/lib64/security/pam_ldap.so):
/lib64/security/pam_ldap.so: cannot open shared object file: No such file or directory
This line probably means that PAM configuration refers to pam_ldap.so
but pam_ldap is not installed on the system.
Dec 06 16:35:04 localhost sshd[1637]: PAM adding faulty module:
/lib64/security/pam_ldap.so
Dec 06 16:35:08 localhost sshd[1639]: pam_unix(sshd:auth): authentication failure;
logname= uid=0 euid=0 tty=ssh ruser= rhost=x.x.x.x. user=myuser
Dec 06 16:35:10 localhost sshd[1637]: PAM: Authentication failure for omri_w from
x.x.x.x
Please advise.
BTW, I’m using CoreOS as operating system.
I've never used CoreOS myself, but the PAM configuration files are pretty
much always at /etc/pam.d/*.
However, I don't think you should need to tune the PAM config yourself
by hand-editing the files. Most distributions provide some sort of a
configuration mechanism to set up the PAM stack, like authconfig on
Fedora/RHEL. I would suggest to consult some CoreOS-specific
documentation to see how should authentication be set up. In SSSD
upstream, we can review the PAM configuration in general, but I'm not
sure we have the knowledge to help you set up CoreOS..