Bug 1161741 – TokenGroups for LDAP provider breaks in corner cases

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1161741 - TokenGroups for LDAP provider breaks in corner cases

Summary:	TokenGroups for LDAP provider breaks in corner cases

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	sssd (Show other bugs)
Sub Component:
Version:	7.1
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	SSSD Maintainers
QA Contact:	Kaushik Banerjee
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1160713
Blocks:
	Show dependency tree / graph

Reported:	2014-11-07 13:23 EST by Jakub Hrozek
Modified:	2015-03-05 05:34 EST (History)
CC List:	10 users (show)

See Also:
Fixed In Version:	sssd-1.12.2-16.el7
Doc Type:	Bug Fix
Doc Text:	Cause: SSSD in rhel-6.6 enabled the tokenGroups performance enhancement for all setups. The tokenGroups attribute contains all the groups the user is a member of, as if the client was a windows machine. Consequence: Unless the SSSD client uses id_provider=ad, some of the group SIDs returned from the tokenGroups attribute might be impossible to map, resulting in failures during the initgroups operation. A user-visible result was that not all groups were displayed in the "id" output and the user might be denied access to the system or to some files based on group membership. Fix: The tokenGroups support was disabled unless the id_provider is set to "ad". Result: The group membership of users is reported correctly, allowing access to the system and to the files.
Story Points:	---
Clone Of:	1160713
Environment:
Last Closed:	2015-03-05 05:34:07 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2015:0441	normal	SHIPPED_LIVE	sssd bug fix and enhancement update	2015-03-05 10:05:27 EST

Groups: None (edit)

Description Jakub Hrozek 2014-11-07 13:23:40 EST

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

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

We tried to speed up processing of initgroup lookups with tokenGroups even for the LDAP provider, but it turns out that there are too many corner cases that we didn't catch during development that break. For instance, groups from other trusted domains might appear in TG and the LDAP provider isn't equipped to handle them.

Overall, users who wish to use the added speed benefits of tokenGroups are advised to use the AD provider.

--- Additional comment from Jakub Hrozek on 2014-11-05 09:31:56 EST ---

To work around this issue, disable the tokenGroups optimization to fall back to plain LDAP lookups:
ldap_use_tokengroups = False

Comment 3 Jakub Hrozek 2014-11-12 11:58:34 EST

* master: 5febf5ed0cfb4ba7665d8c3e36ee6941988da773
* sssd-1-11: 6037341d6d77dc61b11d3d23944c615a96713353

Comment 5 Jakub Hrozek 2014-11-12 12:42:02 EST

Please let me know if RHEL-7 test builds are needed, I can build those on-demand. For RHEL-6 test builds, see https://bugzilla.redhat.com/show_bug.cgi?id=1160713#c5

Comment 7 Kaushik Banerjee 2014-12-03 11:48:19 EST

Verified in version sssd-1.12.2-28.el7

Snippet of output from beaker automation run:
:: [   PASS   ] :: Command 'id lkuser01-817348 | grep lkgroup01-817348 | grep lkgroup011-817348' (Expected 0, got 0)
:: [   PASS   ] :: Command 'id -g lkuser01-817348 | grep 10817348' (Expected 0, got 0)
:: [   PASS   ] :: Command 'su_success lkuser01-817348 Secret123' (Expected 0, got 0)

Comment 9 errata-xmlrpc 2015-03-05 05:34:07 EST

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

Note You need to log in before you can comment on or make changes to this bug.