WO2021068569A1 - Authentication method and apparatus, and computer system and readable storage medium - Google Patents

Abstract

Disclosed are an authentication method and apparatus, and a computer system and a readable storage medium, which are based on the technical field of clouds. The method comprises: creating, based on a preset operation framework, an authentication node having a framework rule, wherein the authentication node includes a permission database; receiving login information sent by a client by means of the authentication node, and acquiring permission information matching the login information from the permission database; storing the permission information by means of the authentication node according to the framework rule; receiving, by means of the authentication node, access information and a URL request which are sent by the client, using the framework rule to respectively compare the access information and the URL request with the permission information in the authentication node to obtain a permission result, and loading the permission result to the URL request to obtain a new URL request; and acquiring system information by means of the authentication node according to the new URL request, or generating a failure prompt box. The present application causes the client, while accessing different systems, to realize authorized access and unauthorized access by means of the permission result only, thereby increasing the operating speed of the system.

Description

Authentication method, device, computer system and readable storage medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on October 12, 2019, the application number is CN201910969165.2, and the invention title is "a certification method, device, computer system and readable storage medium", all of which The content is incorporated in this application by reference.

Technical field

This application relates to the field of communication technology, and in particular to an authentication method, device, computer system, and readable storage medium, which can be applied in the field of big data database clusters.

Background technique

Traditional virtual user authentication is implemented in the following ways:

First determine whether the client's login information is registered in the database, and then obtain the client's login authority from the database. For example, the login authority is that the client can only access the A system; when the client needs to access the A system, it can be based on the login authority Successful access. However, when the customer needs to access the B system, he needs to return to the database again to confirm whether the client has the access permission. If not, then generate a page without permission and output it to the client; the inventor realizes this This method allows the client to return to the database to confirm the authority every time it accesses a different system, which leads to frequent interactions between the client and the database, which greatly increases the amount of system calculations, and reduces the system's calculation speed and efficiency. .

Summary of the invention

The purpose of this application is to provide an authentication method, device, computer system, and readable storage medium, which are used to solve the problem that each time the client accesses a different system, it must return to the database to confirm the authority once, resulting in frequent client and database Interaction, causing the problem of reduced system operation speed and operation efficiency.

In order to achieve the above objective, this application provides an authentication method, including the following steps: S1: Create an authentication node with framework rules based on a preset operating framework, the authentication node includes a permission database, and generates a creation success signal and sends it Output to the client; S2: receive the login information sent by the client through the authentication node, and obtain permission information matching the login information in the permission database; S3: pass the authentication node according to the framework The rules store the authority information, generate a cache success signal and send it to the client; S4: receive the access information and URL request sent by the client through the authentication node, and use the framework rules to transfer the access The information and URL request are respectively compared with the authority information in the authentication node to obtain the authority result, and the authority result is loaded into the URL request to obtain a new URL request; S5: according to the authentication node The new URL requests to obtain system information, or generates a failure prompt box; and outputs the system information or failure prompt box to the client.

In order to achieve the above object, the present application also provides an authentication device, including: a creation module, used to create an authentication node with framework rules based on a preset operating framework, the authentication node includes a permission database, and generates and outputs it To the client; an authority management module, used to receive the login information sent by the client through the authentication node, and obtain the authority information matching the login information in the authority database; a cache module, used to pass the The authentication node stores the authority information according to the framework rules, generates a cache success signal and sends it to the client; a request judgment module is used to receive the access information and URL request sent by the client through the authentication node , Using the framework rules to compare the access information and the URL request with the authorization information in the authentication node to obtain the authorization result, and load the authorization result into the URL request to obtain a new URL Request; a feedback module for obtaining system information according to the new URL request through the authentication node, or generating a failure prompt box; outputting the system information or failure prompt box to the client.

To achieve the above objective, the present application also provides a computer system, which includes multiple computer devices, each computer device includes a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the multiple A processor of a computer device executes an authentication method, wherein the authentication method includes the following steps: S1: Create an authentication node with framework rules based on a preset operating framework, the authentication node includes a permission database, and generates the creation Success signal and output it to the client; S2: receive the login information sent by the client through the authentication node, and obtain permission information matching the login information in the permission database; S3: pass the authentication The node stores the authority information according to the framework rules, generates a cache success signal and sends it to the client; S4: receives the access information and URL request sent by the client through the authentication node, and uses the framework The rule compares the access information and URL request with the authority information in the authentication node to obtain the authority result, and loads the authority result into the URL request to obtain a new URL request; S5: pass The authentication node requests to obtain system information according to the new URL, or generates a failure prompt box; and outputs the system information or failure prompt box to the client.

In order to achieve the above object, the present application also provides a computer-readable storage medium, which includes a plurality of storage media, and each storage medium stores a computer program, wherein the computer program stored in the plurality of storage media is stored by a processor An authentication method is implemented during execution, wherein the authentication method includes the following steps: S1: Create an authentication node with framework rules based on a preset operating framework, the authentication node includes a permission database, and generates a creation success signal and It is output to the client; S2: receiving the login information sent by the client through the authentication node, and obtaining permission information matching the login information in the permission database; S3: passing the authentication node according to the The framework rules store the authority information, generate a cache success signal and send it to the client; S4: receive the access information and URL request sent by the client through the authentication node, and use the framework rules to transfer the The access information and the URL request are respectively compared with the authority information in the authentication node to obtain the authority result, and the authority result is loaded into the URL request to obtain a new URL request; S5: pass the authentication node According to the new URL request to obtain system information, or generate a failure prompt box; output the system information or the failure prompt box to the client.

The authentication method, device, computer system, and readable storage medium provided by the present application create a permission database and create an operation framework through a creation module, obtain permission information matching the login information through the permission management module, and the cache module for the permission Information is stored;

Then, the request judgment module calculates the login information to obtain the authority result, and loads the authority result into the URL request;

Finally, through the feedback module, access the system server and obtain system information according to the authority result, or generate a failure prompt box; then output the system information or failure prompt box to the client;

Therefore, when the client accesses different system servers, it only needs to obtain the permission result by requesting the judgment module, and then access the corresponding system server or generate a failure prompt box through the permission result;

In this way, when the client frequently accesses different systems, it only needs to use the permission result to realize the right and unauthorized access, which greatly reduces the amount of system calculations, and further improves the system's calculation speed and calculation efficiency.

Description of the drawings

FIG. 1 is a flowchart of Embodiment 1 of the authentication method of this application;

2 is a schematic diagram of program modules of Embodiment 2 of the authentication device of this application;

FIG. 3 is a schematic diagram of the hardware structure of the computer equipment in the third embodiment of the computer system of this application.

Reference signs:

1. Authentication device 2. Computer equipment 11. Create module 12. Authority management module

13. Cache module 14. Request judgment module 15. Feedback module 21, memory

22, processor

Detailed ways

In order to make the purpose, technical solutions, and advantages of this application clearer, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present application, and are not used to limit the present application. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

The authentication method, device, computer system, and readable storage medium provided in this application are suitable for the communication field, and provide an authentication method based on a creation module, a rights management module, a cache module, a request judgment module, and a feedback module. In this application, a permission database is created through a creation module and an operating framework is created, permission information matching the login information is obtained through the permission management module, and the cache module stores the permission information; and then the login information is processed through the request judgment module Operate to obtain the authority result, and load the authority result into the URL request; finally, use the feedback module to access the system server and obtain system information according to the authority result, or generate a failure prompt box; and then load the system information or failure The prompt box is output to the client; so that when the client accesses different system servers, it only needs to obtain the permission result by requesting the judgment module, and then access the corresponding system server through the permission result or generate a failure prompt box.

Example one

Please refer to Fig. 1, an authentication method of this embodiment, using the authentication device 1, includes the following steps:

S1: Create an authentication node with framework rules based on a preset operating framework, the authentication node includes a permission database, and generates a creation success signal and outputs it to the client;

S2: receiving the login information sent by the client through the authentication node, and obtaining permission information matching the login information in the permission database;

S3: Store the authority information according to the framework rules through the authentication node, generate a cache success signal, and send it to the client;

S4: Receive the access information and URL request sent by the client through the authentication node, and use the framework rules to compare the access information and URL request with the authority information in the authentication node to obtain authority results , And load the authority result into the URL request to obtain a new URL request;

S5: Obtain system information according to the new URL request through the authentication node, or generate a failure prompt box; output the system information or the failure prompt box to the client.

In this embodiment, the operating framework is a technical implementation framework for the determined requirements, using a complete set of tools, and components that complete tasks under planning steps; the framework rules are for the access information and URL The rules for requesting calculations to obtain permission results can be written in JAVA language or C language; since the framework rules are set in the running framework, authentication nodes based on the framework rules can be created based on the running framework; the permission database Used to store standard resource addresses, multi-level management can be performed on the standard resource addresses in the authority database, so that each standard resource address can have different levels of authority;

The login information includes at least a login account number and a login password. The login information may also include a login device IMEI code, and/or a mobile phone number, and/or a mobile phone verification code; the authority information includes at least role information corresponding to the login information , And the role authority corresponding to the role information, the role information of the client is determined through the login information, and the corresponding role authority is obtained according to the role information;

The running framework can also be used to store data, so the permission information of the client is stored in the running framework according to the framework rules, so that the permission information of the client currently being accessed can be quickly obtained;

The access information is used to describe the identity of the client. Since it is necessary to ensure the uniqueness of the client and the convenience of the client to generate and output access information, the access information in this embodiment can be set as the IMEI code of the login device , And/or mobile phone number, and/or mobile phone verification code; a new URL request is obtained by loading the permission result in the URL request, so as to mark the URL request so that the authentication node only passes the mark, that is, the permission result, that is The URL request can be judged, and based on the judgment, system information can be obtained according to the new URL request, or a failure prompt box can be generated.

It should be noted that the authentication node in this application is equivalent to a virtualized proxy server or a proxy node that performs authentication tasks, and can be installed in the system server as a component of the server. Therefore, the system server includes storage Server A and server B for web page information, and proxy server C for installing the authentication node.

At the same time, URL (Uniform Resource Locator) request is a concise representation of the location and access method of resources available on the Internet, and is the address of a standard resource on the Internet; each file on the Internet has a unique URL, it contains information that indicates the location of the file and how the browser should handle it. In this embodiment, the URL request is the address of a standard resource used to obtain information from the system server. Therefore, the authorization result is loaded into the URL request. This technical solution will first determine whether the URL request has the authorization result. Then it is judged whether the permission result is right, if it is right, the information in the system server is obtained through the URL request and returned to the client; the permission result in the URL request is extracted, and the content of the permission result is judged; If the permission result is right, access the system server specified by the URL request and obtain the system information of the system server; if the permission result is no right, a failure prompt box is generated; and the system information or failed The prompt box is output to the client. It should be noted that the system server is a service system for storing Internet information. For example, the system server includes server A and server B for storing web pages. This application provides a method for judging the access information output by the client. And the method of URL request whether it has the authority to access server A or server B.

Specifically, the S1 includes the following steps:

S11: Create a running framework and set framework rules in the running framework;

It should be noted that the operating framework is the Spring security framework; Spring is an open-source design-level framework that is used to solve the problem of loose coupling between the business logic layer and other layers, so it will interface-oriented programming ideas throughout the entire system applications. Spring is a lightweight Java development framework.

S12: Create an authentication node with the framework rules based on the operating framework;

In this step, the framework rules are rules for obtaining permission results by performing operations on the access information and URL requests, and for storing permission information in the running framework, which can be written in JAVA language or C language.

S13: Create an authority database in the authentication node;

In this step, the authority database includes first-level data, second-level data, and third-level data;

The first-level data includes a first-level information set and a first-level access set, the first-level information set has at least one registration information, and the first-level access set has at least one standard resource address of a system server;

The second-level data includes a second-level information set and a second-level access set, the second-level information set has at least one registration information, and the second-level access set has at least one standard resource address of a system server;

The three-level data includes a three-level access set, and the three-level access set has at least one standard resource address of a system server.

S14: Generate a creation success signal according to the creation authority database and output it to the client;

In this step, the creation success signal can be displayed on the client in the form of a dialog box.

Specifically, the S2 includes the following steps:

S21: Receive, through the authentication node, the login information output by the client according to the creation success signal;

S22: Compare the login information with the first-level information set and the second-level information set in sequence, and generate authority information;

Wherein, the authority information includes role information and role authority;

Specifically, if the login information is consistent with certain registration information in the first-level information set, the generated role information is the login information, and the role authority is the authority information of the first-level access set;

If the login information is consistent with certain registration information in the secondary information set, the generated role information is the login information, and the role authority is the authority information of the secondary access set;

If the login information is inconsistent with all registration information in the first-level information set and the second-level information set, the generated role information is the login information, and the role authority is the authority information of the third-level access set;

S23: Output the authority information to the running framework through the authentication node;

It should be noted that the login information includes a login account, a login password, and a login device IMEI code. Among them, IMEI (International The Mobile Equipment Identity, commonly known as "mobile phone serial number", is stored in the EEPROM (commonly known as chip) of the mobile phone. Each mobile device has a unique IMEI. In this embodiment, the login device IMEI code Is the IMEI code of the client.

Specifically, the S3 includes the following steps:

S31: Store the authority information in the operating framework through the authentication node;

S32: Generate a cache success signal through the authentication node, and output the cache success signal to the client.

Specifically, the S4 includes the following steps:

S41: Receive, through the authentication node, the URL request and access information output by the client according to the cache success signal;

In this step, the URL (Uniform Resource Locator) request is a concise representation of the location and access method of resources available on the Internet, and is the address of a standard resource on the Internet; in this embodiment, the URL request is The address of the standard resource used to obtain information from the system server;

The access information includes the IMEI code of the login device, that is, the IEMI code of the client.

S42: Use the framework rules to compare the access information with the role information of the permission information in the running framework through the authentication node to obtain permission information that matches the access information;

In this embodiment, the access information is compared with the role information in the running framework. The access information includes the IEMI code of the login device, and the role information includes the login account, the login password, and the IMEI code of the login device. The IMEI code of the login device in the role information determines that the access information matches the authority information corresponding to the role information. In a specific application scenario, the above scheme can be used to determine whether the client sending the access information and URL request is in the logged-in state. ；

Extract the role permissions of the permission information matching the access information, use the framework rules to compare the URL request with the standard resource address in the role permissions, and generate the permission result; in this embodiment, the URL request Compare with the standard resource address in the role authority of the authority information, because the content of the URL request includes the requested resource address for requesting information, therefore, if the requested resource address is consistent with a certain standard resource address, the URL request is determined With or without the right to access the standard resource address, in a specific scenario, the above scheme can be used to determine whether the client sending the access information and URL request has the right to access the resource address requested in the URL request.

S43: Load the authority result into the URL request through the authentication node to form a new URL request;

In this step, because the authorization result is loaded into the URL request, when a large amount of access information and URL requests are received, the authentication node will only perform step S5 on the URL request with the authorization result, and execute the URL request for the URL without the authorization result. Step S42 realizes the shunting of the access information and the URL request, and avoids the confusion of the URL request and the permission result caused by the input of a large amount of access information and the URL request. Further, the framework rules in S4 may be admission rules, or may be exclusion rules.

In the S4, using the access rules to calculate the access information and the URL request to obtain the permission result includes the following steps:

S4-01: sequentially compare the access information with the role information of the permission information stored in the running framework, and obtain the permission information having the role information consistent with the access information;

If the access information is inconsistent with the role information of all permission information stored in the running framework, the generated content is an unauthorized permission result, and the permission result is loaded into the URL request;

S4-02: Extract the role authority of the authority information, and sequentially compare the URL request with the standard resource address of the system server in the role authority;

S4-03: If the role authority has the standard resource address of the system server consistent with the URL request, the generated content is the authority result of the authority, and the authority result is loaded into the URL request to form a new URL request;

If the role authority does not have the standard resource address of the system server consistent with the URL request, the generated content is an unauthorized authority result, and the authority result is loaded into the URL request to form a new URL request.

In S4-03, a permission result whose content is right or not is generated by way of JAVA object assignment, and the permission result is loaded into the corresponding URL request.

In the S4, using the exclusion rule to calculate the access information and the URL request to obtain the authority result includes the following steps:

S4-11: The access information is sequentially compared with the role information of the permission information stored in the running framework to obtain the permission information having the role information consistent with the access information;

If the access information is inconsistent with the role information of all permission information stored in the running framework, the generated content is an unauthorized permission result, and the permission result is loaded into the URL request;

S4-12: Extract the role authority of the authority information, and sequentially compare the URL request with the standard resource address of the system server in the role authority;

S4-13: If the role authority has the standard resource address of the system server consistent with the URL request, the generated content is an unauthorized authority result, and the authority result is loaded into the URL request to form a new URL request;

If the role authority does not have the standard resource address of the system server consistent with the URL request, the generated content is the authority result of the authority, and the authority result is loaded into the URL request to form a new URL request;

In S4-13, a permission result whose content is right or not is generated by way of JAVA object assignment, and the permission result is loaded into the corresponding URL request.

Specifically, the S5 includes the following steps:

S51: Extract the authority result in the new URL request through the authentication node, and determine the content of the authority result;

S52: If the authorization result is authorization, access the system server specified by the URL request, and obtain system information of the system server;

If the permission result is no permission, a failure prompt box is generated;

S52: Output the system information or failure prompt box to the client through the authentication node.

Example two

Please refer to FIG. 2. An authentication device 1 of this embodiment includes:

The creation module 11 is used to create an authentication node with framework rules based on a preset operating framework, the authentication node includes a permission database, and generates and outputs it to the client;

The authority management module 12 is configured to receive the login information sent by the client through the authentication node, and obtain the authority information matching the login information in the authority database;

The cache module 13 is configured to store the authority information according to the framework rules through the authentication node, generate a cache success signal, and send it to the client;

The request judgment module 14 is configured to receive the access information and URL request sent by the client through the authentication node, and compare the access information and URL request with the authority information in the authentication node by using the framework rules. Obtain the permission result, and load the permission result into the URL request to obtain a new URL request;

The feedback module 15 is configured to obtain system information according to the new URL request through the authentication node, or generate a failure prompt box; and output the system information or failure prompt box to the client.

This technical solution is based on the cloud security field of cloud technology, creates a permission database and creates an operating framework through a creation module, obtains permission information matching the login information through the permission management module, and stores the permission information through the cache module; The request judgment module calculates the login information to obtain the authorization result, and loads the authorization result into the URL request; finally, the feedback module accesses the system server according to the authorization result and obtains system information, or generates a failure prompt box ; Then output the system information or failure prompt box to the client; realize the technical effect of ensuring the security of the virtual layer based on virtualized user authentication.

Example three

In order to achieve the above objective, the present application also provides a computer system that includes a plurality of computer devices 2. The components of the authentication device 1 of the second embodiment can be dispersed in different computer devices, and the computer devices can execute programs. Smartphones, tablet computers, notebook computers, desktop computers, rack servers, blade servers, tower servers or cabinet servers (including independent servers, or server clusters composed of multiple servers), etc. The computer equipment of this embodiment at least includes but is not limited to: a memory 21 and a processor 22 that can be communicatively connected to each other through a system bus, as shown in FIG. 3. It should be pointed out that FIG. 3 only shows a computer device with components, but it should be understood that it is not required to implement all the illustrated components, and more or fewer components may be implemented instead.

In this embodiment, the memory 21 (ie, readable storage medium) includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), Read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disks, optical disks, etc. In some embodiments, the memory 21 may be an internal storage unit of a computer device, such as a hard disk or memory of the computer device. In other embodiments, the memory 21 may also be an external storage device of the computer device, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), and a secure digital (Secure Digital, SD) equipped on the computer device. Flash card Card) and so on. Of course, the memory 21 may also include both the internal storage unit of the computer device and its external storage device. In this embodiment, the memory 21 is generally used to store an operating system and various application software installed in a computer device, such as the program code of the authentication device in the first embodiment. In addition, the memory 21 can also be used to temporarily store various types of data that have been output or will be output.

In some embodiments, the processor 22 may be a central processing unit (Central Processing Unit, CPU), a controller, a microcontroller, a microprocessor, or other data processing chips. The processor 22 is generally used to control the overall operation of the computer equipment. In this embodiment, the processor 22 is used to run the program code or process data stored in the memory 21, for example, to run an authentication device, so as to implement the authentication method of the first embodiment.

Example four

To achieve the above objective, this application also provides a computer-readable storage system. The computer-readable storage medium may be non-volatile or volatile, and includes multiple storage media, such as flash memory, hard disk, and multimedia. Card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), Programmable read-only memory (PROM), magnetic memory, magnetic disks, optical disks, servers, App application malls, etc., have computer programs stored thereon, and corresponding functions are realized when the programs are executed by the processor 22. The computer-readable storage medium of this embodiment is used to store an authentication device, and when executed by the processor 22, the authentication method of the first embodiment is implemented.

The serial numbers of the foregoing embodiments of the present application are only for description, and do not represent the superiority of the embodiments.

Through the description of the above implementation manners, those skilled in the art can clearly understand that the above-mentioned embodiment method can be implemented by means of software plus the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is better.的实施方式。

The above are only the preferred embodiments of the application, and do not limit the scope of the patent for this application. Any equivalent structure or equivalent process transformation made using the content of the description and drawings of the application, or directly or indirectly applied to other related technical fields , The same reason is included in the scope of patent protection of this application.

Claims (20)

An authentication method, which includes the following steps: S1: Create an authentication node with framework rules based on a preset operating framework, the authentication node includes a permission database, and generates a creation success signal and outputs it to the client; S2: receiving the login information sent by the client through the authentication node, and obtaining permission information matching the login information in the permission database; S3: Store the authority information according to the framework rules through the authentication node, generate a cache success signal, and send it to the client; S4: Receive the access information and URL request sent by the client through the authentication node, and use the framework rules to compare the access information and URL request with the authority information in the authentication node to obtain authority results , And load the authority result into the URL request to obtain a new URL request; S5: Obtain system information according to the new URL request through the authentication node, or generate a failure prompt box; output the system information or the failure prompt box to the client. The authentication method according to claim 1, wherein said S1 comprises the following steps: S11: Create a running framework and set framework rules in the running framework; S12: Create an authentication node with the framework rules based on the operating framework; S13: Create an authority database in the authentication node; S14: Generate a creation success signal according to the creation authority database and output it to the client. The authentication method according to claim 2, wherein the authority database in S11 includes first-level data, second-level data, and third-level data; The first-level data includes a first-level information set and a first-level access set, the first-level information set has at least one registration information, and the first-level access set has at least one standard resource address of a system server; The second-level data includes a second-level information set and a second-level access set, the second-level information set has at least one registration information, and the second-level access set has at least one standard resource address of a system server; The three-level data includes a three-level access set, and the three-level access set has at least one standard resource address of a system server. The authentication method according to claim 3, wherein the S2 includes the following steps: S21: Receive, through the authentication node, the login information output by the client according to the creation success signal; S22: The login information is sequentially compared with the first-level information set and the second-level information set, and authority information is generated; wherein the authority information includes role information and role authority; S23: Output the authority information to the running framework. The authentication method according to claim 4, wherein, in the S22 includes: If the login information is consistent with certain registration information in the first-level information set, the generated role information is the login information, and the role authority is the authority information of the first-level access set; If the login information is consistent with certain registration information in the secondary information set, the generated role information is the login information, and the role authority is the authority information of the secondary access set; If the login information is inconsistent with all registration information in the first-level information set and the second-level information set, the generated role information is the login information, and the role authority is the authority information of the third-level access set. The authentication method according to claim 5, wherein the framework rule in S4 may be an access rule; in S4, using the access rule to calculate the access information and URL request to obtain the authority result, it comprises the following steps : S4-01: sequentially compare the access information with the role information of the permission information stored in the running framework, and obtain the permission information having the role information consistent with the access information; If the access information is inconsistent with the role information of all permission information stored in the running framework, the generated content is an unauthorized permission result, and the permission result is loaded into the URL request; S4-02: Extract the role authority of the authority information, and sequentially compare the URL request with the standard resource address of the system server in the role authority; S4-03: If the role authority has the standard resource address of the system server consistent with the URL request, the generated content is the authority result of the authority, and the authority result is loaded into the URL request; If the role authority does not have the standard resource address of the system server consistent with the URL request, the generated content is an unauthorized authority result, and the authority result is loaded into the URL request. The authentication method according to claim 5, wherein the frame rule in S4 may also be an exclusion rule; the use of exclusion rule in S4 to calculate the access information and URL request to obtain the authority result includes the following steps: S4-11: The access information is sequentially compared with the role information of the permission information stored in the running framework to obtain the permission information having the role information consistent with the access information; If the access information is inconsistent with the role information of all permission information stored in the running framework, the generated content is an unauthorized permission result, and the permission result is loaded into the URL request; S4-12: Extract the role authority of the authority information, and sequentially compare the URL request with the standard resource address of the system server in the role authority; S4-13: If the role authority has a standard resource address of the system server consistent with the URL request, the generated content is an unauthorized authority result, and the authority result is loaded into the URL request; If the role authority does not have the standard resource address of the system server consistent with the URL request, the generated content is the authority result of the authority, and the authority result is loaded into the URL request. An authentication device, which includes: The creation module is used to create an authentication node with framework rules based on a preset operating framework, the authentication node includes a permission database, and generates and outputs it to the client; The authority management module is configured to receive the login information sent by the client through the authentication node, and obtain the authority information matching the login information in the authority database; A cache module, configured to store the authority information according to the framework rules through the authentication node, generate a cache success signal, and send it to the client; The request judgment module is configured to receive the access information and URL request sent by the client through the authentication node, and use the framework rules to compare the access information and URL request with the authority information in the authentication node. To obtain the authority result, and load the authority result into the URL request to obtain a new URL request; The feedback module is configured to obtain system information according to the new URL request through the authentication node, or generate a failure prompt box; and output the system information or failure prompt box to the client. A computer system includes multiple computer devices, each computer device includes a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processors of the multiple computer devices execute a The authentication method, wherein the authentication method includes the following steps: S1: Create an authentication node with framework rules based on a preset operating framework, the authentication node includes a permission database, and generates a creation success signal and outputs it to the client; S2: receiving the login information sent by the client through the authentication node, and obtaining permission information matching the login information in the permission database; S3: Store the authority information according to the framework rules through the authentication node, generate a cache success signal, and send it to the client; S4: Receive the access information and URL request sent by the client through the authentication node, and use the framework rules to compare the access information and URL request with the authority information in the authentication node to obtain authority results , And load the authority result into the URL request to obtain a new URL request; S5: Obtain system information according to the new URL request through the authentication node, or generate a failure prompt box; output the system information or the failure prompt box to the client. The computer system according to claim 9, wherein said S1 comprises the following steps: S11: Create a running framework and set framework rules in the running framework; S12: Create an authentication node with the framework rules based on the operating framework; S13: Create an authority database in the authentication node; S14: Generate a creation success signal according to the creation authority database and output it to the client. The computer system according to claim 10, wherein the authority database in S11 includes first-level data, second-level data, and third-level data; The first-level data includes a first-level information set and a first-level access set, the first-level information set has at least one registration information, and the first-level access set has at least one standard resource address of a system server; The second-level data includes a second-level information set and a second-level access set, the second-level information set has at least one registration information, and the second-level access set has at least one standard resource address of a system server; The three-level data includes a three-level access set, and the three-level access set has at least one standard resource location of a system server; The S2 includes the following steps: S21: Receive, through the authentication node, the login information output by the client according to the creation success signal; S22: The login information is sequentially compared with the first-level information set and the second-level information set, and authority information is generated; wherein the authority information includes role information and role authority; S23: Output the authority information to the running framework. The computer system according to claim 11, wherein, in the S22 includes: If the login information is consistent with certain registration information in the first-level information set, the generated role information is the login information, and the role authority is the authority information of the first-level access set; If the login information is consistent with certain registration information in the secondary information set, the generated role information is the login information, and the role authority is the authority information of the secondary access set; If the login information is inconsistent with all registration information in the first-level information set and the second-level information set, the generated role information is the login information, and the role authority is the authority information of the third-level access set. The computer system according to claim 12, wherein the framework rule in S4 may be an access rule; in S4, using the access rule to calculate the access information and URL request to obtain a permission result includes the following steps : S4-01: sequentially compare the access information with the role information of the permission information stored in the running framework, and obtain the permission information having the role information consistent with the access information; If the access information is inconsistent with the role information of all permission information stored in the running framework, the generated content is an unauthorized permission result, and the permission result is loaded into the URL request; S4-02: Extract the role authority of the authority information, and sequentially compare the URL request with the standard resource address of the system server in the role authority; S4-03: If the role authority has the standard resource address of the system server consistent with the URL request, the generated content is the authority result of the authority, and the authority result is loaded into the URL request; If the role authority does not have the standard resource address of the system server consistent with the URL request, the generated content is an unauthorized authority result, and the authority result is loaded into the URL request. The computer system according to claim 12, wherein the frame rule in S4 may also be an exclusion rule; and the use of exclusion rules in S4 to calculate the access information and URL request to obtain a permission result includes the following steps: S4-11: The access information is sequentially compared with the role information of the permission information stored in the running framework to obtain the permission information having the role information consistent with the access information; If the access information is inconsistent with the role information of all permission information stored in the running framework, the generated content is an unauthorized permission result, and the permission result is loaded into the URL request; S4-12: Extract the role authority of the authority information, and sequentially compare the URL request with the standard resource address of the system server in the role authority; S4-13: If the role authority has a standard resource address of the system server consistent with the URL request, the generated content is an unauthorized authority result, and the authority result is loaded into the URL request; If the role authority does not have the standard resource address of the system server consistent with the URL request, the generated content is the authority result of the authority, and the authority result is loaded into the URL request. A computer-readable storage medium includes multiple storage media, and each storage medium stores a computer program, wherein the computer program stored in the multiple storage media implements an authentication method when executed by a processor, wherein , The authentication method includes the following steps: S1: Create an authentication node with framework rules based on a preset operating framework, the authentication node includes a permission database, and generates a creation success signal and outputs it to the client; S2: receiving the login information sent by the client through the authentication node, and obtaining permission information matching the login information in the permission database; S3: Store the authority information according to the framework rules through the authentication node, generate a cache success signal, and send it to the client; S4: Receive the access information and URL request sent by the client through the authentication node, and use the framework rules to compare the access information and URL request with the authority information in the authentication node to obtain authority results , And load the authority result into the URL request to obtain a new URL request; S5: Obtain system information according to the new URL request through the authentication node, or generate a failure prompt box; output the system information or the failure prompt box to the client. The computer-readable storage medium according to claim 15, wherein said S1 comprises the following steps: S11: Create a running framework and set framework rules in the running framework; S12: Create an authentication node with the framework rules based on the operating framework; S13: Create an authority database in the authentication node; S14: Generate a creation success signal according to the creation authority database and output it to the client. The computer-readable storage medium according to claim 16, wherein the authority database in S11 includes first-level data, second-level data, and third-level data; The first-level data includes a first-level information set and a first-level access set, the first-level information set has at least one registration information, and the first-level access set has at least one standard resource address of a system server; The second-level data includes a second-level information set and a second-level access set, the second-level information set has at least one registration information, and the second-level access set has at least one standard resource address of a system server; The three-level data includes a three-level access set, and the three-level access set has at least one standard resource address of a system server; The S2 includes the following steps: S21: Receive, through the authentication node, the login information output by the client according to the creation success signal; S22: The login information is sequentially compared with the first-level information set and the second-level information set, and authority information is generated; wherein the authority information includes role information and role authority; S23: Output the authority information to the running framework. The computer-readable storage medium according to claim 17, wherein, in the S22 includes: If the login information is consistent with certain registration information in the first-level information set, the generated role information is the login information, and the role authority is the authority information of the first-level access set; If the login information is consistent with certain registration information in the secondary information set, the generated role information is the login information, and the role authority is the authority information of the secondary access set; If the login information is inconsistent with all registration information in the first-level information set and the second-level information set, the generated role information is the login information, and the role authority is the authority information of the third-level access set. 18. The computer-readable storage medium according to claim 18, wherein the framework rules in S4 may be admission rules; in S4, admission rules are used to perform operations on the access information and URL requests to obtain permission results, It includes the following steps: S4-01: sequentially compare the access information with the role information of the permission information stored in the running framework, and obtain the permission information having the role information consistent with the access information; If the access information is inconsistent with the role information of all permission information stored in the running framework, the generated content is an unauthorized permission result, and the permission result is loaded into the URL request; S4-02: Extract the role authority of the authority information, and sequentially compare the URL request with the standard resource address of the system server in the role authority; S4-03: If the role authority has the standard resource address of the system server consistent with the URL request, the generated content is the authority result of the authority, and the authority result is loaded into the URL request; If the role authority does not have the standard resource address of the system server consistent with the URL request, the generated content is an unauthorized authority result, and the authority result is loaded into the URL request. The computer-readable storage medium according to claim 18, wherein the frame rule in S4 may also be an exclusion rule; in S4, the exclusion rule is used to calculate the access information and URL request to obtain the authority result, including The following steps: S4-11: The access information is sequentially compared with the role information of the permission information stored in the running framework to obtain the permission information having the role information consistent with the access information; If the access information is inconsistent with the role information of all permission information stored in the running framework, the generated content is an unauthorized permission result, and the permission result is loaded into the URL request; S4-12: Extract the role authority of the authority information, and sequentially compare the URL request with the standard resource address of the system server in the role authority; S4-13: If the role authority has a standard resource address of the system server consistent with the URL request, the generated content is an unauthorized authority result, and the authority result is loaded into the URL request; If the role authority does not have the standard resource address of the system server consistent with the URL request, the generated content is the authority result of the authority, and the authority result is loaded into the URL request.