vivalaz / laravel-route-restrict
Managing project routes via roles and permissions which are assigned to users.
Requires (Dev)
- orchestra/testbench: ^3.5
- phpunit/phpunit: ^7.0
This package is not auto-updated.
Last update: 2024-11-04 13:31:35 UTC
README
Associate project routes with user permissions and roles
This package allows you to extend default spatie/laravel-permission behavoir and manage project routes via roles and permissions which are assigned to users.
Laravel Installation
You can install the package via composer:
composer require vivalaz/laravel-route-restrict
The service provider will automatically get registered. Or you may manually add the service provider in your config/app.php
file:
'providers' => [
// ...
Vivalaz\LaravelRouteRestrict\LaravelRouteRestrictServiceProvider::class
//..
]
Next you should publish the migration with:
php artisan vendor:publish --provider="Vivalaz\LaravelRouteRestrict\LaravelRouteRestrictServiceProvider" --tag="migrations"
After the migration has been published you can create the role- and permission-tables for routes by running the migrations:
php artisan migrate
You can publish the config file with:
php artisan vendor:publish --provider="Vivalaz\LaravelRouteRestrict\LaravelRouteRestrictServiceProvider" --tag="config"
When published, the config/laravel-route-restrict.php
config file initially contains:
return [
'models' => [
'route' => Vivalaz\LaravelRouteRestrict\Models\Route::class
],
'table_names' => [
'routes' => 'routes',
'route_for_roles' => 'route_for_roles',
'route_for_permissions' => 'route_for_permissions'
]
];
Basic usage
Firstly, add the Vivalaz\LaravelRouteRestrict\Traits\HasRouteAccess
trait to your User
model:
class User extends Authenticatable
{
// ...
use HasRouteAccess;
//...
}
This package allows for routes to be associated with user permissions and roles. (More about Roles and Permissions).
For add roles or permissions that can be accessed by user you need to create new Route
in database. Then you can sync roles or permissions:
// sync roles to route
Route::create(['route' => 'api/route', 'method' => 'GET'])->syncRoles([1]);
// sync permissions to route
Route::create(['route' => 'api/permissions_route', 'method' => 'GET'])->syncPermissions([1,2,3]);
WARNING: If route not spicified in database, then it can be accessed by any user with any role or permission.
Using a middleware
This package comes with RouteHasRolesMiddleware
, RouteHasPermissionsMiddleware
and RouteHasRolesOrPermissionsMiddleware
middleware. You can add them inside your app/Http/Kernel.php
file.
protected $routeMiddleware = [
// ...
'route_has_roles' => RouteHasRolesMiddleware::class,
'route_has_permissions' => RouteHasPermissionsMiddleware::class,
'route_has_roles_or_permissions' => RouteHasRolesOrPermissionsMiddleware::class
// ...
];
RouteHasRolesMiddleware::class
- check if user has roles that route requires. If user doesn't have any role, which are allowed for route it throws 403 Forbidden.RouteHasPermissionsMiddleware::class
- check if user has permissions that route requires. If user doesn't have any permission, which are allowed for route it throws 403 Forbidden.RouteHasRolesOrPermissionsMiddleware::class
- check if user has roles or permissions that route requires. If user doesn't have any role or permission, which are allowed for route it throws 403 Forbidden.
Then you can protect your routes using this middleware in web.php
or api.php
.
Route::group(['middleware' => ['route_has_roles_or_permissions']], function() {
//
});
Alternatively, you can add middleware to each route individually.
Route::get('/home', 'HomeController@index')->middleware('route_has_roles_or_permissions');
Or you can protect your controllers similarly, by setting desired middleware in the constructor:
public function __construct()
{
$this->middleware(['route_has_roles_or_permissions']);
}
Testing
composer test
License
The MIT License (MIT).
Copyright 2019 Grinevich Vitaly (vitaliy.grinevich1@gmail.com)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.