Forum: Ruby on Rails [ANN] acl_system plugin first look

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
132a94ca65959bda6c74fae54bff2425?d=identicon&s=25 Ezra Zygmuntowicz (Guest)
on 2006-02-21 17:40
(Received via mailing list)
Friends-

	Here is another plugin hot off the presses of the three day
weekend ;) Its a role based authorization system. I have been talking
with Bill Katz about this system so it ties in with his recent
announcement as well. Its just my implementation.

	Its an acl/role type system that can sit on top of the
acts_as_authenticated login system or any login system that
implements a few requirements. You just need to make a roles table in
your db that habtm your User or account model. And you need to have a
controller method 'current_user' that returns the currently logged in
user. The acts_as_authenticated plugin already implements this and
this is what this implementation is built on top of, but it can be
used with any user authentication system that has the two features
mentioned above.

	Lets see the candy here fist. This is what it looks like to use this
to protect your controller actions using roles and & | ! to define
complex permissions.

class PostController < ApplicationController

   before_filter :login_required, :except => [:list, :index]

   access_control [:new, :create] => '(admin | user | moderator) & !
blacklist',
                               [:update, :delete] => '(admin |
moderator) & !blacklist',
                               :approve => 'admin & (!moderator | !
blacklist)' )

# rest of controller actions
end


	And then we have a controller/view helper that can be used to build
conditional menu's and such:

<% if permit?("(admin | moderator) & !blacklist", current_user) %>
   <%= link_to "Admin & Moderator only link", :action =>'foo' %>
<% end %>


	In the permissions logic strings you can use as many nested parens
and logic as you want to define what roles have permissions to access
which action. The plugin contains a small recursive descent parser to
parse the permissions logic strings. If you want application wide
protection for certain actions then you can put this in the
application.rb. The one thing to remember is to put the
access_control macro after the login_required before filter. This
plugin is for authorization and assumes that the user is already
logged in.

	Here is a link to the announcement on my blog where I go into more
detail about how to use this in your applications:

http://brainspl.at/articles/2006/02/20/new-plugin-acl_system

	The main goal of this implementation is to be lightweight as as non
imposing as possible. It does what it does and gets out of your way.
Right now it only works for protecting your controller actions. I am
working on the next version that has a similar protection scheme for
protecting specific model records with similar permissions
flexibility. I will release this part very soon.

	I appreciate any feedback that anyone has about this system. It
works well for me in the app that I built it for and I am eager to
get more feedback to further improve things. You can get it from svn
here:

http://opensvn.csie.org/ezra/rails/plugins/dev/acl_system/

OR

script/plugin install http://opensvn.csie.org/ezra/rails/plugins/dev/
acl_system/


Cheers-

-Ezra Zygmuntowicz
Yakima Herald-Republic
WebMaster
http://yakimaherald.com
509-577-7732
ezra@yakima-herald.com
This topic is locked and can not be replied to.