Just looking for another bug and thought I'd comment. I have TLS working fine with 0.9.8.3-8.
First, let's clear up some confusion: LDAPS is SSL over port 636. TLS starts unencrypted on port 389 and then negotiates TLS (still on port 389). First of all, check ldap from the command line: ldapsearch -W -x -LLL -D cn=admin,dc=example,dc=com -H ldap://ldap.example.com -b dc=example,dc=com -P3 -ZZ Ensure the host string matches the certificate - using a host of "localhost" will fail if the certificate says "ldap.example.com". $ldapservers->SetValue($i,'server','host','ldap.example.com'); // as I said above, 389 is for TLS, 636 for LDAPS /* The port your LDAP server listens on (no quotes). 389 is standard. */ // $ldapservers->SetValue($i,'server','port','389'); $ldapservers->SetValue($i,'server','tls',true); On an older version I used to have to comment out line 1604 in /usr/share/phpldapadmin/functions.php which sets LDAP protocol v3 as it broke sign-in (and we disable v2 anyhow). I do not need to do this in etch. Hope this helps, Adrian -- Email: [EMAIL PROTECTED] -*- GPG key available on public key servers Debian GNU/Linux - the maintainable distribution -*- www.debian.org Avoid working with children, animals and Microsoft "operating" systems -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
