Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 95192 invoked from network); 15 Jul 2006 23:15:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Jul 2006 23:15:18 -0000 Received: (qmail 74746 invoked by uid 500); 15 Jul 2006 23:15:18 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 74687 invoked by uid 500); 15 Jul 2006 23:15:17 -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 74676 invoked by uid 99); 15 Jul 2006 23:15:17 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Jul 2006 16:15:17 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of ersin.er@gmail.com designates 64.233.166.176 as permitted sender) Received: from [64.233.166.176] (HELO py-out-1112.google.com) (64.233.166.176) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Jul 2006 16:15:09 -0700 Received: by py-out-1112.google.com with SMTP id d80so1108542pyd for ; Sat, 15 Jul 2006 16:14:43 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=VQi6qbxzr7FNY57fUANLzKUHajlR5rEsy6MRcyJenAtMesFATIElSZQHpyK4/o5xz19OofrmnNuLwO6V7hQCvlnHuW+2vmMdueOic4fLZrGC20bGbCY/vCLfetar4heS2CTQ63lcEzq09zQ+F9K2DRhB26SdgZsNg1XRg7VgwP0= Received: by 10.35.62.19 with SMTP id p19mr1605023pyk; Sat, 15 Jul 2006 16:14:43 -0700 (PDT) Received: by 10.35.127.12 with HTTP; Sat, 15 Jul 2006 16:14:43 -0700 (PDT) Message-ID: Date: Sun, 16 Jul 2006 02:14:43 +0300 From: "Ersin Er" To: dev@directory.apache.org Subject: Real world experiences with securing directory servers in the context of access control MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi all, I would like to learn your (as directory administrators) experiences with configuring access control on Netscape, OpenLDAP and any other directory servers. What are the configurations as first time task just after the installation? What are being needed in time? And what were the requirements that you could not achieve because of your server's incapabilities? Thanks in advance. -- Ersin