You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user reported that OpenLDAP returned an error while setting LDAP_OPT_X_SASL_NOCANON. SSSD treats all errors while setting LDAP options as fatal and abort connecting. I think this particular option (and maybe others) should not be treated as fatal, we could either:
- only set the nocanon option if SSSD is configured to perform a SASL bind later on
- do not fail during setting the option, just complain to the logs that setting the option failed and a SASL bind might fail later
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/1100
A user reported that OpenLDAP returned an error while setting LDAP_OPT_X_SASL_NOCANON. SSSD treats all errors while setting LDAP options as fatal and abort connecting. I think this particular option (and maybe others) should not be treated as fatal, we could either:
Comments
Comment from dpal at 2011-12-01 15:47:11
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.7.0
owner: somebody => jhrozek
Comment from jhrozek at 2011-12-07 18:49:13
Fields changed
patch: 0 => 1
status: new => assigned
Comment from sgallagh at 2011-12-08 17:39:03
Fields changed
milestone: SSSD 1.7.0 => SSSD 1.5.16
Comment from sgallagh at 2011-12-08 20:34:55
Fixed by:
- 09b7183 (master)
- 17707de (sssd-1-6)
- a8e3b90 (sssd-1-5)
resolution: => fixed
status: assigned => closed
Comment from dpal at 2012-01-19 03:07:54
Fields changed
rhbz: => 0
Comment from jhrozek at 2017-02-24 14:59:40
Metadata Update from @jhrozek:
The text was updated successfully, but these errors were encountered: