You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Alex Karasulu <ao...@bellsouth.net> on 2005/05/01 16:31:08 UTC
[kerberos] Adding kerberos to main
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.
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
Re: [kerberos] Adding kerberos to main
Posted by Alex Karasulu <ao...@bellsouth.net>.
Enrique Rodriguez wrote:
> Alex Karasulu wrote:
>
>> 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?
>
>
> Yes, the implementation of PrincipalStore to use is PrincipalStoreImpl.
>
> Yes, the PrincipalStoreImpl is thin as the beef is in the Command
> (pattern) objects. Since it works, I believe that it is sufficient.
> I've never seen accessors on Command objects, as you committed, nor do
> I see why they are ever useful.
It's not about accessors. As a rule you should never make members
anything but private (you had them as protected). If they need
protected access you just expose a protected accessor for them rather
than making the variable itself protected.
>
>>> 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?
>>
>
> You are right that I should create some user doco. However, I don't
> think it should be about the environment properties, as we planned to
> move these into the system partition.
Even if temporary you can't expect users to figure this out on their
own. Keep in mind releases are for users not us. We talked about
releasing the Kerberos service with ApacheDS on 0.9. Kerberos and all
the parameters needed to run and control it must have some kind of doco
before a release. Releases expose us as a TLP as well as the
foundation. We must make sure we maintain the quality with what is
expected of an Apache project. If the quality of this project is to be
maintained we cannot start thinking, "this is temporary so I will not
documenet it." Even if its in a minimal form you need to take better
care of users.
> A major selling point of ApacheDS was that instead of messing with
> props and command-line interfaces, you could use nice GUI systems over
> LDAP or JMX. I see all this props stuff as temporary, so I'd rather
> not document it since I'm hoping we can toss most of it.
You are right I agree with you here in terms of what should be the right
way to go. This still does not change our duties today even if dealing
with temporary circumstances. The quality of the Kerberos product is
dependent on documentation as well as code.
> What makes sense to make configurable for this release is the user and
> service principals, which means doco about the schema we are using to
> back Kerberos principals, so people can start to use JXplorer or the
> LDIF files to work with user and service principals. I will get on that.
We cannot release ApacheDS with Kerberos unless there is some real doco
so users know what they can do with a 0.9 download.
- Alex
Re: [kerberos] Adding kerberos to main
Posted by Enrique Rodriguez <er...@apache.org>.
Alex Karasulu wrote:
> 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?
Yes, the implementation of PrincipalStore to use is PrincipalStoreImpl.
Yes, the PrincipalStoreImpl is thin as the beef is in the Command
(pattern) objects. Since it works, I believe that it is sufficient.
I've never seen accessors on Command objects, as you committed, nor do I
see why they are ever useful.
>> 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?
You are right that I should create some user doco. However, I don't
think it should be about the environment properties, as we planned to
move these into the system partition. A major selling point of ApacheDS
was that instead of messing with props and command-line interfaces, you
could use nice GUI systems over LDAP or JMX. I see all this props stuff
as temporary, so I'd rather not document it since I'm hoping we can toss
most of it.
What makes sense to make configurable for this release is the user and
service principals, which means doco about the schema we are using to
back Kerberos principals, so people can start to use JXplorer or the
LDIF files to work with user and service principals. I will get on that.
>>
>> Thanks,
>> Alex
>>
>>
Re: Using Eclipse (and Mevenide) for ApacheDS...
Posted by Emmanuel Lecharny <el...@apache.org>.
Hi !
You have choose Eclipse, and you are not alone (sorry, I've no Idea ;-).
I do use eclipse to develop, so I'm using it on ApacheDS. It works
pretty smoothly, but you'll need to set up your env.
1) you have to use 3.0.X version (I suppose that 3.1.0 M6 works, too,
but for compatibility sake, use the current released version)
2) Do NOT use JDK 1.5 for ApacheDS, because it does not work with some
pieces of code (AOP :[ )
3) Install Mevenide, following the doc.
4) Install subclipse, following the doc.
5) Install Maven 1.0.2 (follow the doc, you'll need to create a
MAVEN_HOME environment variable and a ?maven repository - not sure -)
6) Checkout the lastest sources in a separated directory (let's say
<home>/ApacheDS)
7) cd to <home>/ApacheDS/directory/trunk
8) Compile the project
# maven multiproject:install
This will feed the Maven repo
9) Have a coffee. Or two ;)
10) I will send you the .classpath and .project I'm using, it will be
better, you will spare some time ! (as I have to go, you'll get them in
4 hours ...)
11) Enjoy ! And welcome !!!
On Sun, 2005-05-01 at 18:23 +0100, Carlos Trigoso wrote:
> Hi!
>
> I am new to the list. In order to learn I have decided to develop either a
> graphical user interface, or a scripting framework for LDAP administration
> on top of ApacheDS.
>
> This will be Eclipse-based (as sadly this is the only development platform I
> know...)
>
> Has anybody in the list used Eclipse for ApacheDS development? If yes, could
> I have some help with the necessary steps to import the source code as an
> Eclipse project? I am having trouble understanding all the dependencies of
> the code... and what components/libraries I should have in the environment.
>
> I recently installed the Mevenide Eclipse plugin (a Maven plugin)... perhaps
> this will help me to handle the ApacheDS project and do the builds... but I
> am pretty unsure about this. Any advice would be greatly appreciated.
>
> Thank you for your help in advance!
>
> Carlos Trigoso
> 12 Harrow Court
> Bath Road
> Reading
> United Kingdom
>
>
> -----Original Message-----
> From: Alex Karasulu [mailto:aok123@bellsouth.net]
> Sent: 01 May 2005 15:38
> To: Apache Directory Developers List
> Subject: Re: [kerberos] Adding kerberos to main
>
> 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
> >
> >
>
>
>
>
>
>
Using Eclipse (and Mevenide) for ApacheDS...
Posted by Carlos Trigoso <ca...@ntlworld.com>.
Hi!
I am new to the list. In order to learn I have decided to develop either a
graphical user interface, or a scripting framework for LDAP administration
on top of ApacheDS.
This will be Eclipse-based (as sadly this is the only development platform I
know...)
Has anybody in the list used Eclipse for ApacheDS development? If yes, could
I have some help with the necessary steps to import the source code as an
Eclipse project? I am having trouble understanding all the dependencies of
the code... and what components/libraries I should have in the environment.
I recently installed the Mevenide Eclipse plugin (a Maven plugin)... perhaps
this will help me to handle the ApacheDS project and do the builds... but I
am pretty unsure about this. Any advice would be greatly appreciated.
Thank you for your help in advance!
Carlos Trigoso
12 Harrow Court
Bath Road
Reading
United Kingdom
-----Original Message-----
From: Alex Karasulu [mailto:aok123@bellsouth.net]
Sent: 01 May 2005 15:38
To: Apache Directory Developers List
Subject: Re: [kerberos] Adding kerberos to main
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
>
>
Re: [kerberos] Adding kerberos to main
Posted by Alex Karasulu <ao...@bellsouth.net>.
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
>
>