Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1127266

Summary:	Problems with tokengroups and ldap_group_search_base
Product:	Red Hat Enterprise Linux 7	Reporter:	Jakub Hrozek <jhrozek>
Component:	sssd	Assignee:	Jakub Hrozek <jhrozek>
Status:	CLOSED ERRATA	QA Contact:	Kaushik Banerjee <kbanerje>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.1	CC:	ddas, dpal, drieden, grajaiya, jgalipea, kbanerje, lslebodn, mkosek, pbrezina, preichl
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	sssd-1.12.1-1.el7	Doc Type:	Bug Fix
Doc Text:	Cause: When a non-standard group search base was used, the ID provider might be restricted so that it doesn't allow to resolve all group GIDs returned by the tokenGroups attribute during initgroups call. Consequence: The admin restricted the search base in order to only see certain groups in the 'id output' However, all group GIDs would be reported, with those outside the group base available only as numerical GIDs, not group names. Fix: We documented that if restricting the group search base, tokengroups support must be disabled manually. Result: With disabled tokengroups support and restricted group search base, only the groups in the restricted group search base are visible and all the GIDs resolve into group names.	Story Points:	---
Clone Of:	1127265	Environment:
Last Closed:	2015-03-05 10:33:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1127265
Bug Blocks:

Description Jakub Hrozek 2014-08-06 13:45:33 UTC

+++ This bug was initially created as a clone of Bug #1127265 +++

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/2389

When I enable ldap_group_search_base to restrict to a subset of all groups with tokengroups enabled, it breaks spectacularly.  Disable tokengroups, and it works or disable ldap_group_search_base and it works.

{{{
# service sssd stop;rm -f /var/lib/sss/{db,mc}/* /var/log/sssd/*;sleep 3;service sssd start;sleep 3;id user;id user;service sssd stop
Redirecting to /bin/systemctl stop  sssd.service
Redirecting to /bin/systemctl start  sssd.service
uid=12345(user) gid=513(Domain Users) groups=513(Domain Users)
id: user: no such user
}}}

Log includes:

{{{
[sdap_get_initgr_done] (0x4000): Initgroups done
[sdap_get_initgr_done] (0x4000): Error in initgroups: [2][No such file or directory]
}}}

Tested on git/master dfef1d050c35398c6061256a947b4cc9c1f4b8e6

--- Additional comment from Jakub Hrozek on 2014-08-06 09:42:07 EDT ---

This is a user-visible regression.

Comment 3 Jakub Hrozek 2014-08-19 14:37:44 UTC

This was fixed in master some time ago:
    master: 983983dd1629ab33eab340a40d9ee83965a339c6
    sssd-1-11: 6e6c099b02014d6e2ed97a057c6c521db9c30139

Comment 5 Kaushik Banerjee 2014-12-03 11:21:22 UTC

Verified with 1.12.2-28.el7

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: bug_automation_007: Problems with tokengroups and ldap_group_search_base
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   PASS   ] :: Command 'id testuser05-817192' (Expected 0, got 0)
:: [   PASS   ] :: File '/var/log/sssd/sssd_sssdad2012.com.log' should not contain 'No ID ctx available for \[sssdad2012.com\]' 
:: [   LOG    ] :: Duration: 5s
:: [   LOG    ] :: Assertions: 2 good, 0 bad
:: [   PASS   ] :: RESULT: bug_automation_007: Problems with tokengroups and ldap_group_search_base

Comment 19 errata-xmlrpc 2015-03-05 10:33:12 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.

https://rhn.redhat.com/errata/RHBA-2015-0441.html