Skip to content
This repository has been archived by the owner on Jul 8, 2020. It is now read-only.

valet-io/bookshelf-authorization

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

92 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Bookshelf Authorization Build Status NPM version

Bookshelf Authorization is an authorization library made for Bookshelf with an easy-to-read rule syntax and powerful promise-based authorization test.

What is Authorization?

Authorization is the process of determining whether a particular entity should be allowed to access a piece of data. Authentication is the process of verifying an accessor's identity (e.g. matching a username and password to a user model).

Getting Started

First load the plugin:

var Bookshelf = require('bookshelf');
var bookshelfAuthorization = require('bookshelf-authorization');
var bookshelf = Bookshelf.initialize({
  // config
});

bookshelf.plugin(bookshelfAuthorization);

The plugin also support the use of a custom base model. It will check the options (2nd) argument passed to the plugin for a base property. The base option is expected to have an Model property that holds the base model.

var base = {
  Model: Bookshelf.Model.extend()
};
bookshelf.plugin(bookshelfAuthorization, {
  base: base
});

base will now have an updated Model in addtion to User.

Models and Users

Bookshelf Authorization appends an authorize method to models for creating authorization rules. A User inherits from Model and also add the can method for determining permissions. You'll use Model for all of your data and User for anything that needs to be assigned permissions (users, administrators, apps, etc.)

You'll need to use Model.extend otherwise the special authorize and can properties won't be assigned. That means no class MyModel extends Model in CoffeeScript.

Model.authorize

Calling Model.authorize starts an authorization rule chain. Rules chains have two methods:

a(User)

Accepts a user constructor to scope the rule to a particular user type. Also aliased as an.


to(method)

Accepts a method name (e.g. read or write) or array of method names to scope the rule. to can also be chained with the pre-defined read and write methods. The following are equivalent:

Patient.authorize.a(Doctor).to('write').always();
Patient.authorize.a(Doctor).to.write.always();

Rule chains can be closed with three methods:

always()

When the rule is matched, it will allow access.


never()

When the rule is matched, it will prevent access.


when(fn)

When the rule is matched, the supplied fn will be called with a this value of model and an argument of user. The function is wrapped in a promise and the rule outcome depends on its return value.

Access is denied if it:

  • returns a rejected promise
  • throws an exception
  • returns a falsy value (undefined, NaN, null, '', false)
  • returns an empty array ([])

Access is allowed if it:

  • returns a truthy value

Example:

Patient.authorize.a(Doctor).to.write.when(function (doctor) {
  return this.doctor_id === doctor.id;
});

In this snippet, this is the patient being accessed and doctor is the user acessing the data.


About

An authorization library for use with Bookshelf.js

Resources

License

Stars

Watchers

Forks

Packages

No packages published