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.
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/2148
If the DNS names of member domains in an AD forest have a parent-child relation ship, e.g. forest.ad, child.forest.ad, grandchild.forest.ad, the LDAP sub-trees in the GC for the child domains are children of the forest root LDAP tree. Hence a subtree search in the forest root tree will find results in the child domains as well.
Since there are user and group names which are present in all AD domains e.g. a search for 'Domain Users' will return multiple matches. Currently this is not expected by the generic SSSD LDAP code and the following can be found in the logs:
{{{
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_get_groups_next_base] (0x0400): Searching for groups with base [DC=ad18,DC=ipa18,DC=devel]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_get_generic_ext_step] (0x0400): calling ldap_search_ext with [(&(name=domain admins)(objectclass=group)(name=*))][DC=ad18,DC=ipa18,DC=devel].
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_get_generic_ext_step] (0x1000): Requesting attrs: [objectClass]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_get_generic_ext_step] (0x1000): Requesting attrs: [name]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_get_generic_ext_step] (0x1000): Requesting attrs: [gidNumber]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_get_generic_ext_step] (0x1000): Requesting attrs: [member]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_get_generic_ext_step] (0x1000): Requesting attrs: [objectGUID]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_get_generic_ext_step] (0x1000): Requesting attrs: [objectSID]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_get_generic_ext_step] (0x1000): Requesting attrs: [whenChanged]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_get_generic_ext_step] (0x1000): Requesting attrs: [uSNChanged]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_get_generic_ext_step] (0x2000): ldap_search_ext called, msgid = 5
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_id_op_connect_done] (0x4000): caching successful connection after 1 notifies
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [be_run_unconditional_online_cb] (0x4000): List of unconditional online callbacks is empty, nothing to do.
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_process_result] (0x2000): Trace: sh[0x89ed1a8], connected[1], ops[0x89de5b0], ldap[0x89e28d8]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_process_message] (0x4000): Message type: [LDAP_RES_SEARCH_ENTRY]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_parse_entry] (0x4000): OriginalDN: [CN=Domain Admins,CN=Users,DC=ad18,DC=ipa18,DC=devel].
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_parse_range] (0x2000): No sub-attributes for [objectClass]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_parse_range] (0x2000): No sub-attributes for [member]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_parse_range] (0x2000): No sub-attributes for [whenChanged]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_parse_range] (0x2000): No sub-attributes for [uSNChanged]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_parse_range] (0x2000): No sub-attributes for [name]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_parse_range] (0x2000): No sub-attributes for [objectGUID]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_parse_range] (0x2000): No sub-attributes for [objectSid]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_process_result] (0x2000): Trace: sh[0x89ed1a8], connected[1], ops[0x89de5b0], ldap[0x89e28d8]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_process_message] (0x4000): Message type: [LDAP_RES_SEARCH_ENTRY]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_parse_entry] (0x4000): OriginalDN: [CN=Domain Admins,CN=Users,DC=sub,DC=ad18,DC=ipa18,DC=devel].
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_parse_range] (0x2000): No sub-attributes for [objectClass]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_parse_range] (0x2000): No sub-attributes for [whenChanged]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_parse_range] (0x2000): No sub-attributes for [uSNChanged]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_parse_range] (0x2000): No sub-attributes for [name]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_parse_range] (0x2000): No sub-attributes for [objectGUID]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_parse_range] (0x2000): No sub-attributes for [objectSid]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_process_result] (0x2000): Trace: sh[0x89ed1a8], connected[1], ops[0x89de5b0], ldap[0x89e28d8]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_process_message] (0x4000): Message type: [LDAP_RES_SEARCH_RESULT]
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_get_generic_ext_done] (0x0400): Search result: Success(0), no errmsg set
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_get_groups_process] (0x0400): Search for groups, returned 2 results.
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_get_groups_process] (0x0080): Individual group search returned multiple results
(Thu Nov 14 11:49:39 2013) [sssd[be[ad18.ipa18.devel]]] [sdap_id_op_done] (0x4000): releasing operation connection
}}}
This is a similar issue like the one fixed by 022ebf54037982211da729b99213bab7458ae827 but in a different code path.
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.