Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/onury/accesscontrol
Role and Attribute based Access Control for Node.js
https://github.com/onury/accesscontrol
abac access-control acl attributes authorization nodejs permissions rbac roles security
Last synced: about 2 months ago
JSON representation
Role and Attribute based Access Control for Node.js
- Host: GitHub
- URL: https://github.com/onury/accesscontrol
- Owner: onury
- License: mit
- Created: 2016-09-13T16:56:53.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2024-06-21T03:26:21.000Z (3 months ago)
- Last Synced: 2024-07-24T15:03:15.567Z (about 2 months ago)
- Topics: abac, access-control, acl, attributes, authorization, nodejs, permissions, rbac, roles, security
- Language: TypeScript
- Homepage: https://onury.io/accesscontrol
- Size: 425 KB
- Stars: 2,163
- Watchers: 48
- Forks: 177
- Open Issues: 46
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
- awesome-list - accesscontrol
- awesome-auth - accesscontrol - Role and attribute-based access control for Node.js. (Authorization / <a name="authZ-node"></a>Node.js)
README
© 2019, Onur Yıldırım (@onury).
### Role and Attribute based Access Control for Node.js
Many [RBAC][rbac] (Role-Based Access Control) implementations differ, but the basics is widely adopted since it simulates real life role (job) assignments. But while data is getting more and more complex; you need to define policies on resources, subjects or even environments. This is called [ABAC][abac] (Attribute-Based Access Control).
With the idea of merging the best features of the two (see this [NIST paper][nist-paper]); this library implements RBAC basics and also focuses on *resource* and *action* attributes.
Install
Examples
Roles
Actions
Resources
Permissions
More
F.A.Q.
API Reference
## Core Features
- Chainable, friendly API.
e.g. `ac.can(role).create(resource)`
- Role hierarchical **inheritance**.
- Define grants **at once** (e.g. from database result) or **one by one**.
- Grant/deny permissions by attributes defined by **glob notation** (with nested object support).
- Ability to **filter** data (model) instance by allowed attributes.
- Ability to control access on **own** or **any** resources.
- Ability to **lock** underlying grants model.
- No **silent** errors.
- **Fast**. (Grants are stored in memory, no database queries.)
- Brutally **tested**.
- TypeScript support.
_In order to build on more solid foundations, this library (v1.5.0+) is completely re-written in TypeScript._
## Installation
with [**npm**](https://www.npmjs.com/package/accesscontrol): `npm i accesscontrol --save`
with [**yarn**](https://yarn.pm/accesscontrol): `yarn add accesscontrol`
## Guide
```js
const AccessControl = require('accesscontrol');
// or:
// import { AccessControl } from 'accesscontrol';
```
### Basic Example
Define roles and grants one by one.
```js
const ac = new AccessControl();
ac.grant('user') // define new or modify existing role. also takes an array.
.createOwn('video') // equivalent to .createOwn('video', ['*'])
.deleteOwn('video')
.readAny('video')
.grant('admin') // switch to another role without breaking the chain
.extend('user') // inherit role capabilities. also takes an array
.updateAny('video', ['title']) // explicitly defined attributes
.deleteAny('video');
const permission = ac.can('user').createOwn('video');
console.log(permission.granted); // —> true
console.log(permission.attributes); // —> ['*'] (all attributes)
permission = ac.can('admin').updateAny('video');
console.log(permission.granted); // —> true
console.log(permission.attributes); // —> ['title']
```
### Express.js Example
Check role permissions for the requested resource and action, if granted; respond with filtered attributes.
```js
const ac = new AccessControl(grants);
// ...
router.get('/videos/:title', function (req, res, next) {
const permission = ac.can(req.user.role).readAny('video');
if (permission.granted) {
Video.find(req.params.title, function (err, data) {
if (err || !data) return res.status(404).end();
// filter data by permission attributes and send.
res.json(permission.filter(data));
});
} else {
// resource is forbidden for this user/role
res.status(403).end();
}
});
```
## Roles
You can create/define roles simply by calling `.grant()` or `.deny()` methods on an `AccessControl` instance.
- Roles can extend other roles.
```js
// user role inherits viewer role permissions
ac.grant('user').extend('viewer');
// admin role inherits both user and editor role permissions
ac.grant('admin').extend(['user', 'editor']);
// both admin and superadmin roles inherit moderator permissions
ac.grant(['admin', 'superadmin']).extend('moderator');
```
- Inheritance is done by reference, so you can grant resource permissions before or after extending a role.
```js
// case #1
ac.grant('admin').extend('user') // assuming user role already exists
.grant('user').createOwn('video');
// case #2
ac.grant('user').createOwn('video')
.grant('admin').extend('user');
// below results the same for both cases
const permission = ac.can('admin').createOwn('video');
console.log(permission.granted); // true
```
Notes on inheritance:
- A role cannot extend itself.
- Cross-inheritance is not allowed.
e.g. `ac.grant('user').extend('admin').grant('admin').extend('user')` will throw.
- A role cannot (pre)extend a non-existing role. In other words, you should first create the base role. e.g. `ac.grant('baseRole').grant('role').extend('baseRole')`
## Actions and Action-Attributes
[CRUD][crud] operations are the actions you can perform on a resource. There are two action-attributes which define the **possession** of the resource: *own* and *any*.
For example, an `admin` role can `create`, `read`, `update` or `delete` (CRUD) **any** `account` resource. But a `user` role might only `read` or `update` its **own** `account` resource.
Action
Possession
Create
Read
Update
Delete
Own
The C|R|U|D action is (or not) to be performed on own resource(s) of the current subject.
Any
The C|R|U|D action is (or not) to be performed on any resource(s); including own.
```js
ac.grant('role').readOwn('resource');
ac.deny('role').deleteAny('resource');
```
_Note that **own** requires you to also check for the actual possession. See [this](https://github.com/onury/accesscontrol/issues/14#issuecomment-328316670) for more._
## Resources and Resource-Attributes
Multiple roles can have access to a specific resource. But depending on the context, you may need to limit the contents of the resource for specific roles.
This is possible by resource attributes. You can use Glob notation to define allowed or denied attributes.
For example, we have a `video` resource that has the following attributes: `id`, `title` and `runtime`.
All attributes of *any* `video` resource can be read by an `admin` role:
```js
ac.grant('admin').readAny('video', ['*']);
// equivalent to:
// ac.grant('admin').readAny('video');
```
But the `id` attribute should not be read by a `user` role.
```js
ac.grant('user').readOwn('video', ['*', '!id']);
// equivalent to:
// ac.grant('user').readOwn('video', ['title', 'runtime']);
```
You can also use nested objects (attributes).
```js
ac.grant('user').readOwn('account', ['*', '!record.id']);
```
## Checking Permissions and Filtering Attributes
You can call `.can().()` on an `AccessControl` instance to check for granted permissions for a specific resource and action.
```js
const permission = ac.can('user').readOwn('account');
permission.granted; // true
permission.attributes; // ['*', '!record.id']
permission.filter(data); // filtered data (without record.id)
```
See [express.js example](#expressjs-example).
## Defining All Grants at Once
You can pass the grants directly to the `AccessControl` constructor.
It accepts either an `Object`:
```js
// This is actually how the grants are maintained internally.
let grantsObject = {
admin: {
video: {
'create:any': ['*', '!views'],
'read:any': ['*'],
'update:any': ['*', '!views'],
'delete:any': ['*']
}
},
user: {
video: {
'create:own': ['*', '!rating', '!views'],
'read:own': ['*'],
'update:own': ['*', '!rating', '!views'],
'delete:own': ['*']
}
}
};
const ac = new AccessControl(grantsObject);
```
... or an `Array` (useful when fetched from a database):
```js
// grant list fetched from DB (to be converted to a valid grants object, internally)
let grantList = [
{ role: 'admin', resource: 'video', action: 'create:any', attributes: '*, !views' },
{ role: 'admin', resource: 'video', action: 'read:any', attributes: '*' },
{ role: 'admin', resource: 'video', action: 'update:any', attributes: '*, !views' },
{ role: 'admin', resource: 'video', action: 'delete:any', attributes: '*' },
{ role: 'user', resource: 'video', action: 'create:own', attributes: '*, !rating, !views' },
{ role: 'user', resource: 'video', action: 'read:any', attributes: '*' },
{ role: 'user', resource: 'video', action: 'update:own', attributes: '*, !rating, !views' },
{ role: 'user', resource: 'video', action: 'delete:own', attributes: '*' }
];
const ac = new AccessControl(grantList);
```
You can set grants any time...
```js
const ac = new AccessControl();
ac.setGrants(grantsObject);
console.log(ac.getGrants());
```
...unless you lock it:
```js
ac.lock().setGrants({}); // throws after locked
```
## Documentation
You can read the full [**API reference**][docs] with lots of details, features and examples.
And more at the [F.A.Q. section][faq].
## Change-Log
See [CHANGELOG][changelog].
## Contributing
Clone original project:
```sh
git clone https://github.com/onury/accesscontrol.git
```
Install dependencies:
```sh
npm install
```
Add tests to relevant file under [/test](test/) directory and run:
```sh
npm run build && npm run cover
```
Use included `tslint.json` and `editorconfig` for style and linting.
Travis build should pass, coverage should not degrade.
## License
[**MIT**][license].
[docs]:http://onury.io/accesscontrol/?api=ac
[faq]:http://onury.io/accesscontrol/?content=faq
[rbac]:https://en.wikipedia.org/wiki/Role-based_access_control
[abac]:https://en.wikipedia.org/wiki/Attribute-Based_Access_Control
[crud]:https://en.wikipedia.org/wiki/Create,_read,_update_and_delete
[nist-paper]:http://csrc.nist.gov/groups/SNS/rbac/documents/kuhn-coyne-weil-10.pdf
[changelog]:https://github.com/onury/accesscontrol/blob/master/CHANGELOG.md
[license]:https://github.com/onury/accesscontrol/blob/master/LICENSE