Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (hermes.apache.org: domain of david@bozemanpass.com
 designates 69.145.82.195 as permitted sender)
Message-ID: <426FDCE7.9000301@bozemanpass.com>
Date: Wed, 27 Apr 2005 11:41:43 -0700
From: David Boreham <david@bozemanpass.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Server SSL config
References: <NBBBJGEAGJAKLIDBKJOPAEBDAMAC.noel@devtech.com>
 <426E585E.1030708@bellsouth.net>
 <1acb4bbe703d16c8d40d3636862962cc@pegacat.com>
In-Reply-To: <1acb4bbe703d16c8d40d3636862962cc@pegacat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Is the current code in SVN supposed to allow LDAP over SSL to be
used without source code modifications (e.g. with a 'real' certificate) ?

I ask because one of our engineers has implemented some
code that allows property file configuration for things
like the ssl port and whether ssl is enabled or not, and the
keystore name and password. He found that server SSL
really wasn't practially usable without these changes.

I was wondering if this duplicates anyone else's effort,
or if we've missed something about configuring SSL.

If not , then I will ask him to submit the patches for review.

Thanks.