Role-Based Menu Authorization Method

Abstract

The invention discloses a role-based menu authorization method, which includes: selecting one or more roles as authorized objects, each role is an independent individual, not a group / class, and a role can only be associated with a unique user at the same time , and a user is associated with one or more roles; when there is only one authorized object, the permission candidate menu is displayed, and the menu in the permission candidate menu that has been selected and saved by the authorized object before is automatically selected, and from the permission candidate menu Select the corresponding menu; when there are two or more authorized objects, display a blank permission candidate menu, select the corresponding menu from the permission candidate menu; save the permission of the authorized object. In the present invention, a role can only be associated with a unique user at the same time period, and a user is associated with one or more roles, and the user obtains the menu authority through the associated role, and the menu authorization for new employees or post-shift employees is simpler and more convenient, and the form authorization is improved. s efficiency.

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