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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
