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 805924 - SSSD should attempt to get the RootDSE after binding
Summary: SSSD should attempt to get the RootDSE after binding
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Stephen Gallagher
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-22 13:14 UTC by Dmitri Pal
Modified: 2020-05-02 16:48 UTC (History)
4 users (show)

Fixed In Version: sssd-1.8.0-23.el6
Doc Type: Bug Fix
Doc Text:
Cause: SSSD relies on some information it can retrieve from the RootDSE in order to determine the capabilities of the server. Some servers do not make the RootDSE available via unencrypted, non-authenticated LDAP bind (in violation of the LDAP standard) Consequence: On such servers, SSSD operates in a slightly degraded mode, being unable to take advantage of any enhanced features of the LDAP server. Change: SSSD will now make a second attempt to retrieve the RootDSE after it completes a successful bind attempt. Result: SSSD is now able to take advantage of enhanced features on servers that do not expose the RootDSE to non-authenticated users.
Clone Of:
Environment:
Last Closed: 2012-06-20 11:56:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 2300 0 None None None 2020-05-02 16:48:44 UTC
Red Hat Product Errata RHBA-2012:0747 0 normal SHIPPED_LIVE sssd bug fix and enhancement update 2012-06-19 19:31:43 UTC

Description Dmitri Pal 2012-03-22 13:14:52 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/1258

In some situations, a server will disallow retrieving the RootDSE to an anonymous user (or one who is not using a sufficiently high SSF).

In those situations, we should continue as we do currently, binding with reasonable defaults, and then attempt again to retrieve the RootDSE, which may now be available to the properly-bound user.
Comment 3 Amith 2012-05-30 08:45:04 UTC 
Verified the bug using sssd-1.8.0-32.el6. 

Tested by disabling anonymous bind in the LDAP server. The DOMAIN section of sssd.conf was configured with default bind values as given below.

[domain/LDAP]
debug_level = 9
id_provider = ldap
ldap_uri = ldap://SERVER
ldap_search_base = dc=example,dc=com
ldap_schema = rfc2307bis
ldap_group_object_class = groupOfNames

ldap_default_bind_dn = <BIND_DN>
ldap_default_authtok = <PASSWORD>

The user lookup was successful.
Comment 4 Stephen Gallagher 2012-06-12 13:50:59 UTC 
    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:
Cause: SSSD relies on some information it can retrieve from the RootDSE in order to determine the capabilities of the server. Some servers do not make the RootDSE available via unencrypted, non-authenticated LDAP bind (in violation of the LDAP standard)

Consequence: On such servers, SSSD operates in a slightly degraded mode, being unable to take advantage of any enhanced features of the LDAP server.

Change: SSSD will now make a second attempt to retrieve the RootDSE after it completes a successful bind attempt.

Result: SSSD is now able to take advantage of enhanced features on servers that do not expose the RootDSE to non-authenticated users.
Comment 6 errata-xmlrpc 2012-06-20 11:56:31 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/RHBA-2012-0747.html
Note You need to log in before you can comment on or make changes to this bug.