[SSSD-users] sssd with ad backend, pam problems

Lukas Slebodnik lslebodn at redhat.com
Thu Aug 28 14:49:10 UTC 2014


On (28/08/14 16:41), Stefan Schäfer wrote:
>Am 28.08.2014 16:18, schrieb Lukas Slebodnik:
>>>Could you put debug_level = 7 into domain section (in /etc/sssd/sssd.conf)
>>>then restart sssd; login as samba user;
>>>
>>>You should find a reason in sssd_invis-ad.loc.log file (/var/log/sssd)
>>>why sssd returned  4 (System error)
>I increased the debug_level to 7, but in the sssd_invis-ad.loc.log didn't
>appear a single entry.
>
>The same is to the other log files sssd_pam.log and sssd_nss.log. The only
>log are these in /var/log/messages.
>
>Seems that for sssd everything is ok and pam causes the problem?
>
I don't think so.

Are you sure you did not see similar line?
[sssd[be[invis-ad.loc]]] [be_pam_handler_callback] (0x0100): Sent result [4][invis-ad.loc]

yuo can try to search name of function (be_pam_handler_callback)

LS


More information about the sssd-users mailing list