My 2c, having two 'Password:' prompts ( RSA + sssd ) will confuse your users, the easiest would be to configure sd_pam.conf to use a different prompt for RSA.
$ egrep ^AUTH /etc/sd_pam.conf
Enter USERNAME :
REQUEST_STR=Please enter System Password for root :
Enter SecureKey :
Enter your SecureKey :
Now back to your question, I believe you need to define a new system-auth file to be used, in my case
system-auth-ac_new with custom pam config. This is a working rsa + sssd (openldap ) setup, I am not sure about proxy as I haven't used it before.
$ cat /etc/pam.d/sshd
auth required pam_securid.so reserve
auth include system-auth-ac_new
account required pam_nologin.so
account include system-auth-ac_new
password include system-auth-ac_new
session optional pam_keyinit.so force revoke
session include system-auth-ac_new
session required pam_loginuid.so
$ cat /etc/pam.d/system-auth-ac_new
# This file is auto-generated.
# User changes will be destroyed the next time authconfig is run.
auth sufficient pam_sss.so
auth required pam_env.so
auth sufficient pam_unix.so nullok try_first_pass
auth requisite pam_succeed_if.so uid >= 500 quiet
auth required pam_deny.so
account [default=bad success=ok user_unknown=ignore] pam_sss.so
#account required pam_access.so
account required pam_unix.so broken_shadow
account sufficient pam_localuser.so
account sufficient pam_succeed_if.so uid < 500 quiet
account required pam_permit.so
password sufficient pam_sss.so use_authtok
password requisite pam_cracklib.so try_first_pass retry=3 type=
password sufficient pam_unix.so sha512 shadow nullok try_first_pass use_authtok
password required pam_deny.so
session optional pam_sss.so
session optional pam_keyinit.so revoke
session required pam_limits.so
session optional pam_mkhomedir.so
session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid
session required pam_unix.so
On 10/26/2017 07:34 PM, Asif Iqbal wrote:
I can on /etc/pam.d/sshd
auth sufficient pam_securid.so
and at ssh login, I just put PIN at Password: prompt and then I get Enter SMS Token: prompt and I can then put thetokencode and I can ssh into the server fine.
If I do the same with pam_sss.so it keeps asking for Password: and never changes the prompt to Enter SMS Token: and ssh fails badly.At this second Password: prompt I tried with just tokencode (at 18:45:34 in log below) or PIN and tokencode (at 18:47:55). Neither letme in and failed eventually.
I think it is because pam_sss -> proxy -> securid -> pam_securd is failing to handle PAM conversation?
Is there a way to fix that to so pam_sss to behave the right way and let authenticate in two steps with PIN and then TokenCode on next step?
Also without this PAM conversation, when the PIN expires it will not let you update it. With simple pam.d/sshd and auth sufficient pam_securid.sothat works very well as well.
I have sssd.conf setup like thisauth_server = proxyproxy_target_pam = securid
And in pam.d/securid fileauth sufficient pam_securid.so
Here are some log http://dpaste.com/2HD27XH.txt whereI tried with PIN at first Password: prompt and then TokenCode at second Password: prompt at 18:45:34 and failed to loginAndI tried with PIN at first Password: prompt and then PIN and TokenCode at second Password: prompt at 18:47:55 and failed to login
I tried with SElinux off and on and same result
If I put PIN and TokenCode at the first Password: prompt, login works fine . I did not put any log for that here.
Any suggestion how to fix pam_sss for OTP?
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
_________________ sssd-users mailing list -- firstname.lastname@example.org. orgTo unsubscribe send an email to sssd-users-leave@lists. fedorahosted.org