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.
DescriptionKaushik Banerjee
2012-10-31 14:12:46 UTC
Description of problem:
Nested groups not retrieved appropriately from cache
Version-Release number of selected component (if applicable):
sssd-1.9.2-4.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Create a nested group structure in AD as follows:
tuser1_top_grp1
|
tuser1_mid_grp1
|
tuser1
2. Configure sssd to lookup users and groups via ldap provider:
The domain section that I used:
[domain/ADTEST]
debug_level = 0xFFF0
id_provider = ldap
ldap_schema = ad
ldap_uri = ldap://adserver
ldap_default_bind_dn = cn=Administrator,cn=Users,dc=sssdad,dc=com
ldap_default_authtok = xxxxxx
ldap_search_base = dc=sssdad,dc=com
ldap_force_upper_case_realm = True
ldap_referrals = false
3.
Issue1:
Lookup tuser1 in the following sequence:
# service sssd stop;rm -f /var/lib/sss/db/* /var/lib/sss/mc/*;service sssd start
Stopping sssd: [ OK ]
Starting sssd: [ OK ]
# getent group tuser1_mid_grp1
tuser1_mid_grp1:*:10004:tuser1
# getent group tuser1_top_grp1
tuser1_top_grp1:*:10003:tuser1
# id tuser1
uid=10004(tuser1) gid=10004(tuser1_mid_grp1) groups=10004(tuser1_mid_grp1) <== Doesn't show tuser1_top_grp1
Issue2:
# service sssd stop;rm -f /var/lib/sss/db/* /var/lib/sss/mc/*;service sssd start
Stopping sssd: [ OK ]
Starting sssd: [ OK ]
# getent group tuser1_top_grp1
tuser1_top_grp1:*:10003:tuser1
# getent group tuser1_mid_grp1
tuser1_mid_grp1:*:10004:tuser1,tuser1 <== tuser1 is seen twice
Actual results:
Expected results:
a. for Issue1:
# id tuser1
uid=10004(tuser1) gid=10004(tuser1_mid_grp1) groups=10004(tuser1_mid_grp1),10003(tuser1_top_grp1)
b. for Issue2:
# getent group tuser1_mid_grp1
tuser1_mid_grp1:*:10004:tuser1
Additional info:
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/RHSA-2013-0508.html
Description of problem: Nested groups not retrieved appropriately from cache Version-Release number of selected component (if applicable): sssd-1.9.2-4.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Create a nested group structure in AD as follows: tuser1_top_grp1 | tuser1_mid_grp1 | tuser1 2. Configure sssd to lookup users and groups via ldap provider: The domain section that I used: [domain/ADTEST] debug_level = 0xFFF0 id_provider = ldap ldap_schema = ad ldap_uri = ldap://adserver ldap_default_bind_dn = cn=Administrator,cn=Users,dc=sssdad,dc=com ldap_default_authtok = xxxxxx ldap_search_base = dc=sssdad,dc=com ldap_force_upper_case_realm = True ldap_referrals = false 3. Issue1: Lookup tuser1 in the following sequence: # service sssd stop;rm -f /var/lib/sss/db/* /var/lib/sss/mc/*;service sssd start Stopping sssd: [ OK ] Starting sssd: [ OK ] # getent group tuser1_mid_grp1 tuser1_mid_grp1:*:10004:tuser1 # getent group tuser1_top_grp1 tuser1_top_grp1:*:10003:tuser1 # id tuser1 uid=10004(tuser1) gid=10004(tuser1_mid_grp1) groups=10004(tuser1_mid_grp1) <== Doesn't show tuser1_top_grp1 Issue2: # service sssd stop;rm -f /var/lib/sss/db/* /var/lib/sss/mc/*;service sssd start Stopping sssd: [ OK ] Starting sssd: [ OK ] # getent group tuser1_top_grp1 tuser1_top_grp1:*:10003:tuser1 # getent group tuser1_mid_grp1 tuser1_mid_grp1:*:10004:tuser1,tuser1 <== tuser1 is seen twice Actual results: Expected results: a. for Issue1: # id tuser1 uid=10004(tuser1) gid=10004(tuser1_mid_grp1) groups=10004(tuser1_mid_grp1),10003(tuser1_top_grp1) b. for Issue2: # getent group tuser1_mid_grp1 tuser1_mid_grp1:*:10004:tuser1 Additional info: