On Sat, 2017-02-11 at 21:25 +0100, Joakim Tjernlund wrote:
> On Sat, 2017-02-11 at 20:32 +0100, Lukas Slebodnik wrote:
> > On (11/02/17 19:10), Joakim Tjernlund wrote:
> > > I can not get libwbclient in sssd 1.15 work at all for samba.
> > > samba log is not helpful either:
> > > [2017/02/11
On Sat, 2017-02-11 at 20:32 +0100, Lukas Slebodnik wrote:
> On (11/02/17 19:10), Joakim Tjernlund wrote:
> > I can not get libwbclient in sssd 1.15 work at all for samba.
> > samba log is not helpful either:
> > [2017/02/11 20:08:47.742465, 1, pid=21157, effective(0, 0), real(0, 0)]
> >
On Sat, Feb 11, 2017 at 02:41:12PM -0500, Mario Rossi wrote:
> Jakub,
>
> For my production servers I enabled local provider on the customer facing
> servers. I have configured an emergency user that will not be shown in
> /etc/passwd . In a hosting environment anyone can get a a domain for a
Jakub,
For my production servers I enabled local provider on the customer
facing servers. I have configured an emergency user that will not be
shown in /etc/passwd . In a hosting environment anyone can get a a
domain for a just a few $$ and this exposes passwd file. If I add the
account to
What I've seen i rare cases is that sssd will print on screen when
authenticating with cached credentials something like "User
authenticating with cached credentials" . This would be an indication of
sssd going in offline mode because cannot contact the ldap server ( for
whatever other reasons
On (11/02/17 19:10), Joakim Tjernlund wrote:
>I can not get libwbclient in sssd 1.15 work at all for samba.
>samba log is not helpful either:
>[2017/02/11 20:08:47.742465, 1, pid=21157, effective(0, 0), real(0, 0)]
>../source3/smbd/sesssetup.c:290(reply_sesssetup_and_X_spnego)
> Failed to
