Menu authorization method based on roles

Abstract

The invention discloses a menu authorization method based on roles. The menu authorization method comprises steps that one role or a plurality of roles are selected as authorized objects, and each role is an independent individual, and is not a group/category, and one role is only associated with a unique user in the same period, and one user is associated with one role or a plurality of roles; when the number of the authorized objects is one, authority candidate menus are displayed, and the authorized object in the authority candidate menus is selected, and the stored menu is automatically selected, and then the corresponding menu is selected from the authority candidate menus; when the number of the authorized objects is two or more than two, blank authority candidate menus are displayed, and the corresponding menu is selected from the authority candidate menus; the authorities of the authorized objects are stored. One role is only associated with the unique user in the same period, and one user is associated with one role or a plurality of roles, and the users can acquire the menu authorities by the associated roles, and therefore menu authorization of new employees or transferred employees is simple and convenient, and form authorization efficiency 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

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.

[0011] 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

[0012] 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

[0013] 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

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

Images