Package Data | |
---|---|
Maintainer Username: | Jotape |
Maintainer Contact: | joaopinheiro.ti@gmail.com (João Paulo Pinheiro) |
Package Create Date: | 2017-04-17 |
Package Last Update: | 2017-04-17 |
Language: | PHP |
License: | MIT |
Last Refreshed: | 2024-11-26 15:20:40 |
Package Statistics | |
---|---|
Total Downloads: | 203 |
Monthly Downloads: | 0 |
Daily Downloads: | 0 |
Total Stars: | 0 |
Total Watchers: | 3 |
Total Forks: | 0 |
Total Open Issues: | 0 |
A Powerful package for handling roles and permissions in Laravel 5.4 This package is an adaptation of romanbican/roles and ultraware/roles.
This package is very easy to set up. There are only couple of steps.
Pull this package in through Composer
composer require jotapepinheiro/laravel-roles
Add the package to your application service providers in config/app.php
file.
'providers' => [
...
/**
* Third Party Service Providers...
*/
jotapepinheiro\LaravelRoles\RolesServiceProvider::class,
],
Publish the package config file and migrations to your application. Run these commands inside your terminal.
php artisan vendor:publish --provider="jotapepinheiro\LaravelRoles\RolesServiceProvider" --tag=config
php artisan vendor:publish --provider="jotapepinheiro\LaravelRoles\RolesServiceProvider" --tag=migrations
php artisan vendor:publish --provider="jotapepinheiro\LaravelRoles\RolesServiceProvider" --tag=seeds
Include HasRoleAndPermission
trait and also implement HasRoleAndPermission
contract inside your User
model. See example below.
Include use jotapepinheiro\LararvelRoles\Traits\HasRoleAndPermission;
in the top of your User
model below the namespace and implement the HasRoleAndPermission
trait. See example below.
Example User
model Trait And Contract:
<?php
namespace App;
use Illuminate\Database\Eloquent\Model;
use Illuminate\Notifications\Notifiable;
use jotapepinheiro\LaravelRoles\Traits\HasRoleAndPermission;
use Illuminate\Foundation\Auth\User as Authenticatable;
class User extends Authenticatable
{
use Notifiable;
use HasRoleAndPermission;
// rest of your model ...
}
This uses the default users table which is in Laravel. You should already have the migration file for the users table available and migrated.
Setup the needed tables:
php artisan migrate
Update database\seeds\DatabaseSeeder.php
to include the seeds. See example below.
<?php
use Illuminate\Database\Seeder;
use Illuminate\Database\Eloquent\Model;
class DatabaseSeeder extends Seeder
{
/**
* Run the database seeds.
*
* @return void
*/
public function run()
{
Model::unguard();
$this->call(PermissionsTableSeeder::class);
$this->call(RolesTableSeeder::class);
$this->call(ConnectRelationshipsSeeder::class);
//$this->call(UsersTableSeeder::class);
Model::reguard();
}
}
php artisan db:seed
If you migrate from bican/roles to jotapepinheiro/LaravelRoles you will need to update a few things.
can
, canOne
and canAll
to hasPermission
, hasOnePermission
, hasAllPermissions
.is
, isOne
and isAll
to hasRole
, hasOneRole
, hasAllRoles
.use jotapepinheiro\LaravelRoles\Models\Role;
$adminRole = Role::create([
'name' => 'Admin',
'slug' => 'admin',
'description' => '',
'level' => 5,
]);
$moderatorRole = Role::create([
'name' => 'Forum Moderator',
'slug' => 'forum.moderator',
]);
Because of
Slugable
trait, if you make a mistake and for example leave a space in slug parameter, it'll be replaced with a dot automatically, because ofstr_slug
function.
It's really simple. You fetch a user from database and call attachRole
method. There is BelongsToMany
relationship between User
and Role
model.
use App\User;
$user = User::find($id);
$user->attachRole($adminRole); // you can pass whole object, or just an id
$user->detachRole($adminRole); // in case you want to detach role
$user->detachAllRoles(); // in case you want to detach all roles
$user->syncRoles($roles); // you can pass Eloquent collection, or just an array of ids
You can assign the user a role upon the users registration by updating the file app\Http\Controllers\Auth\RegisterController.php
.
You can assign a role to a user upon registration by including the needed models and modifying the create()
method to attach a user role. See example below:
app\Http\Controllers\Auth\RegisterController.php
:<?php
namespace App\Http\Controllers\Auth;
use App\User;
use App\Http\Controllers\Controller;
use Illuminate\Support\Facades\Validator;
use jotapepinheiro\LaravelRoles\Models\Role;
use jotapepinheiro\LaravelRoles\Models\Permission;
use Illuminate\Foundation\Auth\RegistersUsers;
create()
method of app\Http\Controllers\Auth\RegisterController.php
: protected function create(array $data)
{
$user = User::create([
'name' => $data['name'],
'email' => $data['email'],
'password' => bcrypt($data['password']),
]);
$role = Role::where('name', '=', 'User')->first(); //choose the default role upon user creation.
$user->attachRole($role);
return $user;
}
You can now check if the user has required role.
if ($user->hasRole('admin')) { // you can pass an id or slug
//
}
You can also do this:
if ($user->isAdmin()) {
//
}
And of course, there is a way to check for multiple roles:
if ($user->hasRole(['admin', 'moderator'])) {
/*
| Or alternatively:
| $user->hasRole('admin, moderator'), $user->hasRole('admin|moderator'),
| $user->hasOneRole('admin, moderator'), $user->hasOneRole(['admin', 'moderator']), $user->hasOneRole('admin|moderator')
*/
// The user has at least one of the roles
}
if ($user->hasRole(['admin', 'moderator'], true)) {
/*
| Or alternatively:
| $user->hasRole('admin, moderator', true), $user->hasRole('admin|moderator', true),
| $user->hasAllRoles('admin, moderator'), $user->hasAllRoles(['admin', 'moderator']), $user->hasAllRoles('admin|moderator')
*/
// The user has all roles
}
When you are creating roles, there is optional parameter level
. It is set to 1
by default, but you can overwrite it and then you can do something like this:
if ($user->level() > 4) {
//
}
If user has multiple roles, method
level
returns the highest one.
Level
has also big effect on inheriting permissions. About it later.
It's very simple thanks to Permission
model.
use jotapepinheiro\LaravelRoles\Models\Permission;
$createUsersPermission = Permission::create([
'name' => 'Create users',
'slug' => 'create.users',
'description' => '', // optional
]);
$deleteUsersPermission = Permission::create([
'name' => 'Delete users',
'slug' => 'delete.users',
]);
You can attach permissions to a role or directly to a specific user (and of course detach them as well).
use App\User;
use jotapepinheiro\LaravelRoles\Models\Role;
$role = Role::find($roleId);
$role->attachPermission($createUsersPermission); // permission attached to a role
$user = User::find($userId);
$user->attachPermission($deleteUsersPermission); // permission attached to a user
$role->detachPermission($createUsersPermission); // in case you want to detach permission
$role->detachAllPermissions(); // in case you want to detach all permissions
$role->syncPermissions($permissions); // you can pass Eloquent collection, or just an array of ids
$user->detachPermission($deleteUsersPermission);
$user->detachAllPermissions();
$user->syncPermissions($permissions); // you can pass Eloquent collection, or just an array of ids
if ($user->hasPermission('create.users') { // you can pass an id or slug
//
}
if ($user->canDeleteUsers()) {
//
}
You can check for multiple permissions the same way as roles. You can make use of additional methods like hasOnePermission
or hasAllPermissions
.
Role with higher level is inheriting permission from roles with lower level.
There is an example of this magic
:
You have three roles: user
, moderator
and admin
. User has a permission to read articles, moderator can manage comments and admin can create articles. User has a level 1, moderator level 2 and admin level 3. It means, moderator and administrator has also permission to read articles, but administrator can manage comments as well.
If you don't want permissions inheriting feature in you application, simply ignore
level
parameter when you're creating roles.
Let's say you have an article and you want to edit it. This article belongs to a user (there is a column user_id
in articles table).
use App\Article;
use jotapepinheiro\LaravelRoles\Models\Permission;
$editArticlesPermission = Permission::create([
'name' => 'Edit articles',
'slug' => 'edit.articles',
'model' => 'App\Article',
]);
$user->attachPermission($editArticlesPermission);
$article = Article::find(1);
if ($user->allowed('edit.articles', $article)) { // $user->allowedEditArticles($article)
//
}
This condition checks if the current user is the owner of article. If not, it will be looking inside user permissions for a row we created before.
if ($user->allowed('edit.articles', $article, false)) { // now owner check is disabled
//
}
There are four Blade extensions. Basically, it is replacement for classic if statements.
@role('admin') // @if(Auth::check() && Auth::user()->hasRole('admin'))
// user has admin role
@endrole
@permission('edit.articles') // @if(Auth::check() && Auth::user()->hasPermission('edit.articles'))
// user has edit articles permissison
@endpermission
@level(2) // @if(Auth::check() && Auth::user()->level() >= 2)
// user has level 2 or higher
@endlevel
@allowed('edit', $article) // @if(Auth::check() && Auth::user()->allowed('edit', $article))
// show edit button
@endallowed
@role('admin|moderator', true) // @if(Auth::check() && Auth::user()->hasRole('admin|moderator', true))
// user has admin and moderator role
@else
// something else
@endrole
This package comes with VerifyRole
, VerifyPermission
and VerifyLevel
middleware. You must add them inside your app/Http/Kernel.php
file.
/**
* The application's route middleware.
*
* @var array
*/
protected $routeMiddleware = [
'auth' => \App\Http\Middleware\Authenticate::class,
'auth.basic' => \Illuminate\Auth\Middleware\AuthenticateWithBasicAuth::class,
'guest' => \App\Http\Middleware\RedirectIfAuthenticated::class,
'role' => \jotapepinheiro\LaravelRoles\Middleware\VerifyRole::class,
'permission' => \jotapepinheiro\LaravelRoles\Middleware\VerifyPermission::class,
'level' => \jotapepinheiro\LaravelRoles\Middleware\VerifyLevel::class,
];
Now you can easily protect your routes.
$router->get('/example', [
'as' => 'example',
'middleware' => 'role:admin',
'uses' => 'ExampleController@index',
]);
$router->post('/example', [
'as' => 'example',
'middleware' => 'permission:edit.articles',
'uses' => 'ExampleController@index',
]);
$router->get('/example', [
'as' => 'example',
'middleware' => 'level:2', // level >= 2
'uses' => 'ExampleController@index',
]);
It throws \jotapepinheiro\LaravelRoles\Exceptions\RoleDeniedException
, \jotapepinheiro\LaravelRoles\Exceptions\PermissionDeniedException
or \jotapepinheiro\LaravelRoles\Exceptions\LevelDeniedException
exceptions if it goes wrong.
You can catch these exceptions inside app/Exceptions/Handler.php
file and do whatever you want.
/**
* Render an exception into an HTTP response.
*
* @param \Illuminate\Http\Request $request
* @param \Exception $e
* @return \Illuminate\Http\Response
*/
public function render($request, Exception $e)
{
if ($e instanceof \jotapepinheiro\LaravelRoles\Exceptions\RoleDeniedException) {
// you can for example flash message, redirect...
return redirect()->back();
}
return parent::render($request, $e);
}
You can change connection for models, slug separator, models path and there is also a handy pretend feature. Have a look at config file for more information.
For more information, please have a look at HasRoleAndPermission contract.
This package is free software distributed under the terms of the MIT license.