Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 18752 invoked from network); 1 May 2005 14:38:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 May 2005 14:38:06 -0000 Received: (qmail 62347 invoked by uid 500); 1 May 2005 14:39:30 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 62194 invoked by uid 500); 1 May 2005 14:39:30 -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 62178 invoked by uid 99); 1 May 2005 14:39:29 -0000 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=FROM_ENDS_IN_NUMS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of aok123@bellsouth.net designates 205.152.59.64 as permitted sender) Received: from imf16aec.mail.bellsouth.net (HELO imf16aec.mail.bellsouth.net) (205.152.59.64) by apache.org (qpsmtpd/0.28) with ESMTP; Sun, 01 May 2005 07:39:29 -0700 Received: from [172.16.1.7] ([65.80.200.112]) by imf16aec.mail.bellsouth.net (InterMail vM.5.01.06.11 201-253-122-130-111-20040605) with ESMTP id <20050501143803.WTUY1994.imf16aec.mail.bellsouth.net@[172.16.1.7]> for ; Sun, 1 May 2005 10:38:03 -0400 Message-ID: <4274E9CA.9050202@bellsouth.net> Date: Sun, 01 May 2005 10:38:02 -0400 From: Alex Karasulu User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: [kerberos] Adding kerberos to main References: <4274E82C.6010004@bellsouth.net> In-Reply-To: <4274E82C.6010004@bellsouth.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Alex Karasulu wrote: > Enrique, > > The KerberosProtocolProvider constructor takes a KdcConfiguration and > a PrincipalStore argument. I was adding support for the Kerberos > service to the executable. This is to get he 0.9 release out with > Kerberos. I was wondering what implementation of PrincipalStore you > were using. I basically got stuck when I was instantiating > KerberosProtocolProvider. Ok I just found PrincipalStoreImpl ... looks really really thin (few lines). Is this sufficient? What pattern (Command pattern?) did you use with this ContextOperation? > > > BTW while going through the code I noticed a few things and had some > concerns regarding our upcoming release. > > > There is barely any documentation in most of the Kerberos code. > Primarily referring to javadocs and a user guide. If we are releasing > Kerberos we need some documentation. In general (this goes for me > too) this project has to do a better job at getting Javadocs done. > Furthermoe we need some sort of user guide similar to the one for the > ldap portion of apacheds. Here's what I'm referring to exactly: > > > http://directory.apache.org/subprojects/apacheds/users/index.html > > > I was asking myself how our users will be able to figure out a means > to configure the kerberos server. There really is no guide at this > point and we're about to announce that we have a Kerberos server for > them inside ApacheDS. At a bare minimum before we release we need to > describe all the different environment options. WDYT? > > Thanks, > Alex > >