[Adminpages-development] ACLs, permissions

[Martin Scheffler]

Hi all,

I took a look at various methods for authentication and ownership handling.

Could you tell me what your ideas for authentication are?
I would go like this:
Three roles: admin, designer, editor
Editor can only edit content and pages
Designer can also edit templates
Admin can also edit element types and users

What kind of permission system do we need for pages and content? Do we need
any at all?
In all my previous projects I never had any use for fine-grained access
control, every user could edit every page. What do you think?

This is the stuff I found:

UserStamp plugin
http://www.delynnberry.com/pages/userstamp/
The Userstamp Plugin extends
*ActiveRecord::Base<http://api.rubyonrails.com/classes/ActiveRecord/Base.html>
* to add automatic updating of *created_by* and *updated_by* attributes of
your models in much the same way that the
*ActiveRecord::Timestamp<http://api.rubyonrails.com/classes/ActiveRecord/Timestamp.html>
* module updates *created_(at/on)* and *updated_(at/on)* attributes.
Could be useful, have to take a closer look

LoginEngine+UserEngine:
simple, wide-spread usage, tested, takes long to install?

ActiveRBAC
https://activerbac.turingstudio.com
Authentication with more fine-grained role handling, role inheritance model,
groups. Seems to be pretty new. I got it to work without problems.

Mac Engine
http://www.ruby-forum.com/topic/61145#new
to provide finer grained control over ActiveRecord results than can be
achieved by using user_engine.  The intention is to provide filtering of
results and assigning permissions to users/groups over what they can
access.

Didn't really take a look at it, but is described as alpha software

Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/adminpages-development/attachments/20060417/c098da53/attachment.htm