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

Port 636 and SLAPD(8)

To: openldap-technical@openldap.org
Subject: Port 636 and SLAPD(8)
From: jumpgroup@aol.com
Date: Wed, 8 Jan 2014 10:10:24 -0500 (EST)
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20121107; t=1389193825; bh=m+d5ksLE0NOrCDQbgauZ8XAiI6UFbpW4LuDwWp1sdgE=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=BihfpHKdyAz/QtFN8EiPzB6lUkB1EdakYMW7DT8Q6nRMJrbuK15tsEUEo+SPit1d0 tG/xnb2k6I5ceLcwru5KAw9TJGDzhzVd2ZPDxlTo+X0kUbENkamSkeb7SiA8gy/Jhx T+VGygUG4/GRxhxJt53hSBwpRxUaZki9MdLrkX9Y=

Hello Experts,

In need of a little guidance please.

I'm installed OpenLdap 2.4.23 on RHEL in a sandbox and would like to enable SSL on port 636. All documentation references SLAPD(5), but since I'm using SLAPD(8), I do not know have the slapd.conf file. Looking for the current SLAPD(8) method of configuring this along with starting the service to support port 636.

Thanks in advance!

Jeff P.

Follow-Ups:
- Re: Port 636 and SLAPD(8)
  - From: Michael Proto <michael.proto@tstllc.net>

Prev by Date: Re: replication of databases with different backends???
Next by Date: Re: Port 636 and SLAPD(8)
Index(es):
- Chronological
- Thread