[Samba] valid users issue with a few groups
Shannon Price
pricesw at auburn.edu
Sat Oct 10 12:41:37 UTC 2026
Thanks for the quick reply. I wondered about the overlapping ID ranges (put in place by another admin), but it never caused any issues in our testing. I have also earlier this week adjusted them in our samba test environment so they don't overlap and I see the same behavior.
idmap config * : backend = tdb
idmap config * : range = 2000000000-2000099999
idmap config AUBURN : backend = nss
idmap config AUBURN : range = 5-1999999999
Thanks for the info about "winbind nss info = sss" (also a previous administrator). Obviously this invalid setting has no effect. The other options are not interesting in our situation.
The winbind + sssd combo is what we landed on to allow MSAD authentication (via Winbind), but sss provides the connection to our IdM/OpenLDAP/FreeIPA for Posix. We could not get Winbind alone to pull that information from any LDAP we tried. We don't have access to the RFC2307 attributes from our MSAD.
--
Shannon
-----Original Message-----
From: samba <samba-bounces at lists.samba.org> On Behalf Of Rowland Penny via samba
Sent: Saturday, October 10, 2026 6:56 AM
To: samba at lists.samba.org
Cc: Rowland Penny <rpenny at samba.org>
Subject: Re: [Samba] valid users issue with a few groups
On Sat, 10 Oct 2026 13:22:00 +0200
Ralph Boehme via samba <samba at lists.samba.org> wrote:
> On 10/10/26 1:02 PM, Shannon Price via samba wrote:
> > With Samba we have noticed that certain groups do not work in the
> > valid users field for their share. If we remove the valid users
> > field, Samba still recognizes group memberships on the file systems
> > correctly. In the attached config, my user is in four groups:
> > deans, ecegrad, ea, rams. I have four shares defined each with a
> > corresponding @groupname (we have also played with +groupname and
> > various fully qualified formats). Two shares work (ea - GID 30,
> > rams GID 324). Two shares don't work (deans - GID 35, ecegrad - GID
> > 2009).
> interesting. I'd set logging to level 10 and then compare the working
> against the non working case. smbd might be talking to winbindd so you
> might have to look into the winbind logs as well.
>
> Cheers!
> -Ralph
>
Hmm, interesting isn't the word I would use, the smb.conf has 'winbind nss info = sss' and, as far as I am aware, the 'winbind nss info'
parameter doesn't have a value called 'sss', the user appears to be running both sssd and winbind, not using winbind, why? they both do the same thing. There is also the matter of the domain ranges, they overlap, more than that, they are virtual the same.
Rowland
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
More information about the samba
mailing list