> Is anyone using foreman with ldap + ssl?
>
> I can authenticate with plain ldap, but when I turn on ssl I am getting:
>
> SSL_connect returned=1 errno=0 state=SSLv3 read finished A: sslv3 alert
> handshake failure
>
>
did you update the port to 636? also are you sure your AD works with SSL? http://support.microsoft.com/kb/247078/en-us
Ohad
···
On Tue, Jul 24, 2012 at 9:23 PM, Gustavo Soares wrote:
I have LDAPS working. Does Foreman not make use of the ssl_ca_file option
in settings for LDAP SSL as well?
···
On Tuesday, July 24, 2012 2:23:55 PM UTC-4, Gus wrote:
>
> Is anyone using foreman with ldap + ssl?
>
> I can authenticate with plain ldap, but when I turn on ssl I am getting:
>
> SSL_connect returned=1 errno=0 state=SSLv3 read finished A: sslv3 alert
> handshake failure
>
> I didn't find any place to set the certs file..
>
> Thanks in advance,
> Gus
>
>
yeap… the port was set to 636… and in fact I were already authenticating
against an AD but a new ldap server was installed in a linux box (AD will
no longer be used)… some machines are already authenticating the users
against it with ssl… therefore I can be pretty sure that ssl is working…
Thanks,
···
On Tue, Jul 24, 2012 at 3:34 PM, Ohad Levy wrote: