Menu authorization method based on roles

Abstract

The invention discloses a menu authorization method based on roles. The method includes steps: selecting one or more roles as authorized objects, wherein each role is an independent individual ratherthan a group / kind, one role in the same period can only be associated with a unique user, and one user is associated with one or more roles; when the authorized object is one, displaying permission candidate menus, automatically selecting saved menus, and selecting a corresponding menu from the permission candidate menus, wherein the authorized objects in the permission candidate menus are previously selected; when the authorized objects are two or more, displaying a blank permission candidate menu, and selecting a corresponding menu from the permission candidate menus; and saving the permissions of the authorized objects. According to the method, one role can only be associated with the unique user in the same period, one user is associated with one or more roles, the users can obtain themenu permissions through the associated roles, the menu authorization of new employees and position-transfer employees is simpler and more convenient, and the efficiency of form authorization is improved.

Description

technical field [0001] The invention relates to a form authorization method of management software systems such as ERP, in particular to a role-based menu authorization method. Background technique [0002] Role-based access control (RBAC) is the most researched and thoughtful database permission management mechanism in recent years. It is considered to be an ideal candidate to replace traditional mandatory access control (MAC) and discretionary access control (DAC). The basic idea of ​​role-based access control (RBAC) is to divide different roles according to different functional positions in the enterprise organization view, encapsulate the access rights of database resources in roles, and users can indirectly access database resources by being assigned different roles. [0003] There are often a large number of tables and views in large-scale application systems, which makes the management and authorization of database resources very complicated. It is very difficult for...

AI Technical Summary

Problems solved by technology

[0005] However, the traditional role-based user rights management methods all adopt the "role-to-user one-to-many" association mechanism. / Position / Type of work and other concepts, the authorization of user rights under this association mechanism is basically divided into the following three forms: 1. figure 1 As shown, the disadvantage of directly authorizing users is heavy workload, frequent and cumbersome operations; 2. figure 2 As shown, authorize the role (category / group / position / type of work) (a role can be associated with multiple users), and the user obtains the authority through the role; 3. For example image 3 As shown, the combination of the above two methods

[0006] In the above statement, both 2 and 3 need to authorize the role of class / group nature, but the way of authorization through the role of class / group / post / work type has the following disadvantages: 1. The operation is difficult when the user authority changes: In the actual system use, it is often necessary to adjust the user's permissions during the operation process. For example, when dealing with changes in employee permissions, the permissions of an employee associated with a role change. We cannot Changes to change the permissions of the entire role, because the role is also associated with other employees whose permissions have not changed

The above two processing methods not only take a long time to authorize the role in the case of many role permissions, but also are prone to mistakes. The operation of the user is cumbersome and troublesome, and it is also easy to make mistakes and cause losses to the system user.

[0007] 2. It is difficult to remember the specific permissions contained in the role for a long time: If the role has many permission function points, it is difficult to remember the specific permissions of the role over time, and it is even more difficult to remember the permission differences between roles with similar permissions. To associate a new user, it is impossible to accurately determine how to choose the association

[0008] 3. Due to the change of user permissions, more and more roles will be created (if no new roles are created, the direct authorization to users will be greatly increased), and it is more difficult to distinguish the specific differences between the permissions of each role

[0009] 4. When transferring a post, if you want to assign many permissions of the transferred user to several other users, you must distinguish these permissions of the transferred user during processing, and then create roles to associate with the other users. users, such an operation is not only complicated and time-consuming, but also prone to errors

[0010] The traditional menu authorization for employees is to directly authorize the menus for each employee. When employees are transferred, they need to authorize the menus for employees again. When there are many menus, the workload is heavy and the efficiency is low.

Images