Web development front-end and rear-end separation authority control method and system

Abstract

The invention discloses a web development front-end and rear-end separation authority control method and system, and relates to the technical field of web system authority control. The method comprises the steps of creating a role; initializing a service packet and interface data corresponding to the service packet; initializing functions and function interface data corresponding to the functions;initializing a menu and menu functions; initializing a role menu; initializing a role menu function; initializing an interface capable of being called by a role; carrying out role permission controljudgment; when a user calls an interface, the back end acquiring the role of the user; querying an interface list which can be called by the role of the user, and judging whether calling can be carried out or not according to the interface list which can be called by the role of the user. By decoupling the interface service logic and the permission control part, the rear-end interface only needs to realize the service logic, and when the interface needs to be increased or decreased, only the corresponding relationship between the function and the interface needs to be modified, so that the control method of the interface calling permission can be simplified, and the permission control complexity is reduced.

Description

technical field [0001] The present application relates to the technical field of web system authority control, and in particular, relates to a method and system for separating authority control between front and rear ends of web development. Background technique [0002] In web development, the separation of front-end and back-end has become the mainstream technology. By defining interfaces at the back-end, generating js (javascript) scripts and interface documents, the front-end can see all the interfaces provided by the back-end. Therefore, the front-end can call the back-end according to the documents. Any interface, so as to realize the data interaction between the front and back ends. Although the development efficiency can be improved by separating and decoupling the front and back ends, at the same time, for security reasons, when a user calls a back-end interface, it is necessary to determine whether the user has permission to call the interface, that is, it is neces...

AI Technical Summary

Problems solved by technology

[0003] The authority control method in the prior art is divided into two modules: menu and interface. There is no connection between the two modules. The granularity of menu authority control is relatively coarse, and the granularity of interface authority control is too fine. For some functions, the menu must be opened, and then the implementation interface of some functions in the menu must be opened, and customized page development must be carried out for different roles, and some functions in the menu cannot be opened through general configuration.

Images