Manpage for ldap_sasl_mech should be made more clear

[sssd-bot]

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/1180

• Created at 2012-02-07 17:25:51 by mpizzoli
• Closed as Invalid
• Assigned to nobody

---

As reported in the mailing list (https://fedorahosted.org/pipermail/sssd-devel/2012-February/008505.html) SSSD fails to connect to the LDAP server if it finds only GSSAPI as supportedSASLMechanisms.
It should be assuming simple bind is always available.

Comments

---

Comment from sgallagh at 2012-02-07 18:12:39

This was actually a misconfiguration due to the man page reading:

       ldap_sasl_mech (string)
           Specify the SASL mechanism to use. Currently only GSSAPI is tested and supported.

           Default: none

The user had set

ldap_sasl_mech = none

We should fix the manpage so it reads "not set" instead of "none" to avoid confusion.

component: SSSD => Documentation
priority: major => trivial

---

Comment from sgallagh at 2012-02-09 16:10:23

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.0
resolution: => invalid
status: new => closed
summary: SSSD LDAP should be assuming that bind SIMPLE is always available => Manpage for ldap_sasl_mech should be made more clear

---

Comment from dpal at 2012-02-10 21:32:56

Fields changed

rhbz: => 0

---

Comment from mpizzoli at 2017-02-24 15:01:41

Metadata Update from @mpizzoli:

• Issue set to the milestone: SSSD 1.9.0