Hide Forgot
Right now, SSSD is dependent on openldap's ldap.conf to set the required minssf level for communication when using SASL (such as GSSAPI). We should add a new integer option ldap_sasl_minssf that takes the following defaults: LDAP provider: use ldap.conf values IPA provider: 72
Verified in version: # rpm -qi sssd | head Name : sssd Relocations: (not relocatable) Version : 1.8.0 Vendor: Red Hat, Inc. Release : 23.el6 Build Date: Fri 20 Apr 2012 11:30:39 PM IST Install Date: Wed 25 Apr 2012 07:28:48 PM IST Build Host: x86-003.build.bos.redhat.com Group : Applications/System Source RPM: sssd-1.8.0-23.el6.src.rpm Size : 7874744 License: GPLv3+ Signature : (none) Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> URL : http://fedorahosted.org/sssd/ Summary : System Security Services Daemon
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: ldap_sasl_minssf was added to the configuration of SSSD. Through this option is is possible to specify minimal level of encryption SSSD (or rather LDAP library) should use when communicating with a server.
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 +1 @@ -ldap_sasl_minssf was added to the configuration of SSSD. Through this option is is possible to specify minimal level of encryption SSSD (or rather LDAP library) should use when communicating with a server.+ldap_sasl_minssf was added to the configuration of SSSD. Through this option it is possible to specify minimal level of encryption SSSD (or rather, the LDAP library used by SSSD) should use when communicating with a server.
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