[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: TLS fails to bind (Please help)
Lorenzo Thurman <lorenzo@thethurmans.com> writes:
> I've been trying to get this working for days now. I've searched high
> and low and read a lot of manuals. I have LDAP working on port 389 and
> can use ldapsearch w/o trouble as long as I start slapd on port 389
> only . Now I want TLS to work, but I when I start slapd, I see that it
> fails to bind on port 636. netstat -l shows that slapd is listening on
> that port and also on port 389. I also noticed that slapd calls
> ldap_sasl_bind although I compiled openldap w/o sasl support,
> twice. Is that my problem, I need SASL? None of the documentation
> said it was required. Anyway here is some of the output when starting
> slapd with these options:
> -d -1 -h 'ldap:// ldaps:// ldapi://%2fvar%2frun%2fopenldap%2fslapd.sock
>
> If anyone has any ideas, I'd love to hear them.
1. did you create certificates and have you configured slapd and ldap
clients to use TLS?
2. What is the result of 'ldapsearch -H ldap://my.host:389 -b "my
base" -x -ZZ'
-Dieter
--
Dieter Klünter | Systemberatung
http://www.dkluenter.de
GPG Key ID:01443B53