To publish the config, run the vendor publish command:
php artisan vendor:publish
This will create a new model config file named config/lauthz-rbac-model.conf and a new lauthz config file named config/lauthz.php.
To migrate the migrations, run the migrate command:
php artisan migrate
This will create a new table named rules
Usage
Quick start
Once installed you can do stuff like this:
use Enforcer;
// adds permissions to a user
Enforcer::addPermissionForUser('eve', 'articles', 'read');
// adds a role for a user.
Enforcer::addRoleForUser('eve', 'writer');
// adds permissions to a role
Enforcer::addPolicy('writer', 'articles','edit');
You can check if a user has a permission like this:
// to check if a user has permission
if (Enforcer::enforce("eve", "articles", "edit")) {
// permit eve to edit articles
} else {
// deny the request, show an error
}
Using Enforcer Api
It provides a very rich api to facilitate various operations on the Policy:
Gets all roles:
Enforcer::getAllRoles(); // ['writer', 'reader']
Gets all the authorization rules in the policy.:
Enforcer::getPolicy();
Gets the roles that a user has.
Enforcer::getRolesForUser('eve'); // ['writer']
Gets the users that has a role.
Enforcer::getUsersForRole('writer'); // ['eve']
Determines whether a user has a role.
Enforcer::hasRoleForUser('eve', 'writer'); // true or false
Adds a role for a user.
Enforcer::addRoleForUser('eve', 'writer');
Adds a permission for a user or role.
// to user
Enforcer::addPermissionForUser('eve', 'articles', 'read');
// to role
Enforcer::addPermissionForUser('writer', 'articles','edit');
Deletes a role for a user.
Enforcer::deleteRoleForUser('eve', 'writer');
Deletes all roles for a user.
Enforcer::deleteRolesForUser('eve');
Deletes a role.
Enforcer::deleteRole('writer');
Deletes a permission.
Enforcer::deletePermission('articles', 'read'); // returns false if the permission does not exist (aka not affected).
Then you can protect your routes using middleware rules:
Route::group(['middleware' => ['enforcer:articles,read']], function () {
// pass
});
HTTP Request Middleware ( RESTful is also supported )
If you need to authorize a Request,you need to define the model configuration first in config/lauthz-rbac-model.conf:
[request_definition]
r = sub, obj, act
[policy_definition]
p = sub, obj, act
[role_definition]
g = _, _
[policy_effect]
e = some(where (p.eft == allow))
[matchers]
m = g(r.sub, p.sub) && keyMatch2(r.obj, p.obj) && regexMatch(r.act, p.act)
Then, using middleware rules:
Route::group(['middleware' => ['http_request']], function () {
Route::resource('photo', 'PhotoController');
});
Using Gates
You can use Laravel Gates to check if a user has a permission, provided that you have set an existing user instance as the currently authenticated user.
$user->can('articles,read');
// For multiple enforcers
$user->can('articles,read', 'second');
// The methods cant, cannot, canAny, etc. also work
If you require custom Laravel Gates, you can disable the automatic registration by setting enabled_register_at_gates to false in the lauthz file. After that, you can use Gates::before or Gates::after in your ServiceProvider to register custom Gates. See Gates for more details.
Multiple enforcers
If you need multiple permission controls in your project, you can configure multiple enforcers.
You can create a policy from a console with artisan commands.
To user:
php artisan policy:add eve,articles,read
To Role:
php artisan policy:add writer,articles,edit
Adds a role for a user:
php artisan role:assign eve writer
# Specify the ptype of the role assignment by using the --ptype option.
php artisan role:assign eve writer --ptype=g2
Using cache
Authorization rules are cached to speed up performance. The default is off.
Sets your own cache configs in Laravel’s config/lauthz.php.
Laravel Authorization
Laravel-authz is an authorization library for the laravel framework.
It’s based on Casbin, an authorization library that supports access control models like ACL, RBAC, ABAC.
All you need to learn to use
Casbin
first.Installation
Require this package in the
composer.json
of your Laravel project. This will download the package.The
Lauthz\LauthzServiceProvider
isauto-discovered
and registered by default, but if you want to register it yourself:Add the ServiceProvider in
config/app.php
The Enforcer facade is also
auto-discovered
, but if you want to add it manually:Add the Facade in
config/app.php
To publish the config, run the vendor publish command:
This will create a new model config file named
config/lauthz-rbac-model.conf
and a new lauthz config file namedconfig/lauthz.php
.To migrate the migrations, run the migrate command:
This will create a new table named
rules
Usage
Quick start
Once installed you can do stuff like this:
You can check if a user has a permission like this:
Using Enforcer Api
It provides a very rich api to facilitate various operations on the Policy:
Gets all roles:
Gets all the authorization rules in the policy.:
Gets the roles that a user has.
Gets the users that has a role.
Determines whether a user has a role.
Adds a role for a user.
Adds a permission for a user or role.
Deletes a role for a user.
Deletes all roles for a user.
Deletes a role.
Deletes a permission.
Deletes a permission for a user or role.
Deletes permissions for a user or role.
Gets permissions for a user or role.
Determines whether a user has a permission.
See Casbin API for more APIs.
Using a middleware
This package comes with
EnforcerMiddleware
,RequestMiddleware
middlewares. You can add them inside yourapp/Http/Kernel.php
file.basic Enforcer Middleware
Then you can protect your routes using middleware rules:
HTTP Request Middleware ( RESTful is also supported )
If you need to authorize a Request,you need to define the model configuration first in
config/lauthz-rbac-model.conf
:Then, using middleware rules:
Using Gates
You can use Laravel Gates to check if a user has a permission, provided that you have set an existing user instance as the currently authenticated user.
If you require custom Laravel Gates, you can disable the automatic registration by setting
enabled_register_at_gates
tofalse
in the lauthz file. After that, you can useGates::before
orGates::after
in your ServiceProvider to register custom Gates. See Gates for more details.Multiple enforcers
If you need multiple permission controls in your project, you can configure multiple enforcers.
In the lauthz file, it should be like this:
Then you can choose which enforcers to use.
Using artisan commands
You can create a policy from a console with artisan commands.
To user:
To Role:
Adds a role for a user:
Using cache
Authorization rules are cached to speed up performance. The default is off.
Sets your own cache configs in Laravel’s
config/lauthz.php
.Thinks
Casbin in Laravel. You can find the full documentation of Casbin on the website.
License
This project is licensed under the Apache 2.0 license.