You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Peter Donald <do...@apache.org> on 2001/08/29 05:48:01 UTC
Re: cvs commit: jakarta-avalon-cornerstone/apps/ftpserver/src/java/org/apache/avalon/ftpserver/interfaces UserManagerInterface.java
+1 to idea of UserManagement Block
On Wed, 29 Aug 2001 13:38, hammant@apache.org wrote:
> /**
> * Ftp server starting point. Avalon framework will load this
> @@ -66,12 +56,14 @@
>
> private static final String SOCK_MANAGER =
> "org.apache.avalon.cornerstone.services.sockets.SocketManager"; private
> static final String CONN_MANAGER =
> "org.apache.avalon.cornerstone.services.connection.ConnectionManager"; +
> private static final String TIME_SCHEDULER =
> "org.apache.avalon.cornerstone.services.scheduler.TimeScheduler";
>
...snip...
> try{
> mSocManager =
> (SocketManager)compManager.lookup(SOCK_MANAGER); mConManager =
> (ConnectionManager)compManager.lookup(CONN_MANAGER); +
> mTimeScheduler = (TimeScheduler)compManager.lookup(TIME_SCHEDULER); +
> //TODO (PH) should be a block itself.
> } catch (ComponentException ce) {
> getLogger().error("compose(): ComponentException",ce);
Instead of defining string like above I would recomend that this be replaced
with something like
mTimeScheduler =(TimeScheduler)compManager.lookup(TimeScheduler.ROLE);
ie InterfaceName.ROLE should contain string representation.
--
Cheers,
Pete
--------------------------------------------------
you've made a dangerous leap right over common
sense, like some kind of metaphysical Evil Knievel
--------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: James & Avalon FtpServer UserManager ?
Posted by Peter Donald <do...@apache.org>.
On Thu, 30 Aug 2001 18:45, Charles Benett wrote:
> For Avalon folk:
> - over in James we have started on a block - userstore - that we
> intended to migrate to Avalon once it was tested. Its designed to serve
> multiple Avalon sars/ bars. Essentially, the userstore is a set of
> UserRepositories. You might have different repositories for, e.g. local
> email users, authorised ftp users and an email list. There is a base
> User interface (currently just name & password) from which you can
> extend application specific users. e.g JamesUser for email, which has
> aliases and forwarding info. The current implementations support hashed
> passwords. We have filesystem and database storage implementations. See
> jakarta-james/proposals/userstore
> - a quick look at the ftp user stuff suggests the james user material is
> much simpler thean the ftp material, but the ftp could be done as an
> extension of the common base.
Sounds good. However could we have a terminology change. Namely instead of
using UserRepositories could we use the term Realm as that would make it much
easier to integrate into J2EE style terminology. There is currently a JSR in
progress to standardize and interface for Realms but last I checked it had
just started.
> For James folk:
> - Avalon has just added an ftp server (in jakarta-avalon-cornerstone)
> with an extensive user management facility. (Which does quite a lot more
> than is needed for james)
>
> I suggest we move the james userstore block to avalon and then look at
> combining that with the ftpserver user stuff.
+1
--
Cheers,
Pete
------------------------------------------------------
"If people are good only because they fear punishment,
and hope for reward, then we are a sorry lot indeed."
-Albert Einstein
------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: James & Avalon FtpServer UserManager ?
Posted by Paul Hammant <Pa...@yahoo.com>.
>
>
>I suggest we move the james userstore block to avalon and then look at
>combining that with the ftpserver user stuff.
>
Good idea.
Your's sounds quite powerful and maybe only needs small mods for it to
be usable for FtpServer.
-PH
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: James & Avalon FtpServer UserManager ?
Posted by Paul Hammant <Pa...@yahoo.com>.
>
>
>I suggest we move the james userstore block to avalon and then look at
>combining that with the ftpserver user stuff.
>
Good idea.
Your's sounds quite powerful and maybe only needs small mods for it to
be usable for FtpServer.
-PH
---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org
James & Avalon FtpServer UserManager ?
Posted by Charles Benett <ch...@benett1.demon.co.uk>.
Paul Hammant wrote:
>
> Peter Donald wrote:
>
> >+1 to idea of UserManagement Block
> >
> For just FtpServer or should James and FtpServer find commonality and
> make a cornerstone "service" style block ?
>
> One stage further, could/should it have multiple implementations
> including one that uses JNI <spit> to access real (rather than virtual)
> users ?
For Avalon folk:
- over in James we have started on a block - userstore - that we
intended to migrate to Avalon once it was tested. Its designed to serve
multiple Avalon sars/ bars. Essentially, the userstore is a set of
UserRepositories. You might have different repositories for, e.g. local
email users, authorised ftp users and an email list. There is a base
User interface (currently just name & password) from which you can
extend application specific users. e.g JamesUser for email, which has
aliases and forwarding info. The current implementations support hashed
passwords. We have filesystem and database storage implementations. See
jakarta-james/proposals/userstore
- a quick look at the ftp user stuff suggests the james user material is
much simpler thean the ftp material, but the ftp could be done as an
extension of the common base.
For James folk:
- Avalon has just added an ftp server (in jakarta-avalon-cornerstone)
with an extensive user management facility. (Which does quite a lot more
than is needed for james)
I suggest we move the james userstore block to avalon and then look at
combining that with the ftpserver user stuff.
Thoughts?
Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Re : UserManager ?
Posted by Peter Donald <do...@apache.org>.
On Wed, 29 Aug 2001 19:14, Paul Hammant wrote:
> Peter Donald wrote:
> >+1 to idea of UserManagement Block
>
> For just FtpServer or should James and FtpServer find commonality and
> make a cornerstone "service" style block ?
If it can be done. First it may be best to just refactor inside ftpserver.
Then look at commonalities and other User systems (like jetspeed+turbine,
james and ftpserver) to see where they overlap. I think the commonalities are
essentially.
Every API has notion of "user". Associated with each user are a number of
"attributes". Example attributes could be username, password, home directory,
mail spool, Human presentable name etc. In some cases you may even allow
complex-types/objects to be associated with a User.
The actual implementation could arbitrarily map this to any underlying
format. Some underlying formats include;
* database
* NT Realm
* Unix /etc/passwd
* LDAP
* simple xml format
* YP directory (or whatever it is called nowdays ... ndis???)
etc.
Each has a different "schema" and allows different set of attributes.
Hopefully when constructing UserManager you could specify appropriate schema.
At one stage I was talking about this and you can see the start of it in
cornerstone.services.security. However the company I was writing it for went
under so ... ;)
--
Cheers,
Pete
---------------------------------------------------
"If you don't know where you want to go, we'll make
sure you get taken."
Microsoft ad slogan, translated into Japanese.
---------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Re : UserManager ?
Posted by Peter Donald <do...@apache.org>.
On Wed, 29 Aug 2001 19:30, Paul Hammant wrote:
> >> +1 to idea of UserManagement Block
> >
> > For just FtpServer or should James and FtpServer find commonality and
> > make a cornerstone "service" style block ?
> >
> > One stage further, could/should it have multiple implementations
> > including one that uses JNI <spit> to access real (rather than
> > virtual) users ?
>
> Further still, implementations like ..
>
> * RemoteUserManager
>
> ... in addition to ...
>
> * VirtualUserManager
> * NativeAuthenticationUserManager
>
> Hmm, loads of overlap there with Sun LDAP kits.
Yep. I was originally modelling interface via a vastly somplified JNDI
directory context ;)
--
Cheers,
Pete
*------------------------------------------------*
| Trying is the first step to failure. |
| So never try, Lisa - Homer Jay Simpson |
*------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: Re : UserManager ?
Posted by Paul Hammant <Pa...@yahoo.com>.
>
>
>> +1 to idea of UserManagement Block
>
> For just FtpServer or should James and FtpServer find commonality and
> make a cornerstone "service" style block ?
>
> One stage further, could/should it have multiple implementations
> including one that uses JNI <spit> to access real (rather than
> virtual) users ?
Further still, implementations like ..
* RemoteUserManager
... in addition to ...
* VirtualUserManager
* NativeAuthenticationUserManager
Hmm, loads of overlap there with Sun LDAP kits.
Maybe RemoteUserManager could <depend> on some API forwarding blocks ...
* RMIForwarder
* SOAPForwarder
* IIOPForwarder
... provided the dreaded RemoteException is handled and hidden completly.
Everything would be laced together in assembly.xml in the ususal way.
- Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
James & Avalon FtpServer UserManager ?
Posted by Charles Benett <ch...@benett1.demon.co.uk>.
Paul Hammant wrote:
>
> Peter Donald wrote:
>
> >+1 to idea of UserManagement Block
> >
> For just FtpServer or should James and FtpServer find commonality and
> make a cornerstone "service" style block ?
>
> One stage further, could/should it have multiple implementations
> including one that uses JNI <spit> to access real (rather than virtual)
> users ?
For Avalon folk:
- over in James we have started on a block - userstore - that we
intended to migrate to Avalon once it was tested. Its designed to serve
multiple Avalon sars/ bars. Essentially, the userstore is a set of
UserRepositories. You might have different repositories for, e.g. local
email users, authorised ftp users and an email list. There is a base
User interface (currently just name & password) from which you can
extend application specific users. e.g JamesUser for email, which has
aliases and forwarding info. The current implementations support hashed
passwords. We have filesystem and database storage implementations. See
jakarta-james/proposals/userstore
- a quick look at the ftp user stuff suggests the james user material is
much simpler thean the ftp material, but the ftp could be done as an
extension of the common base.
For James folk:
- Avalon has just added an ftp server (in jakarta-avalon-cornerstone)
with an extensive user management facility. (Which does quite a lot more
than is needed for james)
I suggest we move the james userstore block to avalon and then look at
combining that with the ftpserver user stuff.
Thoughts?
Charles
---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org
Re : UserManager ?
Posted by Paul Hammant <Pa...@yahoo.com>.
Peter Donald wrote:
>+1 to idea of UserManagement Block
>
For just FtpServer or should James and FtpServer find commonality and
make a cornerstone "service" style block ?
One stage further, could/should it have multiple implementations
including one that uses JNI <spit> to access real (rather than virtual)
users ?
-PH
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: cvs commit:
jakarta-avalon-cornerstone/apps/ftpserver/src/java/org/apache/avalon/ftpserver/interfaces
UserManagerInterface.java
Posted by Berin Loritsch <bl...@apache.org>.
Peter Donald wrote:
>
> On Wed, 29 Aug 2001 22:46, Berin Loritsch wrote:
> > Peter Donald wrote:
> > > +1 to idea of UserManagement Block
> >
> > Is there any way the UserManagement Block can be authentication method
> > agnostic?
>
> Yes and no. In JAAS users are *Subjects* and consist of a number of
> Principles. The Principle may represent the Subject in different systems or
> via different access methods. For instance you may have a different Principle
> for Unix user login, and a different principle for Kerberos (sp?) login, and
> a different for PKI, different for biometric etc.
I have looked at JAAS alot. Basically a "Subject" is in effect a complex
Principle (it extends Principle I believe) that is an aggregate. When authenticated
via JAAS, the Subject is the Principal tested against, and you get a positive
if any of the correct methods worked (i.e. if a Certificate is presented, JAAS
can be configured to allow that to be enough).
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: cvs commit: jakarta-avalon-cornerstone/apps/ftpserver/src/java/org/apache/avalon/ftpserver/interfaces UserManagerInterface.java
Posted by Peter Donald <do...@apache.org>.
On Wed, 29 Aug 2001 22:46, Berin Loritsch wrote:
> Peter Donald wrote:
> > +1 to idea of UserManagement Block
>
> Is there any way the UserManagement Block can be authentication method
> agnostic?
Yes and no. In JAAS users are *Subjects* and consist of a number of
Principles. The Principle may represent the Subject in different systems or
via different access methods. For instance you may have a different Principle
for Unix user login, and a different principle for Kerberos (sp?) login, and
a different for PKI, different for biometric etc.
The problem is that most systems still don't distinguish between Subject and
Principle. So in a unix or NT setting the "user" is represented by Principle
and not by Subject. This will slowly change in time - especially with
external groups (MS/other) managing identity servers and authentication
servers.
> In other words, the same general information needs to be managed, but
> the method of collecting it from the client is different.
>
> With PKI (Public Key Infrastructure), the Certificate is part of the
> Handshake, and can be obtained from the SSL connection. Everyone is
> already familiar with username/password.
In this case JAAS's LoginCallback (or whatever it is called) works. But IIRC
this requires that users be represented by "Subject"s.
--
Cheers,
Pete
*-----------------------------------------------------*
| For those who refuse to understand, no explanation |
| will ever suffice. For those who refuse to believe, |
| no evidence will ever suffice. |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: cvs commit:
jakarta-avalon-cornerstone/apps/ftpserver/src/java/org/apache/avalon/ftpserver/interfaces
UserManagerInterface.java
Posted by Berin Loritsch <bl...@apache.org>.
Peter Donald wrote:
>
> +1 to idea of UserManagement Block
Is there any way the UserManagement Block can be authentication method
agnostic?
In other words, the same general information needs to be managed, but
the method of collecting it from the client is different.
With PKI (Public Key Infrastructure), the Certificate is part of the
Handshake, and can be obtained from the SSL connection. Everyone is
already familiar with username/password.
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org