Return-Path: 
 <dev-return-22999-apmail-directory-dev-archive=directory.apache.org@directory.apache.org>
Delivered-To: apmail-directory-dev-archive@www.apache.org
Received: (qmail 90648 invoked from network); 30 Dec 2007 18:34:28 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 30 Dec 2007 18:34:28 -0000
Received: (qmail 62826 invoked by uid 500); 30 Dec 2007 18:34:16 -0000
Delivered-To: apmail-directory-dev-archive@directory.apache.org
Received: (qmail 62777 invoked by uid 500); 30 Dec 2007 18:34:16 -0000
Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@directory.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@directory.apache.org>
List-Post: <mailto:dev@directory.apache.org>
List-Id: <dev.directory.apache.org>
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Delivered-To: mailing list dev@directory.apache.org
Received: (qmail 62766 invoked by uid 99); 30 Dec 2007 18:34:16 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 Dec 2007 10:34:16 -0800
X-ASF-Spam-Status: No, hits=1.2 required=10.0
	tests=SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received: from [81.169.146.161] (HELO mo-p00-ob.rzone.de) (81.169.146.161)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 Dec 2007 18:33:53 +0000
X-RZG-CLASS-ID: mo00
X-RZG-AUTH: kR2YrGeU3i5GJZNxbYfAbITnBeX/YWiFZ/RSZNN7D9RkvGeL2Q5qpQ75sw==
Received: from [127.0.0.1] (p548FBDFB.dip.t-dialin.net [84.143.189.251])
	by post.webmailer.de (klopstock mo34) (RZmta 14.6)
	with ESMTP id j03c53jBUHxg4x for <dev@directory.apache.org>;
	Sun, 30 Dec 2007 19:33:55 +0100 (MET)
	(envelope-from: <stefan@labeo.de>)
Message-ID: <4777E551.3000604@labeo.de>
Date: Sun, 30 Dec 2007 19:37:05 +0100
From: Stefan Zoerner <stefan@labeo.de>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Configuration in bigbang branch: names of SASL attributes and
 elements
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Hi all!

I am playing around with SASL for my 2.0 documentation examples (Basic 
User's Guide). I was able to authenticate via DIGEST-MD5 against the 
sample partition of the guide, after adjusting some attributes in 
server.xml.

During this I had to modify the attribute "saslHost" from element 
<ldapServer>, and there is also a "saslPrincipal" (which I did not use, 
because no GSSAPI). Other sub elements of ldapServer are named 
saslSomething (saslQop, saslRealms).

But I had also to modify the value of attribute "searchBaseDn". I assume 
this value is only used for user detection in SASL. I therefore propose 
the name saslSearchBaseDn in order to make this consistent.

Another element name I wondered about was "supportedMechanisms". I 
recommend to rename it to "supportedSaslMechanisms", because this is the 
name used in the Root DSE for publication. In fact, it is 
supportedSASLMechanisms, but this does not fit the name scheme.

Thoughts?

Thanks in advance,
     Stefan