How to implement a permission management system in Laravel
How to implement a permission management system in Laravel
Introduction:
With the continuous development of web applications, the permission management system has become one of the basic functions of many applications. one. Laravel, as a popular PHP framework, provides a wealth of tools and functions to implement permission management systems. This article will introduce how to implement a simple and powerful permission management system in Laravel and provide specific code examples.
1. Design ideas of permission management system
When designing the permission management system, the following key points need to be considered:
- Definition of roles and permissions: Role refers to The user's function or identity, and permissions refer to the user's ability to access system functions or resources.
- The relationship between users and roles: A user can have multiple roles, and a role can be owned by multiple users.
- The relationship between permissions and roles: A role can have multiple permissions, and one permission can be owned by multiple roles.
- The relationship between routing and permissions: Routing determines the entrance for users to access system functions. Different routes may require different permissions to restrict access.
Based on the above design ideas, we can start to implement the permission management system in Laravel.
2. Database design and migration
In Laravel, we can use database migration to create and modify database tables. The following is a simple database design:
- User table (users): stores basic information of users, such as user name, password, etc.
- Role table (roles): stores basic information of roles, such as role name, description, etc.
- Permissions table: stores basic information about permissions, such as permission names, descriptions, etc.
- Role-permission association table (role_permission): records the corresponding relationship between roles and permissions.
- User-role association table (user_role): records the corresponding relationship between users and roles.
First, create the migration file:
php artisan make:migration create_users_table php artisan make:migration create_roles_table php artisan make:migration create_permissions_table php artisan make:migration create_role_permission_table php artisan make:migration create_user_role_table
Then, write the table structure in the corresponding migration file (the code is omitted), and run the migration command:
php artisan migrate
3. Define model relationships
In Laravel, we can use the Eloquent model to define relationships between database tables. First, we need to define three models: User, Role, and Permission.
User model (User)
namespace App; use IlluminateDatabaseEloquentModel; class User extends Model { // 用户与角色的多对多关系 public function roles() { return $this->belongsToMany('AppRole')->withTimestamps(); } // 判断用户是否拥有某个角色 public function hasRole($role) { if (is_string($role)) { return $this->roles->contains('name', $role); } return !! $role->intersect($this->roles)->count(); } // 判断用户是否拥有某个权限 public function hasPermission($permission) { return $this->hasRole($permission->roles); } }
Copy after loginRole model (Role)
namespace App; use IlluminateDatabaseEloquentModel; class Role extends Model { // 角色与用户的多对多关系 public function users() { return $this->belongsToMany('AppUser')->withTimestamps(); } // 角色与权限的多对多关系 public function permissions() { return $this->belongsToMany('AppPermission')->withTimestamps(); } // 判断角色是否拥有某个权限 public function hasPermission($permission) { if (is_string($permission)) { return $this->permissions->contains('name', $permission); } return !! $permission->intersect($this->permissions)->count(); } }
Copy after loginPermission model (Permission)
namespace App; use IlluminateDatabaseEloquentModel; class Permission extends Model { // 权限与角色的多对多关系 public function roles() { return $this->belongsToMany('AppRole'); } }
Copy after login
4. Middleware and routing settings
In order to implement the permission management system, we can use middleware to intercept and verify user access requests. First, we need to define a permission middleware.
Define permission middleware:
namespace AppHttpMiddleware; use Closure; use IlluminateSupportFacadesAuth; class CheckPermission { public function handle($request, Closure $next, $permission) { $user = Auth::user(); if ($user && $user->hasPermission($permission)) { return $next($request); } return redirect()->route('403'); // 没有权限则跳转到403页面 } }
Copy after loginRegister permission middleware:
InappHttpKernel.php
$routeMiddleware
Register permission middleware in the array:protected $routeMiddleware = [ // ... 'permission' => AppHttpMiddlewareCheckPermission::class, ];
Copy after loginAssociate middleware and routing:
Define the requirements inroutesweb.php
Permission control routing, and usepermission
middleware:Route::get('/members', 'MemberController@index')->middleware('permission:member_view');
Copy after login
5. Controller and view
In the controller, you can use the following code example to view the user The identity is verified and the corresponding view is returned according to the permissions.
Method in controller:
namespace AppHttpControllers; use IlluminateSupportFacadesAuth; class MemberController extends Controller { public function index() { if (Auth::user()->hasPermission('member_view')) { return view('members.index'); } // 没有权限则跳转到403页面 return redirect()->route('403'); } }
Copy after loginCode in view:
@if(Auth::user()->hasPermission('member_view')) <!-- 具有查看成员的权限,显示相关内容 --> <table> ... </table> @else <!-- 没有权限,显示无权限提示 --> <div>您没有查看成员的权限</div> @endif
Copy after loginSix , Summary
Through the above steps, we successfully implemented a simple and powerful permission management system in Laravel. By defining roles, permissions and corresponding relationships, using middleware to intercept routes, and judging permissions in controllers and views, we can achieve precise control of user access permissions. I hope this article can help you better understand and apply the permission management functions in Laravel.Reference:
- Laravel official documentation (https://laravel.com/docs/8.x/)
- Laravel Beyond CRUD series tutorials: Permissions Management (https://laravelbestpractices.com/series/show/laravel-beyond-crud/episodes/9)
The above is the detailed content of How to implement a permission management system in Laravel. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



The latest versions of Laravel 9 and CodeIgniter 4 provide updated features and improvements. Laravel9 adopts MVC architecture and provides functions such as database migration, authentication and template engine. CodeIgniter4 uses HMVC architecture to provide routing, ORM and caching. In terms of performance, Laravel9's service provider-based design pattern and CodeIgniter4's lightweight framework give it excellent performance. In practical applications, Laravel9 is suitable for complex projects that require flexibility and powerful functions, while CodeIgniter4 is suitable for rapid development and small applications.

Compare the data processing capabilities of Laravel and CodeIgniter: ORM: Laravel uses EloquentORM, which provides class-object relational mapping, while CodeIgniter uses ActiveRecord to represent the database model as a subclass of PHP classes. Query builder: Laravel has a flexible chained query API, while CodeIgniter’s query builder is simpler and array-based. Data validation: Laravel provides a Validator class that supports custom validation rules, while CodeIgniter has less built-in validation functions and requires manual coding of custom rules. Practical case: User registration example shows Lar

Laravel - Artisan Commands - Laravel 5.7 comes with new way of treating and testing new commands. It includes a new feature of testing artisan commands and the demonstration is mentioned below ?

For beginners, CodeIgniter has a gentler learning curve and fewer features, but covers basic needs. Laravel offers a wider feature set but has a slightly steeper learning curve. In terms of performance, both Laravel and CodeIgniter perform well. Laravel has more extensive documentation and active community support, while CodeIgniter is simpler, lightweight, and has strong security features. In the practical case of building a blogging application, Laravel's EloquentORM simplifies data manipulation, while CodeIgniter requires more manual configuration.

When choosing a framework for large projects, Laravel and CodeIgniter each have their own advantages. Laravel is designed for enterprise-level applications, offering modular design, dependency injection, and a powerful feature set. CodeIgniter is a lightweight framework more suitable for small to medium-sized projects, emphasizing speed and ease of use. For large projects with complex requirements and a large number of users, Laravel's power and scalability are more suitable. For simple projects or situations with limited resources, CodeIgniter's lightweight and rapid development capabilities are more ideal.

Microservice architecture uses PHP frameworks (such as Symfony and Laravel) to implement microservices and follows RESTful principles and standard data formats to design APIs. Microservices communicate via message queues, HTTP requests, or gRPC, and use tools such as Prometheus and ELKStack for monitoring and troubleshooting.

For small projects, Laravel is suitable for larger projects that require strong functionality and security. CodeIgniter is suitable for very small projects that require lightweight and ease of use.

Comparing Laravel's Blade and CodeIgniter's Twig template engine, choose based on project needs and personal preferences: Blade is based on MVC syntax, which encourages good code organization and template inheritance. Twig is a third-party library that provides flexible syntax, powerful filters, extended support, and security sandboxing.
