Is there a specific way, i have to configure the slapd to listem to 636 port..? And does the 389 search is a secure search...? Is there a particular way of Starting the TLS operation..? Thanks in advance
On Fri, Jan 4, 2013 at 4:31 PM, Quanah Gibson-Mount quanah@zimbra.comwrote:
--On Friday, January 04, 2013 4:09 PM -0800 Bheeshma SM < bheeshma.manjunath@gmail.com> wrote:
Hi guys.
I have a problem in Openldap 2.4.33 on RHEL 5.8
I am able to do a " ldapsearch -x -p 389 -h -D<> -w<> -b<> "
but i am not able to do
" ldapsearch -x -p 636 -h -D<> -w<> -b<>
Sounds like slapd is not configured to listen to port 636. No amount of mucking with ldapsearch is going to change that.
I would note that you can do secure searches over port 389 just fine. Simply use the startTLS operation.
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc.
Zimbra :: the leader in open source messaging and collaboration
--On Friday, January 04, 2013 4:45 PM -0800 Bheeshma SM bheeshma.manjunath@gmail.com wrote:
Is there a specific way, i have to configure the slapd to listem to 636 port..?
And does the 389 search is a secure search...?
Is there a particular way of Starting the TLS operation..?
Thanks in advance
As I already stated. Use "startTLS" with port 389 and it will be secure. This is all well documented. Please read the slapd(8C) manual page if you want to understand the options for which port(s) slapd should listen to.
Please read the ldapsearch(1) man page to see the options to ldapsearch that you can use to require startTLS.
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
openldap-technical@openldap.org