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.
DescriptionGowrishankar Rajaiyan
2011-01-19 12:55:12 UTC
Created attachment 474249[details]
Complete sssd_LDAP.log
Description of problem:
Nested groups are not unrolled during the first enumeration causing authentication of the users in nested group to fail, however authentication succeeds after the second enumeration.
Version-Release number of selected component (if applicable):
sssd-1.5.0-2.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
DS setup:
1. Server setup: (make sure all users have primary group defined)
SimpleGroup1 => simpleUserA simpleUserB simpleGroup3
SimpleGroup2 => simpleUserC simpleUserD
SimpleGroup3 => simpleUserE
2. Configure SSSD with "enumerate = true". See additional info for relevant
configuration.
3. restart sssd clearing cache.
4. Try authenticating with simpleuserE (which is a memberOf simplegroup3 which is a memberOf simplegroup1)
Actual results:
Authentication fails initially and succeeds after the second enumeration.
Expected results:
Authentication should succeed after the first enumeration.
Additional info:
1. Relevant sssd configuration:
[domain/LDAP]
id_provider = ldap
auth_provider = ldap
ldap_uri = ldaps://rhdsserver.redhat.com:636
ldap_search_base = dc=example,dc=com
ldap_tls_reqcert = demand
ldap_tls_cacertdir = /etc/openldap/cacerts
ldap_tls_cacert = /etc/openldap/cacerts/cacert.asc
ldap_schema = rfc2307bis
cache_credentials = true
enumerate = true
debug_level = 9
access_provider = simple
simple_allow_groups = simplegroup1
Comment 1Stephen Gallagher
2011-01-19 13:07:51 UTC
Currently our enumeration logic makes two passes: In the first pass, it creates all of the users in the cache. In the second pass, it creates all of the groups.
We need to split the second pass into a second and third pass, so that we have:
Pass 1: Create users
Pass 2: Create empty groups
Pass 3: Populate group members
The reason some nested groups were not unrolled is that the order of their creation would matter. If they weren't already in the sysdb when another group wanted to add them as a member, they would be overlooked.
Comment 2Stephen Gallagher
2011-01-19 14:01:13 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHSA-2011-0560.html
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHSA-2011-0560.html
Created attachment 474249 [details] Complete sssd_LDAP.log Description of problem: Nested groups are not unrolled during the first enumeration causing authentication of the users in nested group to fail, however authentication succeeds after the second enumeration. Version-Release number of selected component (if applicable): sssd-1.5.0-2.el6.x86_64 How reproducible: Always Steps to Reproduce: DS setup: 1. Server setup: (make sure all users have primary group defined) SimpleGroup1 => simpleUserA simpleUserB simpleGroup3 SimpleGroup2 => simpleUserC simpleUserD SimpleGroup3 => simpleUserE 2. Configure SSSD with "enumerate = true". See additional info for relevant configuration. 3. restart sssd clearing cache. 4. Try authenticating with simpleuserE (which is a memberOf simplegroup3 which is a memberOf simplegroup1) Actual results: Authentication fails initially and succeeds after the second enumeration. Expected results: Authentication should succeed after the first enumeration. Additional info: 1. Relevant sssd configuration: [domain/LDAP] id_provider = ldap auth_provider = ldap ldap_uri = ldaps://rhdsserver.redhat.com:636 ldap_search_base = dc=example,dc=com ldap_tls_reqcert = demand ldap_tls_cacertdir = /etc/openldap/cacerts ldap_tls_cacert = /etc/openldap/cacerts/cacert.asc ldap_schema = rfc2307bis cache_credentials = true enumerate = true debug_level = 9 access_provider = simple simple_allow_groups = simplegroup1