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.

Bug 799009

Summary: Warn to syslog when dereference requests fail
Product: Red Hat Enterprise Linux 6 Reporter: Stephen Gallagher <sgallagh>
Component: sssdAssignee: Jakub Hrozek <jhrozek>
Status: CLOSED ERRATA QA Contact: Kaushik Banerjee <kbanerje>
Severity: unspecified Docs Contact:
Priority: low    
Version: 6.3CC: grajaiya, jgalipea, prc
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: sssd-1.9.1-1.el6 Doc Type: Bug Fix
Doc Text:
Do not document
 Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-21 09:20:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Stephen Gallagher 2012-03-01 14:54:08 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/1213

In some cases, the dereference search might fail - for example if the server incorrectly advertizes deref support or if the attribute we try to dereference is not a DN.

SSSD should fall back to individual lookups in this case. The hard part is picking the errors that would be non-fatal for the search. "Protocol error" and "Server refused to perform" might be a good start.
Comment 1 Stephen Gallagher 2012-03-01 14:54:33 UTC 
This is not really a bug in SSSD so much as a misconfiguration on the server. The original report was failing because someone had changed the OID on the LDAP member attribute so that it did not report as a DN.

We should just write a descriptive error message to the syslog in this case, so the administrator is aware that there is a problem on the LDAP server.
Comment 2 RHEL Program Management 2012-07-10 05:49:47 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 3 RHEL Program Management 2012-07-11 02:04:37 UTC 
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 5 Kaushik Banerjee 2013-01-23 10:43:18 UTC 
Verified in version 1.9.2-74

/var/log/messages shows:
Jan 23 12:31:25 dhcp201-200 sssd[be[LDAP]]: dereference processing failed : Invalid argument

Domain log shows:
(Wed Jan 23 12:31:25 2013) [sssd[be[LDAP]]] [sdap_nested_group_process_deref_step] (0x0400): Missing data past threshold, doing a full deref
(Wed Jan 23 12:31:25 2013) [sssd[be[LDAP]]] [sdap_deref_search_send] (0x2000): Server supports OpenLDAP deref
(Wed Jan 23 12:31:25 2013) [sssd[be[LDAP]]] [sdap_x_deref_search_send] (0x0400): Dereferencing entry [cn=Group_02,ou=Groups,dc=example,dc=com] using OpenLDAP deref
(Wed Jan 23 12:31:25 2013) [sssd[be[LDAP]]] [sdap_get_generic_ext_step] (0x0400): calling ldap_search_ext with [no filter][cn=Group_02,ou=Groups,dc=example,dc=com].
(Wed Jan 23 12:31:25 2013) [sssd[be[LDAP]]] [sdap_process_message] (0x4000): Message type: [LDAP_RES_SEARCH_ENTRY]
(Wed Jan 23 12:31:25 2013) [sssd[be[LDAP]]] [sdap_x_deref_parse_entry] (0x0400): Got deref control
(Wed Jan 23 12:31:25 2013) [sssd[be[LDAP]]] [sdap_parse_deref] (0x1000): Dereferenced DN: uid=kuser2
(Wed Jan 23 12:31:25 2013) [sssd[be[LDAP]]] [sdap_parse_deref] (0x0080): Dereferenced entry [uid=kuser2] has no attributes
(Wed Jan 23 12:31:25 2013) [sssd[be[LDAP]]] [sdap_x_deref_parse_entry] (0x0040): sdap_parse_deref failed [22]: Invalid argument
(Wed Jan 23 12:31:25 2013) [sssd[be[LDAP]]] [sdap_get_generic_ext_done] (0x0020): reply parsing callback failed.
(Wed Jan 23 12:31:25 2013) [sssd[be[LDAP]]] [sdap_x_deref_search_done] (0x0100): sdap_get_generic_ext_recv failed [22]: Invalid argument
(Wed Jan 23 12:31:25 2013) [sssd[be[LDAP]]] [sdap_deref_search_done] (0x0040): dereference processing failed [22]: Invalid argument
(Wed Jan 23 12:31:25 2013) [sssd[be[LDAP]]] [sdap_nested_done] (0x0020): Nested group processing failed: [22][Invalid argument]
(Wed Jan 23 12:31:25 2013) [sssd[be[LDAP]]] [sdap_id_op_done] (0x4000): releasing operation connection
(Wed Jan 23 12:31:25 2013) [sssd[be[LDAP]]] [acctinfo_callback] (0x0100): Request processed. Returned 3,22,Group lookup failed
Comment 6 errata-xmlrpc 2013-02-21 09:20:09 UTC 
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