CN115174142A - Gateway unified authentication management method, device, storage medium and computer - Google Patents

Gateway unified authentication management method, device, storage medium and computer Download PDF

Info

Publication number
CN115174142A
CN115174142A CN202210590954.7A CN202210590954A CN115174142A CN 115174142 A CN115174142 A CN 115174142A CN 202210590954 A CN202210590954 A CN 202210590954A CN 115174142 A CN115174142 A CN 115174142A
Authority
CN
China
Prior art keywords
parameter
request message
client
gateway
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202210590954.7A
Other languages
Chinese (zh)
Other versions
CN115174142B (en
Inventor
刘皓榛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Sekorm Component Network Co Ltd
Original Assignee
Shenzhen Sekorm Component Network Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Sekorm Component Network Co Ltd filed Critical Shenzhen Sekorm Component Network Co Ltd
Priority to CN202210590954.7A priority Critical patent/CN115174142B/en
Publication of CN115174142A publication Critical patent/CN115174142A/en
Application granted granted Critical
Publication of CN115174142B publication Critical patent/CN115174142B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/66Arrangements for connecting between networks having differing types of switching systems, e.g. gateways

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention relates to a gateway unified authentication management method, a gateway unified authentication management device, a storage medium and a computer. The method comprises the following steps: s1, receiving a first request message sent by a client; s2, judging whether the credential is correct or not; s3, if yes, generating a first parameter and returning the first parameter to the client; s4, receiving a second request message sent by the client; s5, judging whether the first parameter in the second request message is correct or not; s6, if yes, judging whether the analysis parameters are correct or not; s7, if so, inserting a second parameter into the second request message, wherein the second request message with the second parameter inserted is a third request message; s8, sending the third request message to a server; and S9, returning the response of the server to the client. The invention realizes the uniformity of code specification, greatly reduces development and maintenance cost, and effectively improves the security of the authentication mode without exposing to the outside.

Description

Gateway unified authentication management method, device, storage medium and computer
Technical Field
The present invention relates to the field of gateway authentication, and more particularly, to a unified gateway authentication management method, device, storage medium, and computer.
Background
Various calling irregularities exist among services provided by traditional multiple service parties. Due to the fact that code specifications of various companies and used programming languages are inconsistent, a plurality of sets of different codes are developed due to the authority authentication problem of service calling between different service terminals and client terminals, accordingly, the docking workload of developers is increased, meanwhile, the various authentication styles are not uniform, the management cost and the maintenance cost are increased, and the problem that the authentication mode is exposed to the outside is also caused.
Disclosure of Invention
The invention aims to provide a gateway unified authentication management method, a gateway unified authentication management device, a storage medium and a computer.
The technical scheme adopted by the invention for solving the technical problems is as follows: a gateway unified authentication management method is constructed, and comprises the following steps:
the method comprises the following steps that S1, a first request message sent by a client is received, wherein the first request message contains a certificate, and the certificate is confirmed and obtained according to agreement of both parties before the client accesses a gateway for the first time;
s2, judging whether the credential is correct or not;
s3, if yes, generating a first parameter and returning the first parameter to the client;
step S4, receiving a second request message sent by the client, wherein the second request message contains the first parameter, an analytic parameter and a service end rule, and the analytic parameter and the service end rule are confirmed and obtained according to agreement of both parties before the client accesses the gateway for the first time;
s5, judging whether the first parameter in the second request message is correct or not;
s6, if yes, judging whether the analysis parameters are correct or not;
s7, if so, inserting a second parameter into the second request message, wherein the second parameter corresponds to the rule of the server, and the second request message into which the second parameter is inserted is a third request message;
s8, sending the third request message to the server;
and S9, returning the response of the server to the client.
Further, in the method for managing unified gateway authentication according to the present invention, the step S3 of generating the first parameter and returning the first parameter to the client includes the steps of:
step S31, after the first parameter is generated, the first parameter is returned to the client, and the client adds the first parameter to the first request message, wherein the first request message after the first parameter is added is a second request message.
Further, in the method for managing unified gateway authentication according to the present invention, the step S3 of generating the first parameter and returning the first parameter to the client includes the steps of:
step S32, after the first parameter is generated, the first parameter is returned to the client, the client adds the first parameter to the first request message and stores the first parameter in the database, and when the client requests again, the first parameter in the database is added to the first request message, wherein the first request message after the first parameter is added is a second request message.
Further, in the method for managing unified gateway authentication of the present invention, in step S4, the parsing parameter corresponds to a server rule, and each server corresponds to one server rule. Further, in the method for managing unified gateway authentication according to the present invention, after the step S2 and before the step S4, the method further includes the steps of:
and S21, if the credentials are incorrect, returning error information of authentication failure to the client.
Further, in the method for managing unified gateway authentication according to the present invention, after the step S5 and before the step S6, the method further includes the steps of:
step S51, if the first parameter in the second request message is incorrect, returning error information to the client.
Further, in the method for managing unified gateway authentication according to the present invention, after the step S6 and before the step S8, the method further includes the steps of:
and S62, if the analysis parameters are incorrect, returning error information to the client.
In addition, the invention also provides a gateway unified authentication management method and device, comprising the following steps:
the first receiving unit is used for receiving a first request message sent by a client, wherein the first request message contains a credential, and the credential is determined and obtained according to agreement of both parties before the client accesses a gateway for the first time;
the first judging unit is used for judging whether the credential is correct or not;
the first feedback unit is used for generating a first parameter and returning the first parameter to the client when the credential is correct;
a second receiving unit, configured to receive a second request packet sent by the client, where the second request packet includes the first parameter, an analysis parameter, and a server rule, and the analysis parameter and the server rule are obtained by confirming according to a contract between the client and the server before the client accesses the gateway for the first time;
a second determining unit, configured to determine whether the first parameter in the second request message is correct;
a third determining unit, configured to determine whether the parsing parameter is correct when the first parameter in the second request message is correct;
a second feedback unit, configured to insert a second parameter into the second request packet if the analysis parameter is correct, where the second parameter corresponds to a rule of the server, and the second request packet into which the second parameter is inserted is a third request packet;
a sending unit, configured to forward the third request packet to the server;
and the return unit is used for returning the response of the server to the client.
In addition, the present invention also provides a computer readable storage medium, which stores a computer program, where the computer program is suitable for being loaded by a processor to execute the steps of the gateway unified authentication management method.
In addition, the invention also provides a computer, which comprises a memory and a processor, wherein the memory is stored with a computer program, and the processor executes the steps of the gateway unified authentication management method by calling the computer program stored in the memory.
The gateway unified authentication management method, the device, the storage medium and the computer have the following beneficial effects that: the invention carries out uniform request entry management, unifies and protects the authentication modes between each server and the client, achieves the uniformity of code specification, greatly reduces the development cost and the maintenance cost of developers of different service parties, and effectively improves the security of the authentication modes without exposing to the outside.
Drawings
The invention will be further described with reference to the accompanying drawings and examples, in which:
fig. 1 is a flowchart of a gateway unified authentication management method according to an embodiment of the present invention;
fig. 2 is a flowchart of a gateway unified authentication management method according to an embodiment of the present invention;
fig. 3 is a flowchart of a gateway unified authentication management method according to an embodiment of the present invention.
Detailed Description
For a more clear understanding of the technical features, objects, and effects of the present invention, embodiments of the present invention will now be described in detail with reference to the accompanying drawings.
In a preferred embodiment, referring to fig. 1, the gateway unified authentication management method of this embodiment includes the steps of:
the method comprises the following steps of S1, receiving a first request message sent by a client, wherein the first request message contains a certificate, and the certificate is confirmed and obtained according to agreement of both sides before the client accesses a gateway for the first time.
Specifically, when the client accesses the gateway for the first time, the client requests the gateway for the credentials, the resolution parameters and the service end rules, and the gateway and the client confirm the credentials, the resolution parameters and the service end rules according to the agreement, the client stores the credentials, the resolution parameters and the service end rules in the database. The gateway stores the server side rule corresponding to the server side before the client requests the evidence, the analysis parameter and the server side rule. When the client needs to send the first request message to the gateway, the client puts the evidence, the analysis parameters and the service end rules into the first request message, and then sends the first request message with the evidence, the analysis parameters and the service end rules put into the first request message to the gateway.
And S2, judging whether the credential is correct or not.
Specifically, after receiving the first request message, the gateway extracts the credential in the first request message, and then determines whether the extracted credential is correct, and the process of determining the correct credential may refer to the existing framework determination process.
And S3, if so, generating a first parameter and returning the first parameter to the client.
Specifically, if the credential in the first request message is correct, the gateway generates a first parameter and returns the first parameter to the client, each first parameter has timeliness, and if the gateway detects that the first parameter is overdimensional, it is determined that the first parameter is wrong.
Further, referring to fig. 2, after receiving the first parameter returned by the gateway, the client adds the first parameter to the first request message without storing the first parameter, where the first request message after adding the first parameter is a second request message, and this method enables the first parameter obtained by the client each time to be valid and not outdated.
Alternatively, referring to fig. 3, after receiving the first parameter returned by the gateway, the client stores the first parameter into the database, where the database may be a relational database or a non-relational database, and at this time, within the timeliness of the first parameter, the client may directly obtain the first parameter from the database, and then add the first parameter into the first request message as the second request message to be sent to the gateway. In order to prevent the timeliness of the first parameter stored in the relational database or the non-relational database, the client may obtain the first parameter from the gateway after a preset time, which may ensure that the first parameter stored in the relational database or the non-relational database is always valid. In this way, when the client needs to request the gateway, the workload and the corresponding time can be reduced by reducing the number of requests.
And S4, receiving a second request message sent by the client, wherein the second request message contains the first parameter, the analytic parameter and the service end rule, and the analytic parameter and the service end rule are confirmed and obtained according to agreement of both parties before the client accesses the gateway for the first time.
Specifically, the client uses the first request message added with the first parameter as a second request message, and at this time, the second request message includes the first parameter, the analysis parameter and the service end rule, and the client sends the second request message to the gateway.
And S5, judging whether the first parameter in the second request message is correct or not.
Specifically, after receiving the second request message, the gateway extracts the first parameter in the second request message, and determines whether the first parameter in the second request message is correct, and the process of determining the correctness can refer to the existing framework determination process.
And S6, if so, judging whether the analysis parameters are correct.
Specifically, if the first parameter in the second request message is correct, the gateway extracts the analysis parameter in the second request message, determines whether the analysis parameter in the second request message is correct, and refers to the existing framework determination process in the process of determining the correctness, wherein the analysis parameter corresponds to the service end rule, and the analysis parameter may include a plurality of parameters.
And S7, if so, inserting a second parameter into the second request message, wherein the second parameter corresponds to the rule of the server, and the second request message into which the second parameter is inserted is a third request message.
Specifically, if the analysis parameter in the second request message is correct, the self-programming plug-in of the gateway adds a second parameter in the second request message according to the server rule, where the second parameter may be multiple parameters, and the second request message into which the second parameter is inserted is used as a third request message.
And S8, sending the third request message to the server.
And S9, returning the response of the server to the client.
Specifically, the gateway sends the third request message to the server, and sends the content responded by the server according to the third request message to the client.
The gateway unified authentication management method in this embodiment uniformly manages the request entries, and uniformly protects the authentication modes between the servers and the clients, so that the code specification is uniform, the development cost and the maintenance cost of developers of different servers are greatly reduced, and the security that the authentication modes are not exposed to the outside is effectively improved.
In a preferred real-time embodiment, in the gateway unified authentication management method of the present invention, the parsing parameter corresponds to the server rule in step S4, and each server corresponds to a server rule.
Specifically, when the client accesses the gateway for the first time, the client asks for the credential, the analysis parameter and the service end rule from the gateway, and the gateway returns the credential, the analysis parameter and the service end rule to the client. The analysis parameters correspond to corresponding server rules, and when a plurality of servers exist, each server corresponds to one server rule.
In the embodiment, the situation that the gateway can process a plurality of request messages in the authentication process and different service ends requested by different request messages exist is considered, and because the service ends of different service ends have different rules, the gateway unified authentication management method can be implemented to unify the authentication modes between each service end and the client end for protection, so that the code specification uniformity is realized, the development cost and the maintenance cost of developers of different service parties are greatly reduced, and the security of the authentication modes without exposure to the outside is effectively improved.
In a preferred real-time embodiment, the gateway unified authentication management method of the present invention further includes, after step S2 and before step S4, the steps of:
and step S21, if the credential is incorrect, returning error information of authentication failure to the client.
Specifically, if the credential extracted from the first request message by the gateway is determined to be an error, an error message indicating that the authentication failed is returned to the client. Therefore, the user can be reminded of errors in the authentication process and timely carry out the following coping operation.
In a preferred real-time embodiment, the gateway unified authentication management method of the present invention further includes, after step S5 and before step S6, the steps of:
and S51, if the first parameter in the second request message is incorrect, returning error information to the client.
Specifically, if the first parameter extracted from the second request message by the gateway is determined to be an error, an error message indicating authentication failure is returned to the client. Therefore, the user can be reminded of errors in the authentication process and timely carry out the following coping operation.
In a preferred real-time embodiment, the gateway unified authentication management method of the present invention further includes, after step S6 and before step S8, the steps of:
and S62, if the analysis parameters are incorrect, returning error information to the client.
Specifically, if the analysis parameter extracted from the second request message by the gateway is determined to be an error, an error message indicating authentication failure is returned to the client. Therefore, the user can be reminded of errors in the authentication process, and the next coping operation can be carried out in time.
In addition, the invention also provides a gateway unified authentication management method and device, comprising the following steps:
the first receiving unit is used for receiving a first request message sent by the client, wherein the first request message contains a credential, and the credential is determined and obtained according to agreement of both sides before the client accesses the gateway for the first time.
Specifically, when the client accesses the gateway for the first time, the client requests the gateway for the credentials, the resolution parameters, and the service end rules, and the gateway and the client confirm the credentials, the resolution parameters, and the service end rules according to the agreement, the client stores the credentials, the resolution parameters, and the service end rules in the database. When the client needs to send the first request message to the gateway, the client puts the evidence, the analysis parameters and the service end rules into the first request message, and then sends the first request message with the evidence, the analysis parameters and the service end rules put into the first request message to the gateway.
The first judging unit is used for judging whether the credential is the same as the existing credential in the gateway.
Specifically, after receiving the first request message, the gateway extracts the credential in the first request message, and then determines whether the extracted credential is correct, and the process of determining the correct credential may refer to the existing framework determination process.
And the first feedback unit is used for generating a first parameter and returning the first parameter to the client when the credential is the same as the credential existing in the gateway, and storing the first parameter in the gateway.
Specifically, if the credential in the first request message is correct, the gateway generates a first parameter and returns the first parameter to the client, each first parameter has timeliness, and if the gateway detects that the first parameter is overdimensional, it is determined that the first parameter is wrong.
Further, after the client receives the first parameter returned by the gateway, the first parameter is added into the first request message, the first parameter does not need to be stored, wherein the first request message after the first parameter is added is the second request message.
Optionally, after receiving the first parameter returned by the gateway, the client stores the first parameter into the database, where the database may be a relational database or a non-relational database, and at this time, within the timeliness of the first parameter, the client may directly obtain the first parameter from the database, and then add the first parameter into the first request message as the second request message to be sent to the gateway. In order to prevent the timeliness of the first parameter stored in the relational database or the non-relational database, the client may obtain the first parameter from the gateway after a preset time, so as to ensure that the first parameter stored in the relational database or the non-relational database is always valid. In this way, when the client needs to request the gateway, the workload and the corresponding time can be reduced by reducing the number of requests.
And the second receiving unit is used for receiving a second request message sent by the client, wherein the second request message contains the first parameter, the analytic parameter and the service end rule, and the analytic parameter and the service end rule are confirmed and obtained according to agreement of both parties before the client accesses the gateway for the first time.
Specifically, the client uses the first request message added with the first parameter as a second request message, and the second request message includes the first parameter, the analysis parameter and the service end rule, and the client sends the second request message to the gateway.
And the second judging unit is used for judging whether the first parameter in the second request message is the same as the first parameter stored in the gateway or not.
Specifically, after receiving the second request message, the gateway extracts the first parameter in the second request message, and determines whether the first parameter in the second request message is correct, and the process of determining the correctness can refer to the existing framework determination process.
And the third judging unit is used for judging whether the analysis parameters are the same as the existing analysis parameters in the gateway or not when the first parameters in the second request message are the same as the first parameters stored in the gateway.
Specifically, if the first parameter in the second request message is correct, the gateway extracts the parsing parameter in the second request message, determines whether the parsing parameter in the second request message is correct, and refers to the existing framework determination process for determining the correct process, where the parsing parameter may include multiple parameters.
And the second feedback unit is used for inserting a second parameter into the second request message if the analysis parameter is the same as the existing analysis parameter in the gateway, wherein the second parameter corresponds to the rule of the server, and the second request message into which the second parameter is inserted is a third request message.
Specifically, if the analysis parameter in the second request message is correct, the self-programming plug-in of the gateway adds a second parameter in the second request message according to the server rule, where the second parameter may be multiple parameters, and the second request message into which the second parameter is inserted is used as a third request message.
And the sending unit is used for forwarding the third request message to the server.
And the return unit is used for returning the response of the server to the client.
Specifically, the gateway sends the third request message to the server, and sends the content responded by the server according to the third request message to the client.
The gateway unified authentication management method in this embodiment uniformly manages the request entries, and uniformly protects the authentication modes between the servers and the clients, so that the code specification is uniform, the development cost and the maintenance cost of developers of different servers are greatly reduced, and the security that the authentication modes are not exposed to the outside is effectively improved.
In addition, the present invention further provides a computer readable storage medium, where a computer program is stored, where the computer program is suitable for being loaded by a processor to execute the steps of the gateway unified authentication management method.
The readable storage medium in this embodiment stores, but is not limited to, the method steps for performing the unified authentication of the gateway, and after the steps are performed, the request entries can be managed in a unified manner, and the authentication manners between the servers and the clients are protected in a unified manner, so that the uniformity of code specifications is achieved, the development cost and the maintenance cost of developers of different servers are greatly reduced, and the security that the authentication manners are not exposed to the outside is effectively improved.
In addition, the invention also provides a computer, which comprises a memory and a processor, wherein the memory stores a computer program, and the processor executes the steps of the gateway unified authentication management method by calling the computer program stored in the memory.
The computer in this embodiment can uniformly manage the request entry by executing the steps of the gateway uniform authentication management method, and uniformly protect the authentication modes between each server and the client, so that the uniformity of code specification is achieved, the development cost and the maintenance cost of developers of different servers are greatly reduced, and the security that the authentication modes are not exposed to the outside is effectively improved.
In the present specification, the embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed in the embodiment corresponds to the method disclosed in the embodiment, so that the description is simple, and the relevant points can be referred to the description of the method part.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The above embodiments are merely illustrative of the technical ideas and features of the present invention, and are intended to enable those skilled in the art to understand the contents of the present invention and implement the present invention, and not to limit the scope of the present invention. All equivalent changes and modifications made within the scope of the claims of the present invention should be covered by the claims of the present invention.

Claims (10)

1. A gateway unified authentication management method is characterized by comprising the following steps:
step S1, receiving a first request message sent by a client, wherein the first request message contains a credential, and the credential is confirmed and obtained according to agreement of both parties before the client accesses a gateway for the first time;
s2, judging whether the credential is correct or not;
s3, if yes, generating a first parameter and returning the first parameter to the client;
s4, receiving a second request message sent by the client, wherein the second request message contains the first parameter, an analysis parameter and a server rule, and the analysis parameter and the server rule are confirmed and obtained according to the agreement of the client and the gateway before the client accesses the gateway for the first time;
s5, judging whether the first parameter in the second request message is correct or not;
s6, if yes, judging whether the analysis parameters are correct or not;
s7, if so, inserting a second parameter into the second request message, wherein the second parameter corresponds to the rule of the server, and the second request message into which the second parameter is inserted is a third request message;
s8, sending the third request message to the server;
and S9, returning the response of the server to the client.
2. The gateway unified authentication management method according to claim 1, wherein the step of generating the first parameter and returning the first parameter to the client in step S3 comprises the steps of:
and step S31, after the first parameter is generated, returning the first parameter to the client, and adding the first parameter into the first request message by the client, wherein the first request message after the first parameter is added is a second request message.
3. The gateway unified authentication management method according to claim 1, wherein the step of generating the first parameter and returning the first parameter to the client in step S3 comprises the steps of:
step S32, after the first parameter is generated, the first parameter is returned to the client, the client adds the first parameter to the first request message and stores the first parameter in the database, and when the client requests again, the first parameter in the database is added to the first request message, wherein the first request message after the first parameter is added is a second request message.
4. The gateway unified authentication management method according to claim 1,
in the step S4, the parsing parameter corresponds to the server rule, and each server corresponds to one of the server rules.
5. The gateway unified authentication management method according to claim 1, further comprising, after said step S2 and before said step S4, the steps of:
and S21, if the credential is incorrect, returning error information of authentication failure to the client.
6. The gateway unified authentication management method according to claim 1, further comprising, after said step S5 and before said step S6, the steps of:
step S51, if the first parameter in the second request message is incorrect, returning an error message to the client.
7. The gateway unified authentication management method according to claim 1, further comprising, after said step S6 and before said step S8, the steps of:
and S62, if the analysis parameters are incorrect, returning error information to the client.
8. A gateway unified authentication management method device is characterized by comprising the following steps:
the first receiving unit is used for receiving a first request message sent by a client, wherein the first request message contains a credential, and the credential is obtained by confirming according to agreement of both parties before the client accesses a gateway for the first time;
the first judging unit is used for judging whether the credential is correct or not;
the first feedback unit is used for generating a first parameter and returning the first parameter to the client when the credential is correct;
a second receiving unit, configured to receive a second request packet sent by the client, where the second request packet includes the first parameter, an analysis parameter, and a server rule, and the analysis parameter and the server rule are obtained by confirming according to a contract between the client and the server before the client accesses the gateway for the first time;
a second determining unit, configured to determine whether the first parameter in the second request message is correct;
a third determining unit, configured to determine whether the parsing parameter is correct when the first parameter in the second request message is correct;
a second feedback unit, configured to insert a second parameter into the second request packet if the parsing parameter is correct, where the second parameter corresponds to a rule of the server, and the second request packet after the second parameter is inserted is a third request packet;
a sending unit, configured to forward the third request packet to the server;
and the return unit is used for returning the response of the server to the client.
9. A computer-readable storage medium, characterized in that it stores a computer program adapted to be loaded by a processor for performing the steps of the gateway unified authentication management method according to any of claims 1 to 7.
10. A computer, characterized in that it comprises a memory in which a computer program is stored and a processor which performs the steps of the gateway unified authentication management method according to any one of claims 1 to 7 by calling the computer program stored in the memory.
CN202210590954.7A 2022-05-27 2022-05-27 Gateway unified authentication management method, device, storage medium and computer Active CN115174142B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210590954.7A CN115174142B (en) 2022-05-27 2022-05-27 Gateway unified authentication management method, device, storage medium and computer

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210590954.7A CN115174142B (en) 2022-05-27 2022-05-27 Gateway unified authentication management method, device, storage medium and computer

Publications (2)

Publication Number Publication Date
CN115174142A true CN115174142A (en) 2022-10-11
CN115174142B CN115174142B (en) 2024-01-12

Family

ID=83483909

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210590954.7A Active CN115174142B (en) 2022-05-27 2022-05-27 Gateway unified authentication management method, device, storage medium and computer

Country Status (1)

Country Link
CN (1) CN115174142B (en)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012024910A1 (en) * 2010-08-23 2012-03-01 中兴通讯股份有限公司 Authentication method, apparatus and system
CN110493352A (en) * 2019-08-30 2019-11-22 南京联创互联网技术有限公司 A kind of unified gateway service system and its method of servicing based on WEB middleware
CN111416822A (en) * 2020-03-20 2020-07-14 数篷科技(深圳)有限公司 Method for access control, electronic device and storage medium
CN112039909A (en) * 2020-09-03 2020-12-04 平安科技(深圳)有限公司 Authentication method, device, equipment and storage medium based on unified gateway
CN112351015A (en) * 2020-10-28 2021-02-09 广州助蜂网络科技有限公司 Gateway control method based on API
US20210336788A1 (en) * 2020-04-24 2021-10-28 Netapp, Inc. Management services api gateway
CN113992755A (en) * 2021-10-27 2022-01-28 中国电信股份有限公司 Request processing method, system, equipment and storage medium based on micro service gateway
CN113992354A (en) * 2021-09-28 2022-01-28 新华三信息安全技术有限公司 Identity authentication method, device, equipment and machine readable storage medium

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012024910A1 (en) * 2010-08-23 2012-03-01 中兴通讯股份有限公司 Authentication method, apparatus and system
CN110493352A (en) * 2019-08-30 2019-11-22 南京联创互联网技术有限公司 A kind of unified gateway service system and its method of servicing based on WEB middleware
CN111416822A (en) * 2020-03-20 2020-07-14 数篷科技(深圳)有限公司 Method for access control, electronic device and storage medium
US20210336788A1 (en) * 2020-04-24 2021-10-28 Netapp, Inc. Management services api gateway
CN112039909A (en) * 2020-09-03 2020-12-04 平安科技(深圳)有限公司 Authentication method, device, equipment and storage medium based on unified gateway
CN112351015A (en) * 2020-10-28 2021-02-09 广州助蜂网络科技有限公司 Gateway control method based on API
CN113992354A (en) * 2021-09-28 2022-01-28 新华三信息安全技术有限公司 Identity authentication method, device, equipment and machine readable storage medium
CN113992755A (en) * 2021-10-27 2022-01-28 中国电信股份有限公司 Request processing method, system, equipment and storage medium based on micro service gateway

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
李建佳;王晶;: "基于JA-SIG CAS统一认证平台(SSO)的设计与实现", 广东海洋大学学报, no. 03 *

Also Published As

Publication number Publication date
CN115174142B (en) 2024-01-12

Similar Documents

Publication Publication Date Title
CN111586030B (en) Interface authentication and permission verification method and system based on micro-service multi-tenant
CN112866379B (en) Access method and device of microservice
KR102121140B1 (en) Method and device for comparing data versions between time zone crossing stations
WO2022142153A1 (en) Electricity meter upgrading method and system, smart meter, and storage medium
CN108933789B (en) Method for preventing personal information leakage and third-party application server
CN113381979A (en) Access request proxy method and proxy server
US20220377556A1 (en) Internet-of-things device registration method and apparatus, device, and storage medium
CN102611683B (en) A kind of method, device, equipment and system for performing Third Party Authentication
CN106789987B (en) Method and system for single sign-on of multi-service interconnection APP (application) of mobile terminal
CN113194099B (en) Data proxy method and proxy server
CN114297678A (en) Operation method, device, equipment and storage medium of union chain system
CN112653911B (en) Key updating method and equipment
CN114268487A (en) Authority control method and device based on industrial identification node
US20230325833A1 (en) Blockchain-based data processing method and apparatus, device, storage medium, and program product
CN115174142B (en) Gateway unified authentication management method, device, storage medium and computer
CN108924149B (en) Token-based identity validity verification method and system
CN111211902A (en) Digital signature method and device based on enterprise browser
CN111932326B (en) Data processing method based on block chain network and related equipment
CN114445204A (en) Cloud-plus-end-based tax control equipment service processing method and system
CN112597118B (en) Shared file adding method and device
CN110602139B (en) Recharge login access method and system based on Tencent cloud
CN112929397B (en) User information processing method and device, computer equipment and storage medium
CN108449367B (en) Method and device for managing user login security, electronic equipment and readable medium
US10382431B2 (en) Network hop count network location identifier
CN112887255A (en) Network communication method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant