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.

Description of problem:
If SSSD is configured to use non-anonymous bind (a bind DN is specified and an authentication token such as a password is being used), SSSD does not properly follow referrals. It will only attempt to bind anonymously to the referred server.

More information is available at the upstream bug report:
https://fedorahosted.org/sssd/ticket/495

Version-Release number of selected component (if applicable):
sssd-1.2.0-12.el6

How reproducible:
Every time

Steps to Reproduce:
1. Set up two LDAP servers requiring non-anonymous bind (anonymous bind should fail)
2. Add a referral on the primary LDAP server for a particular entry that will be answered by the secondary LDAP server. (Use a user entry for easiest reproduction)
3. Configure SSSD with id_provider = ldap and ldap_uri pointing at the primary LDAP server.
4. Request the user entry above (use 'getent passwd <username>')

  
Actual results:
No results found. The logs for the secondary LDAP server will show a failed anonymous bind.

Expected results:
The user should be returned from the secondary LDAP server.

Additional info:
https://fedorahosted.org/sssd/ticket/495

Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.

New Contents:
Release note:
SSSD currently supports following LDAP referrals for anonymous-bind LDAP connections only.

Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.

Diffed Contents:
@@ -1,2 +1 @@
-Release note:
+The System Security Services Daemon (SSSD) currently supports following LDAP referrals on anonymous-bind LDAP connections only.-SSSD currently supports following LDAP referrals for anonymous-bind LDAP connections only.