Unit test helpers for CanCan

Guard your links with permissions

Allows user to access read-only list of roles and abilities in controller and vie

Implements CanCanCan's rule-based record fetching using neo4j gem.

Heimdallr aims to provide an easy to configure and efficient object- and field-level access control solution, reusing proven patterns from gems like CanCan and allowing one to manage permissions in a very fine-grained manner.

Add namespace for cancan authorization library

Scaffold controller template expoiting i18n and aware of cancan and WiceGrid

DRY authorization with CanCanCan.

Integration layer between Protector and CanCan

ryanb's nifty-generators + i18n, blueprint, formtastic, declarative_authorization and cancan.

Authorizer is a gem for Ruby (in conjunction with Rails 2.3) that does authorization for you on a per-object basis. What makes this gem different from e.g. declarative_authorization and cancan is they define one role for the entire application. With Authorizer, you define roles for different users on every Rails object. Let's use a Dropbox analogy. With Dropbox, you can choose which folder you want to share. For instance: Al has a home folder with these subfolders in it: - Music (shared with Bob) - Pictures (shared with Casper and Bob) - News (shared with no-one) This causes Al to have all 3 folders in his Dropbox. Bob has 2 and Casper has only 1 folder called Pictures. In other words, a user has access to a subset of the entire collection of folders. Bob has access to 2 of Al's folders, namely Music and Pictures. But he doesn't even see the News folder, nor can he download files from it. Bob's access to the two folders is both read and write, so let's call that role "admin". Al is the owner of all 3 folders and has a role called "owner". This leads to the following Roles table: folder_name user_name role Music Al owner Bob admin Pictures Al owner Bob admin Casper admin News Al owner Now if we would allow Bob to also access the News folder but only read from it, we could add the role called "reader" to the table: folder_name user_name role News Bob reader This is exactly what Authorizer does for your Rails application.

Generates initial code for a devise install. Gives the options for oauth, using cancan, and creating a user tool to manage the users.

Extention of the haml generator that generates templates with the use of i18n, cancan and WiceGrid, adds classes to buttons and uses :title helper

Zero-configuration GraphQL + Relay support for Rails. Adds a route to process GraphQL operations and provides a visual editor (GraphiQL) during development. Allows you to specify GraphQL queries and mutations as though they were controller actions. Automatically maps Mongoid models to GraphQL types. Seamlessly integrates with CanCan.

This is a basic Rails engine utilizing Authlogic, CanCan and Easy Roles to create a starting point for simple Rails-based applications that need authentication and authorization.

Split up your CanCan Ability by allowing you to easily create abilities in separate classes which you reference in your main ability model. This is mainly useful if you want to break down your abilities into smaller classes for organizational purposes.'

CanCan[Can] just can't satisfy me

Permitters are an object-oriented way of defining what request parameters are permitted. using Strong Parameters. It is to Strong Parameters what ActiveModel::Serializers are to as_json/to_json, but supports CanCan and similar authorization frameworks.

Exposes CanCan's current_ability object as json through a rails engine controller

Heimdallr-Resource provides CanCan-like interface for Heimdallr-secured objects.