[SSSD-users] Re: one user can't be looked up

2018-07-10 Thread Peter Moody
line breaks are in the original logs: (Tue Jul 10 20:06:37 2018) [sssd[be[x.com]]] [ldb] (0x4000): Ending timer event 0x557c510ec600 "ltdb_callback" (Tue Jul 10 20:06:37 2018) [sssd[be[x.com]]] [ldb] (0x4000): start ldb transaction (nesting: 2) (Tue Jul 10 20:06:37 2018) [sssd[be[x.com]]] [ldb]

[SSSD-users] Re: Missing group memberships with sssd (when using tokengroups)

2018-07-10 Thread Jakub Hrozek
On Mon, Jul 09, 2018 at 03:11:38PM -0500, Spike White wrote: > All, > > Below is a writeup of missing AD groups for accounts when using > tokengroups. When not using tokengroups, sssd is rock solid. > > Yes, most of the missing AD groups are universal or global groups -- but > not all! For

[SSSD-users] Re: recreate machine keytab file

2018-07-10 Thread Ondrej Valousek
Well, I could try that but it's not very handy - you need to go to AD and perform passwd change manually. I was hoping that "net -U administrator ads keytab create" or similar would do everything necessary in a single run - just like "net ads join". Ondrej -Original Message- From:

[SSSD-users] Re: recreate machine keytab file

2018-07-10 Thread Ondrej Valousek
Hi, Ok, I did not have 'netbios name' in my smb.conf (which is a simple 4-liner). I added it but it did not make any difference. In summary, it fills my keytab with entries like (as per klist -k -K): /@ Or /@ Where is a username of someone in AD and is a hostname of some machine joined to