Learn more about these different git repos.
Other Git URLs
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:
Specify the SASL mechanism to use. Currently only GSSAPI is tested and supported.
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
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
rhbz: => 0
Metadata Update from @mpizzoli:
- Issue set to the milestone: SSSD 1.9.0
to comment on this ticket.