Restrictable
Manage authorization restrictions on Ruby on Rails with Devise. Ideal for controlling actions of 2 or 3 types of users.
Restrict user roles from doing specific actions on the controller with two simple controller helpers:
only_allow :cutom_user_role, to: :some_action_in_the_controller
prevent :another_user_role, to: :some_other_action
Installation
Add this line to your application's Gemfile:
gem 'restrictable'
And then execute:
$ bundle
Usage
After adding a User
model with Devise, run the following migration:
$ rails generate migration AddRoleToUsers role:integer
Your migration and model should look like this:
class AddRoleToUsers < ActiveRecord::Migration[5.1]
def change
add_column :users, :role, :integer, default: 0
end
end
class User < ApplicationRecord
devise :database_authenticatable, :recoverable,
:rememberable, :trackable, :validatable,
enum role: [:guest, :content_creator, :admin]
end
And now you can take advantage of the simple controller methods:
class PostsController < ApplicationController
only_allow :admin, to: :destroy
prevent :guest, to: [:create, :update]
def create
end
def update
end
def destroy
end
end
Advanced Usage
Additionally you can match your implementation with Restrictable
simply overriding controller methods. You can do this on the ApplicationController
level or in your Controller.
Example of use:
class ApplicationController < ActionController::Base
protect_from_forgery with: :exception
before_action :authenticate_user!
# `on_forbidden_action` is called when a user role doesn't have
# permission to access the controller method.
def on_forbidden_action
head :forbidden
end
# `should_prevent?(role)` is used to check when a role should be
# prevented.
# Called by the `prevent` helper and should return a boolean value.
def should_prevent?(role)
current_user.role == role
end
# `should_only_allow?(role)` is used to check when a role should be
# allowed.
# Called by the `only_allow` helper and should return a boolean value.
def should_only_allow?(role)
current_user.role != role
end
end
For example, if we want to implement Restrictable
on an application that already have implemented users roles with the model Seller
with devise and the attribute responsability
. Our controller will be something like this:
class SellersController < ApplicationController
only_allow :national_seller, to: :delete
prevent :local_seller, to: :new, :update
def should_prevent?(role)
@seller.responsability == role
end
def should_only_allow?(role)
@seller.responsability != role
end
# ...
end
Development
After checking out the repo, run bin/setup
to install dependencies. Then, run rake test
to run the tests. You can also run bin/console
for an interactive prompt that will allow you to experiment.
To install this gem onto your local machine, run bundle exec rake install
. To release a new version, update the version number in version.rb
, and then run bundle exec rake release
, which will create a git tag for the version, push git commits and tags, and push the .gem
file to rubygems.org.
Roadmap
- Controller helpers
- Controller override methods
- View helpers
- Review flexibility on implementation
Contributing
Bug reports and pull requests are welcome on GitHub at https://github.com/rejonpardenilla/restrictable. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.
License
The gem is available as open source under the terms of the MIT License.
Code of Conduct
Everyone interacting in the Restrictable project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.