Bug 866412 - Samba winbind doesn't return "Domain Local" groups
Summary: Samba winbind doesn't return "Domain Local" groups
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: samba
Version: 6.2
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Andreas Schneider
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-15 10:06 UTC by john
Modified: 2013-02-21 08:45 UTC (History)
3 users (show)

Fixed In Version: samba-3.6.8-139.el6
Doc Type: Bug Fix
Doc Text:
Cause: A bug in winbind has been fixed which changed the behaviour of resolving groups. Consequence: A bugfix changed the behaviour of resolving domain local groups and winbind couldn't find them. Fix: We restored the original behaviour resolving the domain local groups of our own domain. Result: The id command resolves domain local groups of or own domain correctly again.
Clone Of:
Environment:
Last Closed: 2013-02-21 08:45:32 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0338 0 normal SHIPPED_LIVE samba bug fix and enhancement update 2013-02-20 20:54:05 UTC
Samba Project 9100 0 None None None 2012-10-15 10:06:01 UTC

Description john 2012-10-15 10:06:01 UTC 
Description of problem:
winbind doesn't return "Domain Local" groups from Windows 2008 Active Directory 

Version-Release number of selected component (if applicable):3.5.10-114


How reproducible: Install and configure Samba 3.5.10-114 with idmap backend as  "AD"


Steps to Reproduce:
1. Create and join the AD User to a  "Global group" and a "Domain Local group"
2. the "id <AD User>" command displays both Global group and Domain Local group membership
3. After successfull login of AD User to a RHEL system, logout the AD User
4. After approx 5 mins, the "id <AD User>" command displays only Global group membership.
  
Actual results: Installing and configuring Samba 3.5.18 resolves the issue.


Expected results: 

Additional info: Do we have any fixes from Red Hat to resolve this issue specific to Samba 3.5.10--14
Comment 2 Andreas Schneider 2012-10-15 11:59:40 UTC 
This is https://bugzilla.samba.org/show_bug.cgi?id=9052 and has already been fixed for 6.4 due to the rebase.

The patch can be applied on 3.5.10 too.
Comment 8 errata-xmlrpc 2013-02-21 08:45:32 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0338.html
Note You need to log in before you can comment on or make changes to this bug.