RBAC (Role-Based Access Control) role-based access control.
1. Basic idea: Introduce the concept of roles between users and access permissions, connect users and roles, and control user access to system resources through authorization of roles. Compared with traditional access control, the introduction of roles greatly simplifies the management of permissions. (Recommended learning: yii framework )
1). Role: It can be understood as a collection of permissions and permissions. For example: in a forum system, "super administrator" and "moderator" are roles.
2).Permissions: Moderators can manage posts in the forum, users in the forum, etc. These are permissions.
Implementation of rbac in Yii2
1.Yii2 implements a general layered RBAC, and the model it follows is also the NIST RBAC model.
2. The concept of rule is added in yii2. What is rule?
For example: For the article system, we have administrators and ordinary users, which allow administrators to perform any operations on articles, but only ordinary users are allowed to create articles and modify articles they create, that is to say Ordinary users have the permission to modify articles, but the restriction of Extra is that they can only modify their own articles. This verification of Extra is what the rules are responsible for.
3. The permission management implementation of yii2 supports two carriers: file and db. The core of the db-based implementation is four tables:
1) Storage roles or permissions Table: auth_item (type: 1 represents role; 2 represents permission)
CREATE TABLE `auth_item` ( `name` varchar(64) NOT NULL, `type` int(11) NOT NULL, `description` text, `rule_name` varchar(64) DEFAULT NULL, `data` text, `created_at` int(11) DEFAULT NULL, `updated_at` int(11) DEFAULT NULL, PRIMARY KEY (`name`), KEY `rule_name` (`rule_name`), KEY `type` (`type`), CONSTRAINT `auth_item_ibfk_1` FOREIGN KEY (`rule_name`) REFERENCES `auth_rule` (`name`) ON DELETE SET NULL ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8
2) The superior and subordinate association table of permissions and roles: auth_item_child
(includes the relationship: Roles can contain roles, roles can contain permissions, and permissions can contain permissions, but permissions cannot contain roles)
CREATE TABLE `auth_item_child` ( `parent` varchar(64) NOT NULL, `child` varchar(64) NOT NULL, PRIMARY KEY (`parent`,`child`), KEY `child` (`child`), CONSTRAINT `auth_item_child_ibfk_1` FOREIGN KEY (`parent`) REFERENCES `auth_item` (`name`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `auth_item_child_ibfk_2` FOREIGN KEY (`child`) REFERENCES `auth_item` (`name`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8
3) Assignment table of users and permissions (roles): auth_assignment
CREATE TABLE `auth_assignment` ( `item_name` varchar(64) NOT NULL, `user_id` varchar(64) NOT NULL, `created_at` int(11) DEFAULT NULL, PRIMARY KEY (`item_name`,`user_id`), CONSTRAINT `auth_assignment_ibfk_1` FOREIGN KEY (`item_name`) REFERENCES `auth_item` (`name`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8
4) Rule table: auth_rule
CREATE TABLE `auth_rule` ( `name` varchar(64) NOT NULL, `data` text, //存的是一個序列化的實現(xiàn)了yii\rbac\Rule接口的類的一個對象實例 `created_at` int(11) DEFAULT NULL, `updated_at` int(11) DEFAULT NULL, PRIMARY KEY (`name`), KEY `name` (`name`), KEY `created_at` (`created_at`), KEY `updated_at` (`updated_at`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='權(quán)限規(guī)則表';
The above is the detailed content of How to implement rbac in yii2. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

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

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

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

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

ToconfigureaYiiwidget,youcallitwithaconfigurationarraythatsetspropertiesandoptions.1.Usethesyntax\\yii\\widgets\\ClassName::widget($config)inyourview.2.Definethe$configarraywithkeysmatchingthewidget’spublicproperties.3.Somewidgetssupportnestedarraysf

To install the Yii framework, you need to configure PHP and Composer according to different operating systems. The specific steps are as follows: 1. You need to manually download PHP and configure environment variables on Windows, then install Composer, use commands to create a project and run a built-in server; 2. It is recommended to use Homebrew to install PHP and Composer, then create a project and start a development server; 3. Linux (such as Ubuntu) install PHP, extensions and Composer through apt, then create a project and deploy a formal environment with Apache or Nginx. The main differences between different systems are in the environment construction stage. Once PHP and Composer are ready, the subsequent processes are consistent. Note

It is crucial to clearly display verification errors when the user submits the form information incorrectly or missing. 1. Use inline error messages to directly display specific errors next to the relevant fields, such as "Please enter a valid email address", rather than general prompts; 2. Mark the problem fields visually by red borders, background colors or warning icons to enhance readability; 3. When the form is long or the structure is complex, display a click-through summary of the error that can be clicked and jumped at the top, but it needs to be used in conjunction with inline messages; 4. Enable real-time verification in the appropriate situation, and instant feedback when the user enters or leaves the field, such as checking the email format or password strength, but avoiding prompting too early before the user submits. These methods can effectively guide users to quickly correct input errors and improve the form filling experience.

Key skills to become a Yii framework developer include: 1) proficient in PHP and object-oriented programming (OOP), 2) understand MVC architecture, 3) proficient in using Yii's ActiveRecord, 4) familiar with Yii's Gii tools, 5) master RESTful API development, 6) possess front-end integration skills, 7) master debugging and performance optimization, 8) continuous learning and community participation. These skills combined can help developers work efficiently in the Yii framework.

The core process of creating a form in the Yii framework includes four steps: 1. Create a model class, define fields and verification rules; 2. Process the form submission and verification logic in the controller; 3. Render form elements in the view using ActiveForm; 4. Pay attention to CSRF protection, layout and style configuration. The model class sets the required items and data formats through the rules() method. The controller uses load() and validate() to process the submitted data. The view uses ActiveForm to automatically generate input boxes with labels and error prompts, and can customize the layout and styles, thereby achieving a complete form system.

The choice of Yii or Laravel depends on project requirements and team expertise. 1) Yii is suitable for high performance needs and has a lightweight structure. 2) Laravel provides rich functions, is developer-friendly and suitable for complex applications. Both are scalable, but Yii is easier to modular, while Laravel community is more resourceful.

beforeAction() is used in Yii2 to run logic before the controller action is executed. If permission checks or requests modification, it must return true or parent class call to continue execution; afterAction() is run after the action is executed and before the response is sent, which is suitable for output modification or logging. 1.beforeAction() is run before the action is executed, and can be used for user permission verification. For example, redirecting the unlogged user to the login page, you need to return parent::beforeAction($action) or true to continue the process, otherwise the action execution will be prevented; 2. You can skip the check of a specific action by checking $action->id; 3. AfterAc

Yii developers' career prospects still exist, but require diversified skills. 1) Yii still has demand in enterprise applications, but the market competition is fierce. 2) Yii skills can be transferred to other PHP frameworks. 3) Yii community has small support but sufficient resources. 4) Improve career flexibility by learning other frameworks and keeping Yii updated.
