New answers tagged pam
Ubuntu 14.04 Had to add both 'hard' and 'soft' entries in /etc/security/limits.conf for pam to recognize settings for rtprio (-r) and memlock (-l).
The general logic is that a PAM enabled program handling shell logins will hit the auth, account, and session stacks in sequence, but a program can simply skip over any of these if it handles one or more of those functions with its own implementations. sshd supports a few modes of authentication that cannot be delegated to PAM, because they rely on methods ...
If you look at the files in directory /etc/pam.d/ you'll (almost certainly) find one or more of them that refer to pam_pwdfile. The following command will show you which ones ... grep pam_pwdfile /etc/pam.d/* From this you should be able to work out (from the file name) which bit of of the system is trying to use pam_pwdfile for authentication.
I would like to say this solution worked for me! I was having the same issue using free-ipa, and using this setup in my /etc/pam.d/system-auth file avoided the extra "authentication failure" errors: auth required pam_env.so auth sufficient pam_sss.so auth sufficient pam_unix.so nullok try_first_pass auth requisite ...
You can follow up my instruction. This works for me on Centos 7.0 & 7.1 and has not been tested on Centos 6.X. Step 1: Install pam_mount and cifs-utils. Step 2: Please only configure file /etc/pam.d/password-auth, just add 2 lines ( one is on top, and the one is at the end of the file) auth required pam_mount.so auth required ...
Top 50 recent answers are included