[SSSD] SSSD Configuration issue

Jakub Hrozek jhrozek at redhat.com
Tue Nov 15 11:46:01 UTC 2011


On Tue, Nov 15, 2011 at 09:24:57AM +0530, Nitesh Mehare wrote:
>    Here is the snapshot of the file
> 
>    -bash-3.2# cat /etc/pam.d/sshd
>    #%PAM-1.0
>    authA A A A A A  includeA A A A A  system-auth
>    accountA A A  requiredA A A A  pam_nologin.so
>    accountA A A  includeA A A A A  system-auth
>    passwordA A  includeA A A A A  system-auth
>    sessionA A A  optionalA A A A  pam_keyinit.so force revoke
>    sessionA A A  includeA A A A A  system-auth
>    sessionA A A  requiredA A A A  pam_loginuid.so
>    -bash-3.2#

Provided that you still use the same system-auth file as you provided in
one of the first comments, everything looks fine.

Can you run:
strace -e open su - $username

That should tell us whether the pam stack is actually opening the module
or not.



More information about the sssd-devel mailing list