Just as a follow up to this, on ~5% of our hosts (RHEL[456]), crond
would be unable to connect to the ldapserver after /etc/ldap.conf was
updated to use SSL. Restarting crond fixed the issue.
On Thu, Jul 19, 2012 at 10:54 AM, David Nguyen d_k_ngu...@yahoo.com wrote:
The cert is self-signed, but
Hi,
what kind of certificate do you use, selfsigned? Are the certificates signed by
the same CA?
Am 18.07.12, schrieb David Nguyen d_k_ngu...@yahoo.com:
Hi all,
I have a strange one. My current setup is working perfectly. client1
is able to connect to ldap-server1 via SSL and
The cert is self-signed, but by different CA's (each server has it's own CA).
You know what? I took your hint and signed a new server cert using
the working ldap server's CA and voila, it started working. Thank
you so much! I've been scratching my head over this one for days
David
On Thu,
Hi all,
I have a strange one. My current setup is working perfectly. client1
is able to connect to ldap-server1 via SSL and everything is working
correctly. I then had a need to add another ldap server (ldap-server2)
as a multi-master replica and everything is working (user auth, sudo
via ldap
