On Tue, Jul 30, 2013 at 11:53:34AM -0400, Chris Hartman wrote:
Ah. It appears I now have a reason to perform SASL binds over LDAPS.
Active Directory guys are complaining; they say the AD server is throwing
errors that some clients are performing unsigned SASL binds. When signing
is required on the server, bind attempts from SSSD clients fail.
So, I ask again, is there a way I can force my SSSD clients to use LDAPS?
Can you paste the error you saw on the client? (Or even the server side