On Feb 16, 2010, at 12:16 PM, Roland Gruber wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Javier, > > Javier Henderson schrieb: >> I tried also with the name of the server matching the common name in the >> certificate, it made no difference. >> >> The CA is trusted, the ldap.conf file points to the CA root certificate. >> Note that "ldapsearch -Z" issued on the same machine where LAM is installed >> works fine. >> >> I also made sure that there is only one ldap.conf file in the system. >> >> Is there more debug output available from LAM? > > did you select the right encryption method (TLS/SSL)? For TLS the server > URL is ldap://server and for SSL it is ldaps://server. TLS uses port 389 > as default, SSL 636. > Does the LDAP server log connection attempts? You can also use a tool > like wireshark to make sure LAM connects to the correct port. > > There is no more debug output in LAM. You can try to edit lib/ldap.inc. > Search for "function connect" and remove the "@" before > "ldap_connect"/"ldap_bind". This might print additional system error > messages.
Well, I was using ldap://server:389 with TLS, and it was failing. I just entered ldap://server and indicated to use TLS, and it is now working. -jav ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ Lam-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lam-public
