CN114697100A - An authentication method, system, terminal and storage medium for separate setting of front and back ends - Google Patents

Abstract

The invention discloses an authentication method, system, terminal and storage medium for separating front-end and back-end. The target resource authority corresponding to the user ID renders a first-level system page, and the first-level system page includes access links of multiple systems; receives a system access command, and obtains the user ID according to the system access command and the target resource authority The corresponding second-level module resource permissions, third-level page resource permissions, and fourth-level interface resource permissions are used to render corresponding pages. The present invention establishes a complete set of authentication mechanism, and the rules are clearly defined, which can ensure the safe and stable operation of the system.

Description

An authentication method, system, terminal and storage medium for separating front-end and back-end settings

technical field

The invention relates to the technical field of front-end and back-end separation setting authentication, in particular to a front-end and back-end separation setting authentication method, system, terminal and storage medium.

Background technique

With the popularization of mobile devices, the PC model in the traditional sense cannot support the development of mobile Internet. More and more enterprises adopt the separation of front-end and back-end, the back-end provides data interfaces, and the other ends are called through user information.

However, in the prior art, the authority is fixed in the front-end routing file, and the rule definition is not clear enough, which cannot guarantee the safe and stable operation of the authority control of the front-end page.

Therefore, the existing technology still needs to be improved and improved.

SUMMARY OF THE INVENTION

Aiming at the above-mentioned defects of the prior art, the present invention provides an authentication method, system, terminal and storage medium for separating the front and back ends, aiming to solve the problem that the definition of authority rules in the prior art is not clear, and the front-end page authority control cannot be guaranteed to operate safely and stably The problem.

In order to solve the above-mentioned technical problems, the technical scheme adopted in the present invention is as follows:

A first aspect of the present invention provides a front-end and back-end separation setting authentication method, the method comprising:

Obtain the user ID, and obtain the target resource authority corresponding to the user ID from the back end according to the user ID;

Rendering a first-level system page according to the target resource authority corresponding to the user ID, where the first-level system page includes access links of multiple systems;

A system access command is received, and according to the system access command and the target resource authority, the second-level module resource authority, the third-level page resource authority, and the fourth-level interface resource authority corresponding to the user ID are obtained to render the corresponding page.

The front-end and back-end separation setting authentication method, wherein the obtaining the target resource authority corresponding to the user ID from the back-end according to the user ID includes:

A user role is determined according to the user ID, and the target resource authority is determined according to the user role.

The front-end and back-end classification setting authentication method, wherein the resource of the target resource authority corresponding to the user ID is created in the back-end in advance, and the non-first-level resource in the target resource authority corresponds to a parent resource .

The front-end and back-end separation setting authentication method, wherein, according to the system access command and the target resource authority, obtaining the second-level module resource authority, the third-level page resource authority and the fourth-level interface resource authority to render the corresponding page, include:

Enter the sso page according to the system ID and token corresponding to the system access command;

Route matching is performed through the sso page, and the associated routing data of the secondary module resource authority and the tertiary page resource authority of the user ID in the system corresponding to the system ID is obtained;

The page is rendered according to the associated routing data and the user ID's level-4 interface resource authority in the system corresponding to the system ID.

The front-end and back-end separation setting authentication method, wherein the rendering a page according to the associated routing data and the user ID in the system corresponding to the system ID level-4 interface resource authority, includes:

Generate a system page menu according to the associated routing data;

The display mode of the buttons in the system page menu is determined according to the four-level interface resource authority in the target resource authority.

The authentication method for separate setting of front and back ends, wherein the performing route matching through the sso page to obtain the associated routing data of the secondary module resource and the tertiary page resource, comprising:

Through the sso page, the front-end routing object is matched with all the second-level module resources and the third-level page resources corresponding to the system ID pre-cached in the sso page to obtain filtering routing data;

The filtering routing data is added to the front-end routing to obtain the associated routing data.

The authentication method for separate setting of front-end and back-end, wherein the determining the display mode of the buttons in the page according to the four-level interface resource authority in the target resource authority includes:

Through the sso page, match all the level-4 interface resource permissions corresponding to the user ID with all level-4 interface resources in the system corresponding to the system ID by matching API addresses and request methods to determine whether the buttons on the page have operating authority;

When the button has operation authority, the display mode of the OK button is highlighted, and when the button has no operation authority, the display mode of the OK button is hidden or grayed out.

A second aspect of the present invention provides a front-end and back-end separation setting authentication system, comprising:

a permission determination module, which is used to obtain a user ID, and obtain a target resource permission corresponding to the user ID from the back end according to the user ID;

A first-level system rendering module, the first-level system rendering module is used to render a first-level system page according to the target resource authority corresponding to the user ID, and the first-level system page includes access links of multiple systems;

A page rendering module, the page rendering module is configured to receive a system access command, and obtain the second-level module resource authority, third-level page resource authority, and fourth-level interface corresponding to the user ID according to the system access command and the target resource authority Resource permissions to render the corresponding page.

A third aspect of the present invention provides a terminal, the terminal includes a processor and a computer-readable storage medium communicatively connected to the processor, the computer-readable storage medium is suitable for storing a plurality of instructions, the processor is suitable for invoking the instructions in the computer-readable storage medium to execute the steps of implementing the authentication method for separate front-end and back-end settings described in any one of the above.

A fourth aspect of the present invention provides a computer-readable storage medium, where the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to achieve The steps of setting the authentication method separately for the front and back ends as described in any of the above.

Compared with the prior art, the present invention provides a front-end and back-end separation setting authentication method, system, terminal and storage medium. System resources, second-level module resources, third-level page resources and fourth-level interface resources, according to the user's process, first obtain the first-level system page, and then obtain the page permissions in the system level by level, and establish a complete set of authentication mechanism, rules The definition is clear to ensure the safe and stable operation of the system.

Description of drawings

1 is a flowchart of an embodiment of an authentication method provided by the present invention in which the front and back ends are separated and set;

2 is a process diagram of creating a resource in an embodiment of the authentication method provided by the present invention;

3 is a schematic diagram of resources at all levels in the embodiment of the authentication method provided by the present invention for separating the front and back ends;

Fig. 4 is the processing flow chart of resource data preservation in the embodiment of the authentication method provided by the present invention;

5 is a flow chart of the role-resource authority operation in the embodiment of the authentication method provided by the present invention by separating the front and back ends;

Fig. 6 is the processing flow chart of front-end system and route authentication in the embodiment of front-end and back-end separation setting authentication method provided by the present invention;

7 is an effect diagram of a first-level system resource page in an embodiment of the authentication method provided by the present invention;

Fig. 8 is the processing flow chart of the menu resource authority in the embodiment of the authentication method provided by the present invention;

9 is a schematic diagram of a process of route authentication in an embodiment of the authentication method provided by the present invention;

10 is a schematic diagram of the process of route matching in the embodiment of the authentication method provided by the present invention;

Figure 11 is an effect diagram of a page menu in an embodiment of the authentication method provided by the present invention;

12 is a schematic diagram of the interface authentication process in the embodiment of the authentication method provided by the present invention;

13 is a schematic diagram of a button display effect in an embodiment of the authentication method provided by the present invention;

14 is a schematic structural diagram of an embodiment of an authentication system provided by the present invention in which the front and back ends are separated;

FIG. 15 is a schematic diagram of the principle of an embodiment of a terminal provided by the present invention.

Detailed ways

In order to make the objectives, technical solutions and effects of the present invention clearer and clearer, the present invention will be further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain the present invention, but not to limit the present invention.

The front-end and back-end separation setting authentication method provided by the present invention may be performed by a terminal. The terminals include, but are not limited to, various computers, servers, mobile phones, tablet computers, wearable devices, and the like.

Example 1

As shown in FIG. 1, an embodiment of the authentication method for separating front-end and back-end settings includes the steps:

S100. Obtain a user ID, and obtain a target resource authority corresponding to the user ID from the back end according to the user ID.

In this embodiment, resources are created at the back end in advance, and resources are allocated to different user IDs to generate target resource permissions corresponding to each user ID. In order to improve the efficiency of resource allocation, resources can be allocated based on roles, that is, all Described obtaining the target resource authority corresponding to the user ID from the back end according to the user ID, including:

A user role is determined according to the user ID, and the target resource authority is determined according to the user role.

The resource of the target resource permission corresponding to the user ID is created in the backend in advance, and the non-primary resource in the target resource permission corresponds to a parent resource. Specifically, as shown in FIG. 2, FIG. 3 and FIG. 4, resources are divided into first-level system resources, second-level module resources, third-level page resources and fourth-level interface resources, wherein the second-level module resources and third-level page resources can be They are collectively referred to as menu resources or routing resources, interface resources are subclasses of menu resources, and menu resources are subclasses of system resources.

In the new system, point out the system resources of the new system in the first-level menu of resource management, including the url and system name of the system. The first-level system resources are all the systems accessible to the user displayed in the application portal. The first-level system resource table can be shown in Table 1:

system name request method URL address operate xx content center get http://www.xxx.com/path1 xx xx settlement center get http://www.xxx.com/path2 xx xx customer service center get http://www.xxx.com/path3 xx xx operation and maintenance center get http://www.xxx.com/path4 xx

Table 1

The secondary module resource is mainly associated with the parent menu address of the system. You need to fill in the system, url, and module name to which it belongs. The system to which it belongs is the primary system resource. The secondary module resource table can be shown in Table 2:

module name owning system request method URL address operate XxManagement xx content center get /path5 xx Xx review xx settlement center get /path6 xx Xx record xx customer service center get /path7 xx Xx module xx operation and maintenance center get /path8 xx

Table 2

The third-level page resource belongs to the subclass page address in the second-level module resource. You need to fill in the second-level module, name and url to which it belongs. The third-level page resource table can be shown in Table 3:

page name owning system owning module request method URL address operate Xx list xx content center xx management get /path9 xx XxDetails xx content center xx management get /path10 xx Xx entry xx content center xx management get /path11 xx Xx query xx operation and maintenance center xx management get /path12 xx

table 3

Level-4 interface resources can also be called functional resources. After selecting a level-3 page resource, you can enter its corresponding level-4 function resource list page, and then add all functional interface data under level-3 page resources. You need the page to which the antenna belongs, Feature name and url. The four-level interface resource table can be shown in Table 4:

page name owning system owning module request method URL address operate xx list xx content center xx management post /path13 xx xx details xx content center xx management get /path14 xx xx input xx content center xx management put /path15 xx xx query xx operation and maintenance center xx management delete /path16 xx

Table 4

When creating a resource, if you select the resource level, if it is a non-first-level resource, you need to select the corresponding parent resource, and if it is a first-level resource, you can directly store it.

As shown in Figure 5, to create a user and role, add a role to the role list, you need to fill in the role name, parent orange, and whether to break through the parent option, where the parent role is initialized as a super administrator. Associate the role with the corresponding resource, set the resource permission in the role list, select the resource with the number created in the resource creation stage and save it. For created users, associate users with roles, so that resource permissions are configured for each user.

S200. Render a first-level system page according to the target resource authority corresponding to the user ID, where the first-level system page includes access links of multiple systems.

In this embodiment, multiple systems are controlled by the same application. As shown in FIG. 6 , after the user logs in to the application through the user ID, he first obtains the first-level system resource authority according to the user ID, and then renders the first-level system. page, the rendering is shown in Figure 7.

S300. Receive a system access command, and obtain the second-level module resource authority, third-level page resource authority, and fourth-level interface resource authority corresponding to the user ID according to the system access command and the target resource authority to render the corresponding page.

The obtaining the second-level module resource authority, the third-level page resource authority and the fourth-level interface resource authority according to the system access command and the target resource authority to render the corresponding page, including:

Enter the sso page according to the system ID and token corresponding to the system access command;

Route matching is performed through the subsystem sso page, and the associated routing data of the secondary module resource authority and the tertiary page resource authority of the user ID in the system corresponding to the system ID is obtained;

The page is rendered according to the associated routing data and the user ID's level-4 interface resource authority in the system corresponding to the system ID.

When the user clicks on a system link, the system access command is issued, and the system ID of the system and the token corresponding to the user are entered into the system sso page. The asynchronous routing matches the associated routing data, and then generates the system menu through the addRoutes method.

As shown in FIG. 8 , after receiving the system access command, it is necessary to match the new route to realize the rendering of the page menu. Specifically, as shown in FIG. 9 , there are all two, The third and fourth level resources are stored in vuex, and the resource data is kept persistent. The browser is appropriately cached according to the role resource data. The resource data cached in the sso page can be cleared and updated according to the number and frequency of resource visits. Improve access speed. Define front-end permission control files and methods, including filtering routing methods, caching permission methods, and dynamically adding routing methods. The routing resource authority corresponding to the user ID is matched with all secondary and tertiary resources in the system corresponding to the system ID to implement route filtering. As shown in Figure 10, after the matching is successful, the associated routing data is obtained according to the successfully matched routing resource authority, and the associated routing data is added to the front-end routing to realize the rendering of the system page menu, as shown in Figure 11 .

The code for route authentication is as follows:

The described rendering page according to the associated routing data and the user ID in the system corresponding to the system ID's four-level interface resource authority, including:

Generate a system page menu according to the associated routing data;

The display mode of the buttons in the page is determined according to the four-level interface resource authority in the target resource authority.

The determining the display mode of the buttons in the page according to the four-level interface resource authority in the target resource authority includes:

Through the sso page, match all the level-4 interface resource permissions corresponding to the user ID with all level-4 interface resources in the system corresponding to the system ID by matching API addresses and request methods to determine whether the buttons on the page have operating authority;

When the button has operation authority, the display mode of the OK button is highlighted, and when the button has no operation authority, the display mode of the OK button is hidden or grayed out.

The permission control involving button operations in the page menu is implemented by a conventional scheme, that is, the front-end pre-books the four-level resource corresponding to each button operation in the page code layer, as well as the api interface address and request method of the four-level resource. All four-level interface resources of the current system are matched to determine whether the button has operation authority, and then determine the display mode of the button.

Specifically, as shown in FIG. 12 , the corresponding interface address and request method are defined in the front-end port file, and the data parameters defined by the interface are bound to the instruction in the same component introduction method. For example, when caching a level-4 interface resource in an sso page, set its format to ['get','url'], where the 'get' example is the request method, and the 'url' example is the interface address, which stores the request method, and combines the request method with the The interface address is also used as a matching condition, which can avoid the situation that different operation types have the same url, and the corresponding operation cannot be distinguished simply based on the url. The button is associated with all the four-level resource rights of the user ID by means of instructions to match, and filter out the four-level resource rights of the user ID in the current system (the system corresponding to the system ID), so as to determine the menu. Whether each button of the button has operation authority, according to whether there is operation authority, the button is highlighted or grayed out and hidden. The effect diagram is shown in Figure 13.

The code for button operation permission authentication is as follows:

The $_has method is encapsulated as follows:

The button reference is as follows:

<el-button v-has="titleParams.permission.add"></el-button>

To sum up, this embodiment provides an authentication method for separating front-end and back-end settings. The corresponding target data provider and target data specification are determined through target links, and target data is collected from the target data provider according to the target data specification. Depending on the cooperation agreement, when you need to collect data from multiple data providers or add data providers, you only need to add links and map them to different data providers and data specifications. There is no need to create new front-end and back-end separation settings for authentication. interface, reducing duplication of work.

It should be understood that although the various steps in the flowcharts given in the accompanying drawings of the present invention are shown in sequence according to the arrows, these steps are not necessarily executed in sequence according to the sequence shown by the arrows. Unless explicitly stated herein, the execution of these steps is not strictly limited to the order, and these steps may be performed in other orders. Moreover, at least a part of the steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but may be executed at different times. The execution of these sub-steps or stages The sequence is also not necessarily sequential, but may be performed alternately or alternately with other steps or sub-steps of other steps or at least a portion of a phase.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable computer. In the readable storage medium, when executed, the computer program may include the processes of the above-mentioned method embodiments. Wherein, any reference to memory, storage, database or other medium used in the various embodiments provided by the present invention may include non-volatile and/or volatile memory. Nonvolatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain Road (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

Embodiment 2

Based on the above embodiment, the present invention also provides a front-end and back-end separation setting authentication system. As shown in FIG. 14 , the front-end and back-end separation setting authentication system includes:

a permission determination module, the permission determination module is configured to obtain a user ID, and obtain the target resource permission corresponding to the user ID from the back end according to the user ID, specifically as described in Embodiment 1;

A first-level system rendering module, the first-level system rendering module is used to render a first-level system page according to the target resource authority corresponding to the user ID, and the first-level system page includes access links of multiple systems, as in the embodiment. as stated in one;

A page rendering module, the page rendering module is configured to receive a system access command, and obtain the second-level module resource authority, third-level page resource authority, and fourth-level interface corresponding to the user ID according to the system access command and the target resource authority resource permissions to render the corresponding page, as described in the first embodiment.

Embodiment 3

Based on the above embodiment, the present invention also provides a terminal correspondingly, as shown in FIG. 15 , the terminal includes a processor 10 and a memory 20 . FIG. 15 only shows some components of the terminal, but it should be understood that it is not required to implement all the shown components, and more or less components may be implemented instead.

In some embodiments, the memory 20 may be an internal storage unit of the terminal, such as a hard disk or a memory of the terminal. In other embodiments, the memory 20 may also be an external storage device of the terminal, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD card) equipped on the terminal. ) card, flash card (Flash Card) and so on. Further, the memory 20 may also include both an internal storage unit of the terminal and an external storage device. The memory 20 is used for storing application software and various types of data installed in the terminal. The memory 20 can also be used to temporarily store data that has been output or is to be output. In one embodiment, the memory 20 stores a front-end and back-end separation setting authentication program 30, and the front-end and back-end separation setting authentication program 30 can be executed by the processor 10, thereby realizing the front-end and back-end separation setting authentication method in this application.

In some embodiments, the processor 10 may be a central processing unit (Central Processing Unit, CPU), a microprocessor or other chips, for running the program codes or processing data stored in the memory 20, such as executing all The front-end and back-end are separated to set the authentication method, etc.

In one embodiment, when the processor 10 executes the front-end and back-end separation setting authentication program 30 in the memory 20, the following steps are implemented:

Obtain the user ID, and obtain the target resource authority corresponding to the user ID from the back end according to the user ID;

Rendering a first-level system page according to the target resource authority corresponding to the user ID, where the first-level system page includes access links of multiple systems;

A system access command is received, and according to the system access command and the target resource authority, the second-level module resource authority, the third-level page resource authority, and the fourth-level interface resource authority corresponding to the user ID are obtained to render the corresponding page.

Wherein, obtaining the target resource authority corresponding to the user ID from the back end according to the user ID includes:

A user role is determined according to the user ID, and the target resource authority is determined according to the user role.

The resource of the target resource authority corresponding to the user ID is created in the back end in advance, and the non-primary resource in the target resource authority corresponds to a parent resource.

Wherein, obtaining the second-level module resource authority, the third-level page resource authority and the fourth-level interface resource authority according to the system access command and the target resource authority to render the corresponding page, including:

Enter the sso page according to the system ID and token corresponding to the system access command;

Route matching is performed through the sso page, and the associated routing data of the secondary module resource authority and the tertiary page resource authority of the user ID in the system corresponding to the system ID is obtained;

The page is rendered according to the associated routing data and the user ID's level-4 interface resource authority in the system corresponding to the system ID.

Wherein, the rendering of the page according to the associated routing data and the user ID in the system corresponding to the system ID's four-level interface resource authority includes:

Generate a system page menu according to the associated routing data;

The display mode of the buttons in the system page menu is determined according to the four-level interface resource authority in the target resource authority.

Wherein, performing route matching through the sso page to obtain the associated routing data of the secondary module resource and the tertiary page resource, including:

Through the sso page, the front-end routing object is matched with all the second-level module resources and the third-level page resources corresponding to the system ID pre-cached in the sso page to obtain filtering routing data;

The filtering routing data is added to the front-end routing to obtain the associated routing data.

Wherein, determining the display mode of the buttons in the page according to the four-level interface resource authority in the target resource authority includes:

Through the sso page, match all the level-4 interface resource permissions corresponding to the user ID with all level-4 interface resources in the system corresponding to the system ID by matching API addresses and request methods to determine whether the buttons on the page have operating authority;

When the button has operation authority, the display mode of the OK button is highlighted, and when the button has no operation authority, the display mode of the OK button is hidden or grayed out.

Embodiment 4

The present invention also provides a computer-readable storage medium, in which one or more programs are stored, and the one or more programs can be executed by one or more processors to realize the above-mentioned front-end and back-end separation setting authentication Steps of the right method.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present invention, but not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand: it can still be Modifications are made to the technical solutions described in the foregoing embodiments, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims (10)

1. a front-end and back-end separation setting authentication method, is characterized in that, described method comprises: Obtain the user ID, and obtain the target resource authority corresponding to the user ID from the back end according to the user ID; Rendering a first-level system page according to the target resource authority corresponding to the user ID, where the first-level system page includes access links of multiple systems; A system access command is received, and according to the system access command and the target resource authority, the second-level module resource authority, the third-level page resource authority, and the fourth-level interface resource authority corresponding to the user ID are obtained to render the corresponding page. 2. the front-end and back-end separation setting authentication method according to claim 1, is characterized in that, described obtaining the target resource authority corresponding to described user ID from back end according to described user ID, comprising: A user role is determined according to the user ID, and the target resource authority is determined according to the user role. 3. The front-end and back-end separation setting authentication method according to claim 2 is characterized in that, the resource of the target resource authority corresponding to the user ID is created in advance in the back-end, and the non-target resource authority in the target resource authority is created in advance. A first-level resource corresponds to a parent resource. 4. The front-end and back-end separation setting authentication method according to claim 1, is characterized in that, according to described system access command and described target resource authority, obtain secondary module resource authority, 3-level page resource authority and 4-level resource authority Interface resource permissions to render corresponding pages, including: Enter the sso page according to the system ID and token corresponding to the system access command; Route matching is performed through the sso page, and the associated routing data of the secondary module resource authority and the tertiary page resource authority of the user ID in the system corresponding to the system ID is obtained; The page is rendered according to the associated routing data and the user ID's level-4 interface resource authority in the system corresponding to the system ID. 5. The front-end and back-end separation setting authentication method according to claim 4, is characterized in that, described according to described associative routing data and described user ID in the system of described system ID corresponding four-level interface resource authority rendering pages, including: Generate a system page menu according to the associated routing data; The display mode of the buttons in the system page menu is determined according to the four-level interface resource authority in the target resource authority. 6. The front-end and back-end separation setting authentication method according to claim 4, is characterized in that, described carries out route matching by described sso page, obtains the associated routing data of described secondary module resource and described tertiary page resource ,include: Through the sso page, the front-end routing object is matched with all the second-level module resources and the third-level page resources corresponding to the system ID pre-cached in the sso page to obtain filtering routing data; The filtering routing data is added to the front-end routing to obtain the associated routing data. 7. The front-end and back-end separation setting authentication method according to claim 5, wherein, determining the display mode of the button in the page according to the four-level interface resource authority in the target resource authority, comprising: Through the sso page, match all the level-4 interface resource permissions corresponding to the user ID with all level-4 interface resources in the system corresponding to the system ID by matching API addresses and request methods to determine whether the buttons on the page have operating authority; When the button has operation authority, the display mode of the OK button is highlighted, and when the button has no operation authority, the display mode of the OK button is hidden or grayed out. 8. A front-end and back-end separation setting authentication system is characterized in that, comprising: a permission determination module, which is used to obtain a user ID, and obtain a target resource permission corresponding to the user ID from the back end according to the user ID; a first-level system rendering module, the first-level system rendering module is used to render a first-level system page according to the target resource authority corresponding to the user ID, and the first-level system page includes access links of multiple systems; A page rendering module, the page rendering module is configured to receive a system access command, and obtain the second-level module resource authority, third-level page resource authority and fourth-level interface corresponding to the user ID according to the system access command and the target resource authority Resource permissions to render the corresponding page. 9. A terminal, characterized in that the terminal comprises: a processor and a computer-readable storage medium communicatively connected to the processor, the computer-readable storage medium being adapted to store a plurality of instructions, and the processor being adapted to The instructions in the computer-readable storage medium are invoked to execute the steps of implementing the authentication method for separate front-end and back-end settings according to any one of the preceding claims 1-7. 10. A computer-readable storage medium, characterized in that, the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to realize the claim The steps of setting the authentication method separately for the front-end and back-end according to any one of requirements 1-7.

Images