One-to-one authority authorization method and system on user based on roles

Abstract

The invention discloses a one-to-one authority authorization method and system on a user based on roles. The method comprises the steps of 1, building the roles, wherein each role is an independent individual, and is not in a group and / or a category; 2, authorizing the roles built in the first step separately; 3, associating the user to the roles, wherein in the same time frame, one role can be only associated to sole user, while one user can be associated to one or more roles. According to the one-to-one authority authorization method and system on the user based on the roles, the roles are independent individuals, and are different from those of traditional group and / or category properties, and in the same time frame, one role can be associated to sole user, thus the authority management efficiency in the system using process is sharply improved, dynamic authorization is simpler, more convenient, and clearer, and the efficiency and reliability in authority arrangement are improved.

Description

technical field [0001] The invention relates to a user authority management method of management software systems such as EPR, in particular to a role-based one-to-one authority authorization method and system for users. 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...

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

Images