The common name is correct and the exact same CA chain works with yum on
a server signed by the same CA our Active Directory servers are signed
with. So we know the CA chain file includes everything it needs.
HPC Systems Engineer
Information Technology Services - WSU
On 10/02/2017 11:15 AM, Dan Corrigan wrote:
In my experiences, TLS failures are almost always due to a small
handful of problems.
Two that come to mind immediately are
1. Common name matching.
Check the common name for the cert and make sure your requests are
going to that name.
2. Not including certs.
Make sure you are including all certs needed to validate your server's
Make sure you are pointing to the correct directory that includes
these certs i.e. ldap_tls_cacertdir
On Mon, 2017-10-02 at 11:01 -0700, Jeff White wrote:
> I'm attempting to enable LDAP server TLS certificate validation with
> "ldap_tls_reqcert = demand". However, when I set that value to anything
> other than "never", sssd does not work. By that I mean sssd will start
> as normal but no ID lookups are successful and I see "Input/output
> error" in the log. This occurs regardless of what CA certificate chain
> I give it (via ldap_tls_cacert). I have even tried using a known
> working chain that I use to access yum repos which uses TLS certificates
> from the same CA as our Active Directory.
> Any ideas?
> sssd-users mailing list --sssd-users(a)lists.fedorahosted.org
> To unsubscribe send an email tosssd-users-leave(a)lists.fedorahosted.org
sssd-users mailing list -- sssd-users(a)lists.fedorahosted.org
To unsubscribe send an email to sssd-users-leave(a)lists.fedorahosted.org