Mark, Our LDAP servers accept StartTLS sessions on port 389 without problem. This command works fine on our LDAP servers, (substituting hostname and uid of course):
$ ldapsearch -x -p 389 -h ldap.example.com -D "uid=testUID,ou=University of California Irvine, o=University of California, c=US" -ZZ -W uid=* According to the logs from tcpdump and wireshark, the TLS handshake did not fail, and the command succeeds with a proper userID and password. Since I also cannot find anything creating a StartTLSRequest in DSpace, I am now working on a Shibboleth login instead. Peace, Sean Mark H. Wood wrote: > ldaps: typically runs on port 636, not 389. If you speak ldaps: to a > port listening for ldap: then the TLS handshake will fail. Mark H. Wood wrote: > I don't see a StartTlsRequest being created anywhere in DSpace. It > appears that this is not currently supported. -- Sean Hennessee Central Computing Support Office of Information Technology UC Irvine ... . .- -. / .... . -. -. . ... ... . . ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
