Red Hat Bugzilla – Bug 1127266
Problems with tokengroups and ldap_group_search_base
Last modified: 2015-03-05 05:33:12 EST
+++ 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.
This was fixed in master some time ago: master: 983983dd1629ab33eab340a40d9ee83965a339c6 sssd-1-11: 6e6c099b02014d6e2ed97a057c6c521db9c30139
Verified with 1.12.2-28.el7 :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ LOG ] :: bug_automation_007: Problems with tokengroups and ldap_group_search_base :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ PASS ] :: Command 'id testuser05-817192@sssdad2012.com' (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
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