[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: New problem is ports I think

To: "Jim C" <jcllings@tsunamicomm.net>, <openldap-software@OpenLDAP.org>
Subject: RE: New problem is ports I think
From: "Howard Chu" <hyc@symas.com>
Date: Wed, 28 Aug 2002 00:32:17 -0700
Cc: <pgina-general@lists.sourceforge.net>
Importance: Normal
In-reply-to: <3D6C72AC.3010205@tsunamicomm.net>

> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Jim C

> My ldap server is configured to use port 389 for both encrypted and
> unencrypted traffic.
> Is there a way to split the encrypted traffic off to port 636?

start slapd with ' -h "ldap:// ldaps://" ' and it will listen on both ports.
Clients can connect however they wish - plaintext on 389, plaintext
w/StartTLS on 389, or SSL on 636.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support

Follow-Ups:
- Re: New problem is ports I think
  - From: Jim C <jcllings@tsunamicomm.net>

References:
- New problem is ports I think
  - From: Jim C <jcllings@tsunamicomm.net>

Prev by Date: Migrating to v 2.1.x ?
Next by Date: Re: New problem is ports I think
Index(es):
- Chronological
- Thread