Bug 3154 - pam_winbind require_membership_of does not work when SID is from the local machine
Summary: pam_winbind require_membership_of does not work when SID is from the local ma...
Status: RESOLVED FIXED
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: winbind (show other bugs)
Version: 3.0.10
Hardware: x86 Linux
: P3 normal
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-10 16:49 UTC by Tom McLaughlin
Modified: 2006-05-30 10:51 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom McLaughlin 2005-10-10 16:49:06 UTC
I have Samba 3.0.10 instaled on a CentOS 4.1 machine which authenticates users
against a Windows domain via pam_winbind.  When require_membership_of is used
with the PAM module and is set to a SID from the domain everything works fine. 
If I set the SID to a one for a local group, members of the local group cannot
login.  The logs show an "incorrect password or invalid membership" error.  When
I check what should be a valid user's group SIDS via wbinfo I see all domain and
local sids for the user listed.  It appears that pam_wbinfo is not expanding
local SID memberships.  I have also noticed that ntlm_auth when using
--required-membership-of also has this same problem.

The rationale for requiring a local SID is I can created a local nested group on
the box, say Valid Uers, which has for instance the Domain Admins group,
Developers group, johnblow, and janeblow as members.

After some a little push from from Andrew Bartlett on #samba-technical, I took a
look through the svn info for wbinfo.c with my non-existant C knowledge. 
Possibly commits 7786 and 7823 might explain why wbinfo can list the SID of the
local nested groups?  Thanks.

Tom
Comment 1 Guenther Deschner 2005-10-24 06:46:15 UTC
Any chance you test with a more recent release than 3.0.10 ? 

We possibly won't have the ressources to debug / fix that issue for 3.0.10
(quite a bit changed since that).

Comment 2 Guenther Deschner 2006-05-30 10:51:40 UTC
Closing, as this works in more recent releases and there was no feedbacks for months. Please reopen, if you still see any problems with it.