Method for controlling resources in large browser/server (BS) structured system

Abstract

The invention provides a method for controlling resources in a large browser / server (BS) structured system. The method is mainly used for judging whether a uniform resource locator (URL) can be accessed and comprises the following steps of: if a menu identity (ID) is empty, indicating that the URL is not in an authority control range and can be accessed, otherwise, stepping into the next step; taking a corresponding authority list according to the menu ID and a user ID, if the list is empty, indicating that the user does not have the authority, and turning to an authority error webpage, otherwise, stepping into the next step; taking all function lists of the menu according to the menu ID, if an English code of a function is not comprised in the list, indicating that the function is not within function control, and only if the user has the authority to check the menu, indicating that the URL can be accessed, otherwise, stepping into the next step; and judging whether the authority list obtained in the step 2 comprises the English code of the function, and if the authority list comprises the English code of the function, the URL can be accessed, otherwise, turning to the authority error webpage. By the method, codes controlled by authorities can be concentrated, the code complexity can be reduced, and a phenomenon of leakage of control over the resources is avoided.

Description

technical field [0001] The invention relates to a resource control method, in particular to a resource control method in a large-scale BS structure system. Background technique [0002] In the development process of any large-scale BS structure system, user authority management must be involved. Currently, there are two methods commonly used, one is direct user-authority, and the other is user-role-authority, but no matter which Methods are inseparable from the definition of permissions, that is, to decompose and define various resources in the system. [0003] The current method usually used is to define a resource as a string identifier, through which an operation authority can be uniquely determined, this authority may be whether a certain button is visible, or whether some important data can be modified, software development Personnel define permissions during software development, and call the code for permission verification to judge during the coding process. [000...

AI Technical Summary

Problems solved by technology

[0004] This type of resource control method has relatively large defects, and the specific analysis is as follows: 1. Authority control is too scattered: In the process of system development, developers not only need to define and control various permissions, The authority control code is scattered in each module of the system and cannot be managed centrally, resulting in too arbitrary authority control and difficult to achieve unified management. When there are mutual calls between modules, it will be difficult to define the authority

2. Increased code complexity: Because the authority part is only responsible for judging the current authority based on the user's authority, software developers have to write a lot of logic judgment code, resulting in a large number of judgments and branch structures in the system, increasing the The logic complexity of the code is increased, and the probability of system bugs is also increased

3. Resource leakage control is prone to occur: In the process of system application, it is usually divided into two parts: the user interface (UI) and the background data operation. In order to enhance the user experience, it is necessary to control the permissions in the user interface (UI) and Double control of background data operation increases the workload of developers

In some systems, only the user interface is controlled, and the data operation in the background is not controlled. In this way, it is inevitable to simulate URL access to modify the resources of the system, and the purpose of protecting data security cannot be achieved.

4. Poor maintainability: In the management information system, the functions of the system are generally divided according to the menu, but when defining the authority, it is only a specific string corresponding to it, which has no direct relationship with the menu, which increases the number of authority assignees. maintenance difficulty