Method of authorizing an authorized operator in a system

Abstract

The invention discloses a method for authorizing an authorized operator in a system, which comprises the following steps: a system operator selecting one or more authorized operators; setting one or more licensees for each licensed operator, respectively; each authorization operator setting permissions for each authorization operator who needs to set permissions among all authorizations corresponding to the authorization operator. The authorized person performs a corresponding operation according to a right set for the authorized person. A plurality of authorization operators can be arranged in the invention, so that the corresponding authorization operator who clearly understands the rights of each authorization person can authorize each authorization person, so that the authorization operation is not prone to error.

Description

technical field [0001] The invention relates to an authorization method of management software systems such as ERP, in particular to a method for authorizing authorized operators in the system. 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 v...

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, directly authorizing users has the disadvantages of 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] For a large-scale management software system, there are many people who need to be authorized, and there are many permissions that need to be granted to the authorized person, and there are many functional modules included. The traditional authorization method is the system operator (admin / system super administrator) Authorize directly; however, in many cases, the system operator is the network administrator, and the authority of each position and employee is not clear. Usually, the authorization is given to the system operator by the relevant personnel dictating or writing in words, but the system administrator Administrators may have misunderstandings, resulting in authorization errors

[0011] In addition, the existing authorized operators are only system operators. For large-scale software systems, there are a large number of authorization requirements, which makes the authorization workload of system operators huge and error-prone.

Images