GroupUserFolder

This ZopeProduct, also known as GRUF, is a convenient tool to manage groups of users within Zope. It works as a frontend between a Zope application relying on a UserFolder? and a set of two regular UserFolders? : one will store the users and the other one will store the groups. It's used in eg Plone. GRUF has been designed by the Ingeniweb team and is GPL for versions < 2.0, ZPL licence otherwise.

"It has a whole bunch of cool features, especially :

• It doesn't patch anything in Zope ;
• It integrates smoothly without the need of any additional form (some are provided but it's only for convenience) ;
• It doesn't store users by itself but delegates that job to another User Folder. So, it works with virtually ANY Zope UserFolder? in there ! (especially standard acl_users but also LDAPUserFolder, SimpleUserFolder, ...) ;
• It supports groups nesting (ie. groups can belong to other groups and inherit their roles
• It allows groups and users to be stored in a separated backend (eg. groups in ZODB and users in LDAP, ...);
• It supports (since 2.0 version) multiple user sources, ie. you can have a bunch of users in LDAP plus some users in a standard User Folder, and they all will be integrated to GRUF;
• It provides clean management screens (including user and groups editing interfaces) ;
• It provides security auditing tools ;
• It's compatible with regular Zope UserFolder? API ;
• Groups are seen as regular Zope users in applications that doesn't include groups support. Thus, you don't have to rewrite anything to gain benefit from GRUF's groups !

http://ingeniweb.sourceforge.net/Products/GroupUserFolder/

home

comments:

Workflow and GRUF groups -- Thu, 29 Sep 2005 20:33:03 -0700 reply
It's wonderful that users in a GRUF folder can be instances CMFMember subclasses. That lets us use workflow to manage our user signup and user classes. We'd love to be able to do the same thing with groups. Is it possible for the acl_user/Groups/acl_user folder to also contain instances of (a different) CMFMember subclass, so that we can use workflow to manage permissions at various stages of signup and authentication?