Arrthorizer

Dynamic and static access control for your Rails (3+) application. Arrthorizer revolves around the concept of static roles (some kind of 'groups' the user can be a member of) and dynamic roles (detecting the relation the user has to the current context, like 'the writer of this blog post').

Arrthorizer is flexible and allows you to inject much of your own application logic into your authorization subsystem. It allows (that is, requires) you to determine which elements of a context are relevant for authorization and accepts your logic for determining whether a given user is part of a certain group.

Arrthorizer is designed for ease of use and configurability. Its Rails version (currently the only version) comes bundled with some useful generators and most of the configuration is done using a DSL in your controllers, along with a plain old YAML file.

• Works with Rails 3.2, 4.0 and 4.1
• Leverages domain logic for authorization without introducing strong coupling
• Easy-to-use generators get you up-and-running in minutes, not hours
• Well-tested
• Generates tests for your roles for your test framework (MiniTest, RSpec and Test::Unit supported)

Add this line to your application's Gemfile:

gem 'arrthorizer'

And then execute:

$ bundle

Or install it yourself as:

$ gem install arrthorizer

After the above installation, run:

$ bin/rails g arrthorizer:install

After using the arrthorizer:install generator, your git diff will tell you everything you need to know. Read the comments to understand what you need to do to make it work.

When new ContextRoles are required later on, Arrthorizer provides a generator for that, too:

$ bin/rails g arrthorizer:context_role {namespace_if_you_need_it/role_name}

This will generate a file containing the scaffold for the ContextRole and a couple of test cases for your test framework.

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request