Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 96369 invoked from network); 22 Nov 2010 14:18:25 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 22 Nov 2010 14:18:25 -0000 Received: (qmail 30407 invoked by uid 500); 22 Nov 2010 14:18:56 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 29360 invoked by uid 500); 22 Nov 2010 14:18:54 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 29353 invoked by uid 99); 22 Nov 2010 14:18:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Nov 2010 14:18:53 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of pajbam@gmail.com designates 209.85.215.50 as permitted sender) Received: from [209.85.215.50] (HELO mail-ew0-f50.google.com) (209.85.215.50) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Nov 2010 14:18:44 +0000 Received: by ewy7 with SMTP id 7so3751696ewy.37 for ; Mon, 22 Nov 2010 06:18:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:from:content-type :content-transfer-encoding:subject:date:message-id:to:mime-version :x-mailer; bh=y3e0Nr+bCtRvOY0IayLhHHTiWtMdMenUzcvvknRloI0=; b=gmudvZPxWj6RIBgI1iRRybs1idWSdRbc0OLEdZvWIkupjoLXcQSFG/RhTxcHUr6i3y wGy9kvMlq+wdVWx565JaeFiWpBifgmedT2aImt05Z8dedc+9ybJLH6SvwA4hfOTXHqht e5oCKpUDN0BNWLGQgJvVP/SbWTqLVvOtO77Pk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:from:content-type:content-transfer-encoding:subject:date :message-id:to:mime-version:x-mailer; b=uT85RNF8E4m2e7ULahdGRx/Ebu2LLGWpPHSweVcKhu7d5nuolhtOt4eyusd81HC6X6 C5qGVNoAW8DCASQWRbfso/MQ4oq0651xW2GgTV9JQCs0uxHYrod0vcZu6PDOt7aT3v0V +pxzlCnMoYUd9v8nZ0GarBKGYe3EgqevBPQZ0= Received: by 10.216.16.85 with SMTP id g63mr3784255weg.114.1290435455468; Mon, 22 Nov 2010 06:17:35 -0800 (PST) Received: from [192.168.0.52] (lon92-10-78-226-4-211.fbx.proxad.net [78.226.4.211]) by mx.google.com with ESMTPS id p4sm2293737wej.4.2010.11.22.06.17.33 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 22 Nov 2010 06:17:34 -0800 (PST) Sender: Pierre-Arnaud Marcelot From: Pierre-Arnaud Marcelot Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: [ApacheDS] Enablement of LDAPS (SSL) Service in ApacheDS 2.0 configuration Date: Mon, 22 Nov 2010 15:17:32 +0100 Message-Id: <6AABB0C6-5237-4270-BF11-0EF0B5542A9B@marcelot.net> To: Apache Directory Developers List Mime-Version: 1.0 (Apple Message framework v1081) X-Mailer: Apple Mail (2.1081) X-Virus-Checked: Checked by ClamAV on apache.org Hi Dev, A quick question, while I'm writing the configuration editor for = ApacheDS 2.0 configuration. LDAP and LDAPS servers configuration is shared in the = 'ads-serverId=3DldapServer,ou=3Dservers,ads-directoryServiceId=3Ddefault,o= u=3Dconfig' entry. Like other servers (Kerberos, ChangePassword, HTTP, etc.), this entry = has a 'ads-enabled' attribute. But how do I know which servers (LDAP and/org LDAPS) should be enabled? Should I look at the enablement of the transports to see which ones are = enabled? Should we add a specific 'ads-enable-ldaps' attribute to the = LDAP Server configuration? WDYT ? Regards, Pierre-Arnaud=