Cheers. Thanks to all of you for suggestions and interest. I'm going to spend the next couple of days looking at existing solutions that can be retailored for JAAS compliance and Avalon containment. As soon as I get a better feel for afinal solution I'll post it on an external site for review and comments. Again, thanks for all the help, folks.
On Sun, 2004-06-27 at 13:59, Peter Courcoux wrote: > Paul, sorry I'm a bit late with this reply. > > There is a framework for user/group/role/permission management based on > avalon in jakarta-turbine-fulcrum cvs. It is the security component. > > The best documentation on using it and an example is at :- > > http://zebra.tigris.org in the zebra-antelope web application. > > This uses fulcrum-security to manage users etc. and the example shows > screens manipulating the code. Contact the turbine user list for any help. > > hibernate is used for persistence but the framework can be adapted as > required. > > Regards, > > Peter > > > On Sun, 27 Jun 2004, Paul Cooley wrote: > > > With the exceptions of not being JAAS compliant (or am I missing > > something??) and not being avalon based, yes. RMS or jGuard could > > probably be exposed through avalon components in order to facilitate the > > functionality. > > > > Janus' links do not work, so I'm unsure about this one. I'll be > > exposing the TWiki for the project soon in order to get some feedback. > > > > On Sat, 2004-06-26 at 10:56, Alex Karasulu wrote: > > > Take a look at RMS (Realm Management System) and Janus at the directory > > > project here: > > > > > > http://incubator.apache.org/directory/subprojects/rms > > > > > > or for all projects lookie here: > > > > > > http://incubator.apache.org/directory/subprojects/index.html > > > > > > Does this come close to what you're looking for? > > > > > > Alex > > > > > > On Sat, 2004-06-26 at 11:43, Paul Cooley wrote: > > > > Typically, every application (for use with multiple users) has the need > > > > for handling basic authentication and authorization. In addition, we > > > > also inevitably find ourselves trying to manage user logins, their > > > > passwords, what organization they belong to and etc. > > > > > > > > What I'm proposing is a set of services to enable: > > > > 1. User management-- tasks performed by admin on user behalf or by user > > > > on their own information > > > > Creating users > > > > Updating user information (name, etc) > > > > (Re)setting of passwords > > > > Disabling users > > > > Enabling disabled users > > > > 2. Organization Management-- administrative management of organizations > > > > for system > > > > Orgs are just umbrellas to associate users with > > > > 3. Role Management--administrative tasks for associating groups and > > > > users with security roles > > > > 4. Permission Management-- administrative tasks for managing > > > > permissions > > > > Creating permissions for services (based on JAAS) > > > > Associating Permissions to roles > > > > Removing Permissions > > > > > > > > The idea is to creat reusable Avalon services which can be leveraged by > > > > any Avalon compliant application. Yes, there are tons of web-based > > > > solutions, but I have yet to find anything meant to simply run in the > > > > context of avalon containers. > > > > > > > > And that is pretty much what I'd scoped out thus far. We had a very > > > > similiar model in our avalon container at my last job, and it certainly > > > > facilitated rapid app development. If enough of these types of services > > > > are developed, most apps are able to get up to speed very quickly and > > > > focus on what they are supposed to do rather than spend all their > > > > recreating infrastructure that should already exist. > > > > > > > > On Sat, 2004-06-26 at 10:30, Andreas Oberhack wrote: > > > > > Hey great, Paul, > > > > > > > > > > just in the process of doing the same! Right now I'm more focused on the > > > > > contract, product, service and conditions - but I already have an > > > > > initial "party" model. > > > > > > > > > > Beside that I just started a document about the model architecture. > > > > > > > > > > What is your context of your app? > > > > > > > > > > Andreas > > > > > > > > > > -----Original Message----- > > > > > From: Paul Cooley [mailto:[EMAIL PROTECTED] > > > > > Sent: Samstag, 26. Juni 2004 15:57 > > > > > To: Avalon Developers List > > > > > Subject: User Management Services > > > > > > > > > > Before I go and remake the world, is there a set of components out there > > > > > yet for dealing with users, groups, roles, and etc? > > > > > > > > > > I am in the process of designing such a module of Avalon/Merlin services > > > > > and wanted to make sure I wasn't duplicating someone's work already. > > > > > > > > > > Any thoughts? > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --- > > > > > Incoming mail is certified Virus Free. > > > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > > > Version: 6.0.708 / Virus Database: 464 - Release Date: 18.06.2004 > > > > > > > > > > > > > > > --- > > > > > Outgoing mail is certified Virus Free. > > > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > > > Version: 6.0.708 / Virus Database: 464 - Release Date: 18.06.2004 > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
