#1180 Manpage for ldap_sasl_mech should be made more clear
Closed: Invalid None Opened 8 years ago by mpizzoli.

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.


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

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

Fields changed

rhbz: => 0

Metadata Update from @mpizzoli:
- Issue set to the milestone: SSSD 1.9.0

3 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2222

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata