CN114500078A - Authorization management method and device, computer equipment and storage medium - Google Patents
Authorization management method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN114500078A CN114500078A CN202210135491.5A CN202210135491A CN114500078A CN 114500078 A CN114500078 A CN 114500078A CN 202210135491 A CN202210135491 A CN 202210135491A CN 114500078 A CN114500078 A CN 114500078A
- Authority
- CN
- China
- Prior art keywords
- authentication data
- request
- server
- operation request
- client
- 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.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/108—Network architectures or network communication protocols for network security for controlling access to devices or network resources when the policy decisions are valid for a limited amount of time
Abstract
The present disclosure provides an authorization management method, apparatus, computer device and storage medium, wherein the method comprises: sending a first operation request to a server, wherein the first operation request comprises authentication data; under the condition that failure information of failure of the authentication data fed back by the server is received, a request for updating the authentication data is sent to the server; and under the condition of receiving new identity authentication data sent by the server, generating and sending a second operation request to the server based on the first operation request and the new identity authentication data so as to obtain result data corresponding to the first operation request fed back by the server. According to the embodiment of the disclosure, the result data corresponding to the first operation request is requested to be obtained from the server by simulating the first operation request, namely the second operation request, carrying the new authentication data, so that the result data can be obtained without interrupting the first operation request, and the experience of a user is improved.
Description
Technical Field
The present disclosure relates to the field of computer security technologies, and in particular, to an authorization management method, an authorization management apparatus, a computer device, and a storage medium.
Background
The OAUTH protocol is an authorization mechanism, and an owner of data agrees to a third-party application access system to acquire the data in an authorization mode, and simultaneously generates a short-term channel token to replace a password, so that the privacy and the security of data transmission can be ensured. Because an attacker can obtain the access _ token by using the vulnerability and hidden danger of data leakage exists, the access _ token is set to be short in effective time so as to prevent data loss caused by leakage of the access _ token. However, after the access _ token expires, the access _ token carried by the request task is invalid, so that the request task is interrupted, the continuity of user operation cannot be ensured, and the user experience is greatly reduced.
Disclosure of Invention
The embodiment of the disclosure at least provides an authorization management method, an authorization management device, computer equipment and a storage medium.
In a first aspect, an embodiment of the present disclosure provides an authorization management method, applied to a client, including:
sending a first operation request to a server, wherein the first operation request comprises authentication data;
under the condition that failure information of the identity authentication data failure fed back by the server is received, sending a request for updating the identity authentication data to the server;
and under the condition of receiving new identity authentication data sent by the server, generating and sending a second operation request to the server based on the first operation request and the new identity authentication data so as to obtain result data corresponding to the first operation request fed back by the server.
In an alternative embodiment, the first operation request includes at least two interface requests;
the sending, to the server, a request for updating the authentication data when receiving failure information that the authentication data fed back by the server is failed includes:
and under the condition of receiving failure information of the failure of the authentication data fed back by the server, respectively sending a request for updating the authentication data corresponding to each interface request to the server.
In an optional implementation manner, after receiving result data corresponding to the first operation request fed back by the server, the method further includes:
acquiring a first verification result of the new identity verification data;
and under the condition that the first verification result indicates that the new authentication data is invalid, re-sending a request for updating the new authentication data to the server.
In an optional embodiment, after obtaining the first verification result of the new authentication data, the method further includes:
and under the condition that the first verification result indicates that the new identity authentication data is valid, displaying result data corresponding to the first operation request fed back by the server to a user.
In an optional implementation manner, after sending the first operation request to the server, the method further includes:
acquiring a second check result of the identity verification data;
and under the condition that the second check result indicates that the identity verification data is valid, displaying result data corresponding to the first operation request fed back by the server to a user.
In an optional implementation manner, after receiving new authentication data sent by the server, the method further includes:
replacing the authentication data in the database with new authentication data.
In a second aspect, an embodiment of the present disclosure provides an authorization management method, applied to a server, including:
receiving a first operation request sent by a client, wherein the first operation request comprises authentication data;
under the condition that the identity authentication data is determined to be invalid, failure information of the identity authentication data invalidation is sent to the client;
under the condition that a request for updating the authentication data sent by the client is received, generating new authentication data and sending the new authentication data to the client;
under the condition of receiving a second operation request sent by the client, sending result data corresponding to the first operation request to the client; the second operation request is generated based on the first operation request and the new authentication data.
In an optional embodiment, the generating the new authentication data in case of receiving a request sent by the client to update the authentication data includes:
judging whether the identity authentication data is updated at the current moment;
updating the authentication data if it is determined that the authentication data is not being updated at the present time.
In an optional embodiment, the determining whether the authentication data is updated at the current time includes:
and under the condition that the identity verification data is determined to be updated at the current moment, the operation of updating the identity verification data is not repeated.
In an alternative embodiment, the first operation request includes at least two interface requests; the second operation request comprises a simulation interface request corresponding to each interface request;
the sending, to the client, result data corresponding to the first operation request when receiving a second operation request sent by the client includes:
and under the condition of receiving each simulation interface request sent by the client, sending result data requested by the interface request corresponding to the simulation interface request to the client.
In an optional implementation manner, after receiving the first operation request, the method further includes:
and under the condition that the identity authentication data is determined to be valid, sending result data corresponding to the first operation request to the client.
In a third aspect, an embodiment of the present disclosure provides an authorization management apparatus, including:
the operation request module is used for sending a first operation request to a server, wherein the first operation request comprises authentication data;
the request updating module is used for sending a request for updating the identity authentication data to the server under the condition of receiving failure information that the identity authentication data fed back by the server fails;
and the simulation request module is used for generating and sending a second operation request to the server based on the first operation request and the new authentication data under the condition of receiving the new authentication data sent by the server so as to obtain result data corresponding to the first operation request fed back by the server.
In an alternative embodiment, the first operation request includes at least two interface requests;
the request updating module is configured to send, to the server, requests for updating the authentication data corresponding to each interface request, respectively, when failure information that the authentication data fails and is fed back by the server is received.
In an optional implementation manner, the request updating module is further configured to obtain a first verification result of new authentication data after receiving result data corresponding to the first operation request fed back by the server; and under the condition that the first verification result indicates that the new authentication data is invalid, re-sending a request for updating the new authentication data to the server.
In an optional implementation manner, the authorization management apparatus further includes a display module, configured to, after a first verification result of new authentication data is obtained, display, to a user, result data corresponding to the first operation request fed back by the server under a condition that the first verification result indicates that the new authentication data is valid.
In an optional implementation manner, the presentation module is further configured to obtain a second check result of the authentication data after sending the first operation request to the server; and under the condition that the second check result indicates that the identity verification data is valid, displaying result data corresponding to the first operation request fed back by the server to a user.
In an optional implementation manner, the authorization management apparatus further includes a replacing module, configured to replace, after receiving new authentication data sent by the server, the authentication data in the database with the new authentication data.
In a fourth aspect, an embodiment of the present disclosure provides an authorization management apparatus, including:
the system comprises a receiving module, a sending module and a processing module, wherein the receiving module is used for receiving a first operation request sent by a client, and the first operation request comprises authentication data;
the verification module is used for sending failure information of the failure of the identity authentication data to the client under the condition that the identity authentication data is determined to be failed;
the updating module is used for generating new authentication data and sending the new authentication data to the client under the condition of receiving a request for updating the authentication data sent by the client;
the feedback result module is used for sending result data corresponding to the first operation request to the client under the condition of receiving a second operation request sent by the client; the second operation request is generated based on the first operation request and the new authentication data.
In an optional implementation manner, the update module is configured to determine whether the authentication data is being updated at the current time; updating the authentication data if it is determined that the authentication data is not being updated at the present time.
In an optional embodiment, the updating module is configured to, in a case that it is determined that the authentication data is updated at the current time, not repeat the operation of updating the authentication data.
In an alternative embodiment, the first operation request includes at least two interface requests; the second operation request comprises a simulation interface request corresponding to each interface request;
and the feedback result module is used for sending result data requested by the interface request corresponding to the simulation interface request to the client under the condition of receiving each simulation interface request sent by the client.
In an optional implementation manner, the feedback result module is further configured to send, after receiving the first operation request, result data corresponding to the first operation request to the client when it is determined that the authentication data is valid.
In a fifth aspect, an embodiment of the present disclosure further provides a computer device, including: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory communicating via the bus when the computer device is running, the machine-readable instructions when executed by the processor performing the above first and second aspects, or the steps of any of the possible implementations of the first aspect and the steps of any of the possible implementations of the second aspect.
In a sixth aspect, the disclosed embodiments also provide a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, performs the above first and second aspects, or the steps in any one of the possible implementations of the first aspect and the steps in any one of the possible implementations of the second aspect.
For the description of the effects of the authorization management apparatus, the computer device and the storage medium, reference is made to the description of the authorization management method, and details are not repeated here.
According to the authorization management method, the authorization management device, the computer equipment and the storage medium, a first operation request is sent to a server side, wherein the first operation request comprises authentication data; under the condition that failure information of failure of the authentication data fed back by the server is received, a request for updating the authentication data is sent to the server; compared with the request interruption in the prior art, the embodiment of the disclosure requests the server to acquire the result data corresponding to the first operation request by simulating the first operation request, namely the second operation request, and carrying the new authentication data under the condition that the authentication data is invalid, and can acquire the result data without interrupting the first operation request, thereby improving the efficiency of displaying information for a user while ensuring the operation continuity, and further improving the experience of the user.
Further, the authorization management method, the authorization management device, the computer device, and the storage medium provided in the embodiments of the present disclosure do not repeat the operation of updating the authentication data when it is determined that the authentication data is updated at the current time. The method and the device can ensure that the situation of repeated updating can not occur when the identity authentication data is requested to be updated, and reduce the operating pressure of the system, thereby improving the efficiency of obtaining result data by a user and improving the usability of the system.
In order to make the aforementioned objects, features and advantages of the present disclosure more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings required for use in the embodiments will be briefly described below, and the drawings herein incorporated in and forming a part of the specification illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the technical solutions of the present disclosure. It is appreciated that the following drawings depict only certain embodiments of the disclosure and are therefore not to be considered limiting of its scope, for those skilled in the art will be able to derive additional related drawings therefrom without the benefit of the inventive faculty.
Fig. 1 is a schematic view illustrating an application scenario of an authorization management method provided by an embodiment of the present disclosure;
FIG. 2 is a flow chart illustrating a method for authorization management provided by an embodiment of the present disclosure;
FIG. 3 is a schematic diagram illustrating client-side and server-side information interaction under a single interface request provided by an embodiment of the present disclosure;
FIG. 4 is a flow chart illustrating another authorization management method provided by an embodiment of the present disclosure;
FIG. 5 is a schematic diagram illustrating client-side information interaction with a server-side information interaction under a plurality of interface requests provided by an embodiment of the present disclosure;
FIG. 6 is a schematic diagram of an authorization management device provided by an embodiment of the disclosure;
FIG. 7 is a schematic diagram of another authorization management device provided by an embodiment of the disclosure;
fig. 8 shows a schematic structural diagram of a computer device provided by an embodiment of the present disclosure.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present disclosure more clear, the technical solutions of the embodiments of the present disclosure will be described clearly and completely with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, not all of the embodiments. The components of the embodiments of the present disclosure, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present disclosure, presented in the figures, is not intended to limit the scope of the claimed disclosure, but is merely representative of selected embodiments of the disclosure. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the disclosure without making creative efforts, shall fall within the protection scope of the disclosure.
Furthermore, the terms "first," "second," and the like in the description and in the claims, and in the drawings described above, in the embodiments of the present disclosure are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein.
Reference herein to "a plurality or a number" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
Research shows that the OAUTH protocol is an authorization mechanism, and a data owner agrees to a third-party application access system to acquire data in an authorization mode, and generates a short-term channel token access _ token to replace a password, so that the privacy and the security of data transmission can be ensured. Because an attacker can obtain the access _ token by utilizing the vulnerability and hidden danger of data leakage exists, the access _ token can be set to be short effective time so as to prevent data loss caused by leakage of the access _ token. However, after the access _ token expires, the access _ token carried by the request task is invalid, so that the request task is interrupted, the continuity of user operation cannot be ensured, and the user experience is greatly reduced.
Based on the above research, the present disclosure provides an authorization management method, an authorization management apparatus, a computer device, and a storage medium, where, when authentication data fails, a request is made to a server to obtain result data corresponding to a first operation request by simulating the first operation request, that is, a second operation request, and carrying new authentication data, and the result data can be obtained without interrupting the request, so that efficiency of displaying information for a user is improved, and further experience of the user is improved.
The above-mentioned drawbacks are the results of the inventor after practical and careful study, and therefore, the discovery process of the above-mentioned problems and the solutions proposed by the present disclosure to the above-mentioned problems should be the contribution of the inventor in the process of the present disclosure.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
To facilitate understanding of the present embodiment, terms mentioned in the embodiments of the present disclosure are further explained first:
1. access _ token: in the Oauth2.0 protocol, a client accesses a channel token of a resource server, and possession of this token represents authorization of the user.
2. Refresh _ token: the method is used for updating the access _ token, and because the access _ token is easy to leak in the using process, a short effective period is given to the access _ token, so that the leakage risk can be reduced.
3. The network request tool library used in the embodiment of the disclosure adopts the umi-request, and is mainly realized by an interceptor mechanism.
4. isRefresh, a variable that indicates whether the refresh interface is currently triggered.
5. false is no, if isRefresh is false, it indicates that the authentication data is not being updated at the current time.
6. true is if isRefresh ═ true, indicating that the authentication data is being updated at the current time.
To facilitate understanding of the present embodiment, first, an application scenario of the authorization management method disclosed in the present embodiment is described, referring to fig. 1, where a user obtains information stored by a server 12 through a client 11 installed in a terminal device, where the client 11 may be an application client installed in the terminal device, such as a mobile phone, a tablet computer, and the like, or may also be a browser of a web page. Here, the client further includes an interceptor. The client 11 and the server 12 may communicate through a communication network.
The method can be applied to an online education scene, wherein the user can be a student, the client is a student end, and the server end is a teacher end. The student can send to the teacher end and obtain personal information, here, personal information can pass through the A interface request, carry access _ token in the request of A interface, because from the student end to the in-process of teacher end request access information, probably lead to access _ token to become invalid, therefore, it is effective whether access _ token needs further check-up of service end, under the effectual request of access _ token, the service end can directly feed back student's personal information to the student, under the condition that access _ token became invalid, access _ token will be updated again, so that the student utilizes new access _ token to obtain personal information.
To facilitate understanding of the present embodiment, first, a detailed description is given to an authorization management method disclosed in an embodiment of the present disclosure, where an execution subject of the authorization management method provided in the embodiment of the present disclosure is generally a computer device with certain computing capability, and the computer device includes, for example: a terminal device, which may be a User Equipment (UE), a mobile device, a User terminal, a cellular phone, a cordless phone, a Personal Digital Assistant (PDA), a handheld device, a computing device, a vehicle-mounted device, a wearable device, or a server or other processing device. In some possible implementations, the authorization management method may be implemented by a processor calling computer readable instructions stored in a memory.
The following describes the authorization management method provided by the embodiment of the disclosure by taking the execution subject as the client.
Based on the application scenario, an embodiment of the present disclosure provides an authorization management method, as shown in fig. 2, which may include the following steps S201 to S203, where:
s201: and sending a first operation request to the server, wherein the first operation request comprises authentication data.
In this step, the first operation request may be a request of a user for accessing data, or may be a request of a user for storing data, or may be a request of a user for modifying data, and the like. Illustratively, the client may send the first operation request to the server through the a interface.
Here, the authentication data may be a channel token, such as access _ token, which the user can perform the first operation request, instead of the password. When a user sends a first operation request to a server, the user can execute the first operation request by carrying the access _ token.
S202: and under the condition of receiving failure information of failure of the authentication data fed back by the server, sending a request for updating the authentication data to the server.
Since the hidden danger of leakage of the access _ token may exist in the process of sending the first operation request by the client and transmitting the first operation request to the server, the access _ token is set to be short effective time so as to prevent data loss caused by leakage of the access _ token. In addition, the data transmission process needs time, and therefore, there may be a case where the access _ token fails, so the server needs to check whether the access _ token fails. In some embodiments, after the interceptor receives result data corresponding to the first operation request fed back by the server, it is further required to determine whether new authentication data fed back by the a interface is valid. Here, the interceptors are deployed on the client side.
In specific implementation, the server may feed back the second check result of the authentication data to the client, the client obtains the second check result of the authentication data, and the interceptor may send a request for updating the authentication data to the server when the second check result indicates that the authentication data is invalid. And under the condition that the second check result indicates that the identity verification data is valid, the interceptor can directly display result data corresponding to the first operation request fed back by the server to the user.
In this step, when the interceptor receives failure information that the authentication data fed back by the server is invalid, the interceptor needs to update the authentication data again to ensure that the first operation request is continuously executed, so the interceptor needs to send a request for updating the authentication data to the server.
For example, the interceptor may send a request for updating the authentication data to the server, through an update interface and carrying refresh _ token, to request to update the access _ token.
S203: and under the condition of receiving new identity authentication data sent by the server, generating and sending a second operation request to the server based on the first operation request and the new identity authentication data so as to obtain result data corresponding to the first operation request fed back by the server.
Based on the request for updating the authentication data sent to the server in step S202, the server may generate new authentication data and send the new authentication data to the client.
Continuing the example, when the interceptor receives the new access _ token sent by the server, the interceptor can simulate the first operation request to generate the second operation request, carry the new access _ token through the a interface, and send the second operation request to the server to continue to execute the first operation request, so as to obtain the result data corresponding to the first operation request fed back by the server. The continuity of the first operation request can be ensured, and the result data corresponding to the first operation request is obtained under the condition that the first operation request is not interrupted; in addition, the first operation request can be continuously executed, so that the efficiency of displaying information for the user is improved, and the experience of the user is further improved.
In some embodiments, in the case that the interceptor receives new authentication data sent by the server, the authentication data in the database may be replaced with the new authentication data. The database is arranged at the client side and can be updated and cached in real time so as to replace the authentication data with new authentication data, and the fact that the carried authentication data is valid authentication data when the user sends an operation request to the server side next time is guaranteed.
In some embodiments, after the interceptor receives result data corresponding to the first operation request fed back by the server, it is further required to determine whether new authentication data fed back by the server is valid. Here, the server may feed back a first verification result of the new authentication data to the client, the client obtains the first verification result of the new authentication data, and the interceptor may directly display result data corresponding to the first operation request to the user when the first verification result indicates that the new authentication data is valid. In a case that the first check result indicates that the new authentication data is invalid, the interceptor needs to send a request for updating the new authentication data to the server again, and the specific updating process may refer to step S202, and repeated parts are not described herein.
In some embodiments, the first operation request may include at least two interface requests. Here, the at least two interface requests included in the first operation request may be requests sent to the server at the same time, such as an a interface request and a B interface request, where the authentication data carried by the a interface request and the B interface request is valid, but in the data transmission process, it is not guaranteed whether the authentication data is valid, and therefore, the server needs to check the authentication data.
In a specific implementation, the server may feed back the second check result of the authentication data carried by the interface a request and the second check result of the authentication data carried by the interface B request to the client, and the client obtains the second check result of the authentication data. Specifically, under the condition that the second check result indicates that the authentication data is invalid, the interceptor may send a request for updating the authentication data corresponding to each interface request to the server, respectively; and under the condition that the second check result indicates that the identity verification data is valid, the interceptor can display result data corresponding to the interface A request and result data corresponding to the interface B request which are respectively fed back by the server to the user.
Here, after the interceptor sends a request for updating the authentication data corresponding to each interface request to the server, where the interface a request and the interface B request are performed simultaneously, the repeated updating of the authentication data is avoided, and at this time, the server may generate only one new authentication data and send the new authentication data to the client. Then, under the condition that the interceptor receives new authentication data sent by the server, an interface a request and an interface B request can be simultaneously simulated by the interceptor, wherein the simulated interface a request is sent to the server by carrying the new authentication data through the interface a, and the simulated interface B request is sent to the server by carrying the new authentication data through the interface B, so as to continue to execute the first operation request, thereby obtaining result data corresponding to the interface a request and result data corresponding to the interface B request fed back by the server.
For example, for an online education scenario, in a case where a student wants to access details of the student in the server, here, the details of the student may include student personal information and student course information, wherein the student personal information may be transmitted through the a interface, and the student course information may be transmitted through the B interface. Specifically, the client sends an interface A request and an interface B request to the server, the server checks an access _ token carried by the interface A request and an access _ token carried by the interface B request, and the interceptor can send a request for updating the access _ token corresponding to each interface request to the server through an updating interface and a refresh _ token carried by the interceptor according to a second check result fed back by the server under the condition that the second check result indicates that the access _ token is invalid. Here, since the a interface request and the B interface request are simultaneously made and request for updating the access _ token, the server may generate only one new access _ token and transmit the new access _ token to the client. And then, respectively simulating an interface A request and an interface B request through the interceptor, wherein the interface A request carries a new access _ token through the interface A and is sent to the server, and the interface B request carries the new access _ token through the interface B and is sent to the server so as to continuously access the student details in the server and obtain the student personal information corresponding to the interface A request and the student course information corresponding to the interface B request fed back by the server.
In summary, for information interaction between the client and the server, reference may be made to fig. 3, which is a schematic diagram of information interaction between the client and the server under a single interface request. Here, the client is provided with an interceptor.
Firstly, the client sends an interface request A, and if the server verifies that the access _ token is invalid, the server executes a second step; if the server side feedback access _ token is valid, executing step (c).
And step two, the server side feeds back the failure of the access _ token to the interceptor.
And step three, the interceptor requests to update the access _ token through an updating interface and carrying refresh _ token.
Step four, the server side updates the access _ token and sends the new access _ token to the interceptor; the interceptor replaces the access _ token in the database with the new access _ token.
And fifthly, simulating an A interface request by the interceptor, and carrying a new access _ token to send to the server.
Step sixthly, sending result data corresponding to the interface request A to the interceptor.
Step (c), the interceptor judges whether a new access _ token or an access _ token carried by the interface A fed back by the server is valid, and under the condition that the new access _ token or the access _ token is invalid, the interceptor needs to execute the step (c) and sends a request for updating the new access _ token or the access _ token to the server again; in case the new access _ token or access _ token is valid, the step is executed.
And step eight, the interceptor displays the result data corresponding to the interface A request to the user.
The following describes the authorization management method provided by the embodiment of the disclosure by taking the execution subject as a server.
The embodiment of the present disclosure further provides another authorization management method, as shown in fig. 4, the authorization management method may include the following steps S401 to S404, where:
s401: receiving a first operation request sent by a client, wherein the first operation request comprises authentication data.
In this step, the first operation request and the authentication data may refer to the description in step S201, and repeated parts are not described herein again.
S402: and under the condition that the authentication data is determined to be invalid, the invalid information of the authentication data invalidation is sent to the client.
Here, for any interface request sent by the client, the authentication data carried in the interface request, such as access _ token, needs to be checked first, and a second check result is generated.
In one embodiment, in case it is determined that the authentication data indicated by the second check result is invalid, invalidation information of the invalidation of the authentication data is sent to the client.
In another embodiment, in case it is determined that the authentication data indicated by the second check result is valid, result data corresponding to the first operation request is sent to the client.
S403: and under the condition of receiving a request for updating the authentication data sent by the client, generating new authentication data and sending the new authentication data to the client.
Specifically, when a request for updating the authentication data transmitted by the update interface is received, that is, when a refresh _ token is received, the access _ token is updated, a new access _ token is generated, and the new access _ token is sent to the interceptor.
S404: and under the condition of receiving a second operation request sent by the client, sending result data corresponding to the first operation request to the client.
Wherein the second operation request is generated based on the first operation request and the new authentication data.
Based on the step S403, in order to avoid repeatedly updating the authentication data and improve the efficiency of displaying information for the user, an implementation manner is provided below, which can ensure that the interface does not repeatedly update when requesting to update the authentication data.
In specific implementation, whether identity authentication data is updated at the current moment is judged; under the condition that the identity authentication data is not updated at the current moment, updating the identity authentication data to obtain new identity authentication data; under the condition that the identity authentication data is determined to be updated at the current moment, the operation of updating the identity authentication data is not repeated, and meanwhile, whether the identity authentication data is updated at the current moment or not is detected regularly.
Illustratively, after receiving a request for updating the authentication data from the update interface, checking a value of a variable isRefresh, where the variable isRefresh indicates whether the refresh interface is currently triggered, and if isRefresh is false, indicating that the authentication data is not being updated at the current time, it may normally request to update the access _ token, and generate a new access _ token; if isRefresh ═ true, it means that the authentication data is being updated at the current time, at this time, the access _ token cannot be requested to be updated again, otherwise, a repeat request will result, and then, it is only necessary to periodically detect whether isRefresh is false. Here, the timing time may be customized according to an application scenario, and the embodiment of the present disclosure is not limited. Note that isRefresh is true when the server is updating access _ token. After generating a new access _ token, let isRefresh be false. If isRefresh is false, the new access _ token is directly sent to the interface waiting for the request to update the access _ token, and then the interface waiting for the request to update the access _ token does not need to request to update the access _ token again.
In some embodiments, the first operation request may include at least two interface requests; the second operation request includes a simulated interface request corresponding to each interface request. Here, the at least two interface requests included in the first operation request may be requests sent to the server at the same time, such as an a interface request and a B interface request, and the second operation request includes a simulated interface request corresponding to each interface request, such as a simulated a interface request and a simulated B interface request.
After receiving the request for updating the authentication data from the interface a and the request for updating the authentication data from the interface B, which are sent by the interceptor, respectively, it is further required to determine whether the authentication data is being updated at the current time.
Illustratively, after receiving a request for updating authentication data from an update interface, checking a value of a variable isRefresh, if isRefresh is false, indicating that the authentication data is not updated at the present time, normally requesting to update an access _ token, at this time, requesting to update the access _ token based on an A interface request, and/or requesting to update the access _ token based on a B interface request, generating a new access _ token, and then directly sending the new access _ token to the A interface and the B interface, so that the interceptor simulates the A interface request and the B interface request respectively and sends the new access _ token to the server; if isRefresh is true, it indicates that there is an invalid access _ token request carried by the C interface request for updating, and at this time, the invalid access _ token carried by the A interface request and the B interface request cannot be updated again, and it only needs to detect in timing whether isRefresh is false. After generating a new access _ token, let isRefresh be false. And under the condition that isRefresh is false, directly sending the new access _ token to the interface A, the interface B and the interface C, so that the interceptor simulates the interface A request, the interface B request and the interface C request respectively and sends the requests carrying the new access _ token to the server.
In addition, when each simulation interface request sent by the client is received, the result data requested by the interface request corresponding to the simulation interface request is sent to the client. Here, the interface request corresponding to the simulated interface request, for example, the interface request corresponding to the simulated a interface request is an a interface request, and the interface request corresponding to the simulated B interface request is a B interface request.
In summary, for information interaction between the client and the server, reference may be made to fig. 5, which is a schematic diagram illustrating information interaction between the client and the server under a plurality of interface requests. Here, the client is provided with an interceptor. For information interaction between a client and a server under a plurality of interface requests, two interface requests are described as an example below:
the client side sends an interface A request and an interface B request at the same time, and if the server side verifies that an access _ token carried by the interface A request is invalid, the server side executes the step II; and if the server side feedback access _ token is valid, executing step (c).
And step two, the server side feeds back the failure of the access _ token to the interceptor respectively aiming at the interface A request and the interface B request.
And step three, aiming at the interface A request or the interface B request, the interceptor requests to update the access _ token by updating the interface and carrying the refresh _ token.
Judging whether the identity verification data is updated at the current moment by the server side, and if isRefresh is false, executing a fifth step; if isRefresh is true, then step r is performed.
Step five, the server side updates the access _ token, sends the new access _ token to the interceptor, and sets isRefresh as false; the interceptor replaces the access _ token in the database with the new access _ token.
And sixthly, the interceptor simulates the interface A request and the interface B request respectively and carries a new access _ token to send to the server.
Step (c), sending result data corresponding to the interface request A to the interceptor; and sending result data corresponding to the interface B request to the interceptor.
Judging whether a new access _ token or an access _ token carried by an interface A and an interface B fed back by a server is valid or not by the interceptor, and if the new access _ token or the access _ token is invalid, executing the step (c) by the interceptor and sending a request for updating the new access _ token or the access _ token to the server again; and executing step ninthly under the condition that the new access _ token or the access _ token is effective.
And ninthly, the interceptor displays the result data corresponding to the interface A request and the result data corresponding to the interface B request to the user.
And (C) the server does not repeatedly update the access _ token, and regularly detects whether isRefresh is false, if so, the fifth step is executed, and the fifth step is to say that the interceptor respectively simulates the A interface request, the B interface request and the C interface request and carries the new access _ token to send to the server aiming at the updated new access _ token indicated by the C interface request when the sixth step is continuously executed.
Through the steps S201 to S203 and the steps S401 to S404, by simulating the first operation request, that is, the second operation request, and carrying new authentication data, requesting the server to obtain result data corresponding to the first operation request, the frequency of repeatedly inputting a password by the user is reduced while the security of the user account is ensured, the result data can be obtained without interrupting the first operation request, the operation continuity is ensured, the efficiency of displaying information for the user is improved, and the experience of the user is further improved; in addition, under the condition that the first operation request comprises a plurality of interface requests, the repeated updating of the authentication data is limited, the repeated updating can be avoided when the authentication data is requested to be updated, and the system operation pressure is reduced, so that the efficiency of obtaining result data by a user is improved, and the system usability is improved.
It will be understood by those skilled in the art that in the method of the present invention, the order of writing the steps does not imply a strict order of execution and any limitations on the implementation, and the specific order of execution of the steps should be determined by their function and possible inherent logic.
Based on the same inventive concept, an authorization management device corresponding to the authorization management method is also provided in the embodiments of the present disclosure, and since the principle of solving the problem of the device in the embodiments of the present disclosure is similar to the authorization management method in the embodiments of the present disclosure, the implementation of the device may refer to the implementation of the method, and repeated details are not repeated.
Referring to fig. 6, a schematic diagram of an authorization management apparatus provided in an embodiment of the present disclosure is shown, where the apparatus includes: an operation request module 601, a request update module 602 and a simulation request module 603; wherein, the first and the second end of the pipe are connected with each other,
an operation request module 601, configured to send a first operation request to a server, where the first operation request includes authentication data;
a request updating module 602, configured to send a request for updating the authentication data to the server when failure information that the authentication data fed back by the server is failed is received;
the simulation request module 603 is configured to, when new authentication data sent by the server is received, generate and send a second operation request to the server based on the first operation request and the new authentication data, so as to obtain result data corresponding to the first operation request fed back by the server.
In an alternative embodiment, the first operation request includes at least two interface requests;
the request updating module 602 is configured to send, to the server, requests for updating the authentication data corresponding to each interface request respectively when failure information that the authentication data fed back by the server fails is received.
In an optional implementation manner, the request updating module 602 is further configured to obtain a first verification result of new authentication data after receiving result data corresponding to the first operation request fed back by the server; and under the condition that the first verification result indicates that the new authentication data is invalid, re-sending a request for updating the new authentication data to the server.
In an optional implementation manner, the authorization management apparatus further includes a displaying module 604, configured to, after obtaining a first verification result of new authentication data, display result data corresponding to the first operation request fed back by the server to a user when the first verification result indicates that the new authentication data is valid.
In an optional implementation manner, the presentation module 604 is further configured to obtain a second check result of the authentication data after sending the first operation request to the server; and under the condition that the second check result indicates that the identity verification data is valid, displaying result data corresponding to the first operation request fed back by the server to a user.
In an optional implementation manner, the authorization management apparatus further includes a replacing module 605, configured to replace the authentication data in the database with new authentication data after receiving the new authentication data sent by the server.
Referring to fig. 7, a schematic diagram of another authorization management apparatus provided in an embodiment of the present disclosure is shown, where the apparatus includes: a receiving module 701, a checking module 702, an updating module 703 and a feedback result module 704; wherein, the first and the second end of the pipe are connected with each other,
a receiving module 701, configured to receive a first operation request sent by a client, where the first operation request includes authentication data;
a checking module 702, configured to send failure information indicating that the authentication data fails to be valid to the client when it is determined that the authentication data fails;
an updating module 703, configured to generate new authentication data and send the new authentication data to the client when receiving a request for updating the authentication data sent by the client;
a feedback result module 704, configured to send, in a case that a second operation request sent by the client is received, result data corresponding to the first operation request to the client; the second operation request is generated based on the first operation request and the new authentication data.
In an optional implementation manner, the updating module 703 is configured to determine whether the authentication data is being updated at the current time; updating the authentication data if it is determined that the authentication data is not being updated at the present time.
In an optional embodiment, the updating module 703 is configured to, in a case that it is determined that the authentication data is updated at the current time, not repeat the operation of updating the authentication data.
In an alternative embodiment, the first operation request includes at least two interface requests; the second operation request comprises a simulation interface request corresponding to each interface request;
the feedback result module 704 is configured to, in a case that each analog interface request sent by the client is received, send result data requested by an interface request corresponding to the analog interface request to the client.
In an optional implementation manner, the feedback result module 704 is further configured to, after receiving the first operation request, send result data corresponding to the first operation request to the client if it is determined that the authentication data is valid.
The description of the processing flow of each module in the device and the interaction flow between the modules may refer to the related description in the above method embodiments, and will not be described in detail here.
Based on the same technical concept, the embodiment of the application also provides computer equipment. Referring to fig. 8, a schematic structural diagram of a computer device provided in an embodiment of the present application includes:
a processor 81, a memory 82, and a bus 83. Wherein the memory 82 stores machine-readable instructions executable by the processor 81, the processor 81 is configured to execute the machine-readable instructions stored in the memory 82, and when the machine-readable instructions are executed by the processor 81, the processor 81 performs the following steps:
s201: sending a first operation request to a server, wherein the first operation request comprises authentication data;
s202: under the condition that failure information of failure of the authentication data fed back by the server is received, a request for updating the authentication data is sent to the server;
s203: and under the condition of receiving new identity authentication data sent by the server, generating and sending a second operation request to the server based on the first operation request and the new identity authentication data so as to obtain result data corresponding to the first operation request fed back by the server.
Alternatively, processor 81 performs the following steps:
s401: receiving a first operation request sent by a client, wherein the first operation request comprises authentication data.
S402: and under the condition that the authentication data is determined to be invalid, the invalid information of the authentication data invalidation is sent to the client.
S403: and under the condition of receiving a request for updating the authentication data sent by the client, generating new authentication data and sending the new authentication data to the client.
S404: and under the condition of receiving a second operation request sent by the client, sending result data corresponding to the first operation request to the client.
The memory 82 includes a memory 821 and an external memory 822; the memory 821 is also referred to as an internal memory and is used for temporarily storing the operation data in the processor 81 and the data exchanged with the external storage 822 such as a hard disk, the processor 81 exchanges data with the external storage 822 through the memory 821, and when the computer device is operated, the processor 81 communicates with the storage 82 through the bus 83, so that the processor 81 executes the execution instructions mentioned in the above method embodiments.
The embodiments of the present disclosure also provide a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program performs the steps of the authorization management method in the foregoing method embodiments. The storage medium may be a volatile or non-volatile computer-readable storage medium.
The embodiments of the present disclosure also provide a computer program product, where the computer program product carries a program code, and instructions included in the program code may be used to execute the steps of the authorization management method in the foregoing method embodiments, which may be referred to specifically in the foregoing method embodiments, and are not described herein again.
The computer program product may be implemented by hardware, software or a combination thereof. In an alternative embodiment, the computer program product is embodied in a computer storage medium, and in another alternative embodiment, the computer program product is embodied in a Software product, such as a Software Development Kit (SDK), or the like.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the system and the apparatus described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again. In the several embodiments provided in the present disclosure, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. The above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is merely a logical division, and there may be other divisions in actual implementation, and for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or modules through some communication interfaces, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional modules in the embodiments of the present disclosure may be integrated into one processing module, or each module may exist alone physically, or two or more modules are integrated into one module.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a non-volatile computer-readable storage medium executable by a processor. Based on such understanding, the technical solution of the present disclosure may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present disclosure. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
Finally, it should be noted that: the above-mentioned embodiments are merely specific embodiments of the present disclosure, which are used for illustrating the technical solutions of the present disclosure and not for limiting the same, and the scope of the present disclosure is not limited thereto, and although the present disclosure is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive of the technical solutions described in the foregoing embodiments or equivalent technical features thereof within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the embodiments of the present disclosure, and should be construed as being included therein. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.
Claims (15)
1. An authorization management method applied to a client includes:
sending a first operation request to a server, wherein the first operation request comprises authentication data;
under the condition that failure information of the identity authentication data failure fed back by the server is received, sending a request for updating the identity authentication data to the server;
and under the condition of receiving new identity authentication data sent by the server, generating and sending a second operation request to the server based on the first operation request and the new identity authentication data so as to obtain result data corresponding to the first operation request fed back by the server.
2. The method of claim 1, wherein the first operation request comprises at least two interface requests;
the sending, to the server, a request for updating the authentication data when receiving failure information that the authentication data fed back by the server is failed includes:
and under the condition of receiving failure information of the failure of the authentication data fed back by the server, respectively sending a request for updating the authentication data corresponding to each interface request to the server.
3. The method according to any one of claims 1 or 2, further comprising, after receiving result data corresponding to the first operation request fed back by the server, the following steps:
acquiring a first verification result of the new identity verification data;
and under the condition that the first verification result indicates that the new authentication data is invalid, re-sending a request for updating the new authentication data to the server.
4. The method of claim 3, further comprising, after obtaining the first verification result of the new authentication data:
and under the condition that the first verification result indicates that the new identity authentication data is valid, displaying result data corresponding to the first operation request fed back by the server to a user.
5. The method according to any one of claims 1 or 2, further comprising, after sending the first operation request to the server:
acquiring a second check result of the identity verification data;
and under the condition that the second check result indicates that the identity verification data is valid, displaying result data corresponding to the first operation request fed back by the server to a user.
6. The method according to claim 1, further comprising, after receiving new authentication data sent by the server side:
replacing the authentication data in the database with new authentication data.
7. An authorization management method is applied to a server and comprises the following steps:
receiving a first operation request sent by a client, wherein the first operation request comprises authentication data;
under the condition that the identity authentication data is determined to be invalid, failure information of the identity authentication data invalidation is sent to the client;
under the condition that a request for updating the authentication data sent by the client is received, generating new authentication data and sending the new authentication data to the client;
under the condition of receiving a second operation request sent by the client, sending result data corresponding to the first operation request to the client; the second operation request is generated based on the first operation request and the new authentication data.
8. The method of claim 7, wherein generating the new authentication data upon receiving a request sent by the client to update the authentication data comprises:
judging whether the identity authentication data is updated at the current moment;
updating the authentication data if it is determined that the authentication data is not being updated at the present time.
9. The method of claim 8, wherein the determining whether the authentication data is being updated at the current time comprises:
and under the condition that the identity verification data is determined to be updated at the current moment, the operation of updating the identity verification data is not repeated.
10. The method of claim 7, wherein the first operation request comprises at least two interface requests; the second operation request comprises a simulation interface request corresponding to each interface request;
the sending, to the client, result data corresponding to the first operation request when receiving a second operation request sent by the client includes:
and under the condition of receiving each simulation interface request sent by the client, sending result data requested by the interface request corresponding to the simulation interface request to the client.
11. The method of claim 7, after receiving the first operation request, further comprising:
and under the condition that the identity authentication data is determined to be valid, sending result data corresponding to the first operation request to the client.
12. An authorization management device, comprising:
the operation request module is used for sending a first operation request to a server, wherein the first operation request comprises authentication data;
the request updating module is used for sending a request for updating the identity authentication data to the server under the condition of receiving failure information that the identity authentication data fed back by the server fails;
and the simulation request module is used for generating and sending a second operation request to the server based on the first operation request and the new authentication data under the condition of receiving the new authentication data sent by the server so as to obtain result data corresponding to the first operation request fed back by the server.
13. An authorization management device, comprising:
the system comprises a receiving module, a sending module and a processing module, wherein the receiving module is used for receiving a first operation request sent by a client, and the first operation request comprises authentication data;
the verification module is used for sending failure information of the failure of the identity authentication data to the client under the condition that the identity authentication data is determined to be failed;
the updating module is used for generating new authentication data and sending the new authentication data to the client under the condition of receiving a request for updating the authentication data sent by the client;
the feedback result module is used for sending result data corresponding to the first operation request to the client under the condition of receiving a second operation request sent by the client; the second operation request is generated based on the first operation request and the new authentication data.
14. A computer device, comprising: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory communicating over the bus when a computer device is run, the machine-readable instructions when executed by the processor performing the steps of the authorization management method according to any of claims 1 to 11.
15. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, performs the steps of the authorization management method according to any of the claims 1 to 11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210135491.5A CN114500078A (en) | 2022-02-14 | 2022-02-14 | Authorization management method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210135491.5A CN114500078A (en) | 2022-02-14 | 2022-02-14 | Authorization management method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114500078A true CN114500078A (en) | 2022-05-13 |
Family
ID=81479507
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210135491.5A Pending CN114500078A (en) | 2022-02-14 | 2022-02-14 | Authorization management method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114500078A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103780396A (en) * | 2014-01-27 | 2014-05-07 | 华为软件技术有限公司 | Token obtaining method and device |
| CN106534175A (en) * | 2016-12-07 | 2017-03-22 | 西安电子科技大学 | Open platform authorization and authentication system and method based on OAuth protocol |
| US20190007419A1 (en) * | 2017-06-30 | 2019-01-03 | International Business Machines Corporation | Extended oauth architecture support in a scalable environment |
| CN111131242A (en) * | 2019-12-24 | 2020-05-08 | 北京格林威尔科技发展有限公司 | Authority control method, device and system |
| CN111756753A (en) * | 2020-06-28 | 2020-10-09 | 中国平安财产保险股份有限公司 | Authority verification method and system |
-
2022
- 2022-02-14 CN CN202210135491.5A patent/CN114500078A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103780396A (en) * | 2014-01-27 | 2014-05-07 | 华为软件技术有限公司 | Token obtaining method and device |
| CN106534175A (en) * | 2016-12-07 | 2017-03-22 | 西安电子科技大学 | Open platform authorization and authentication system and method based on OAuth protocol |
| US20190007419A1 (en) * | 2017-06-30 | 2019-01-03 | International Business Machines Corporation | Extended oauth architecture support in a scalable environment |
| CN111131242A (en) * | 2019-12-24 | 2020-05-08 | 北京格林威尔科技发展有限公司 | Authority control method, device and system |
| CN111756753A (en) * | 2020-06-28 | 2020-10-09 | 中国平安财产保险股份有限公司 | Authority verification method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110351269B (en) | Method for logging in open platform through third-party server | |
| US10136281B2 (en) | Method for logging in to application, server, terminal, and nonvolatile computer readable storage medium | |
| CN106372940A (en) | Identity authentication method based on block chain network, server and terminal device | |
| CN105338011A (en) | Cloud-service-based system configuration method and apparatus, and cloud server | |
| CN103581108A (en) | Login authentication method, login authentication client, login authentication server and login authentication system | |
| CN110365684B (en) | Access control method and device for application cluster and electronic equipment | |
| KR101229858B1 (en) | Web-based system and method for sharing testing devices | |
| CN103118355A (en) | Display method of mobile terminal user information, mobile terminals and service system | |
| CN102970284A (en) | User information processing method and server | |
| CN102946384A (en) | User authentication method and device | |
| CN104065633A (en) | Method, device and system for verifying by virtue of verification diagram | |
| CN110503433A (en) | Implementation method, device, equipment and the medium endorsed in a kind of block chain | |
| CN105871423A (en) | Data processing method and device | |
| CN112532629B (en) | Data transmission method, device, equipment and medium | |
| CN113938886A (en) | Identity authentication platform test method, device, equipment and storage medium | |
| CN111628871A (en) | Block chain transaction processing method and device, electronic equipment and storage medium | |
| CN111010379B (en) | Data login method and device based on block chain network | |
| KR20130027313A (en) | Method and system for authenticating using input pattern | |
| CN105162805A (en) | User account login method and apparatus | |
| CN110602700B (en) | Seed key processing method and device and electronic equipment | |
| CN114500078A (en) | Authorization management method and device, computer equipment and storage medium | |
| CN109150880B (en) | Data transmission method, device and computer readable storage medium | |
| CN110177096A (en) | Client certificate method, apparatus, medium and calculating equipment | |
| CN107277067B (en) | Third-party system docking method based on unified developer account | |
| CN112637254B (en) | Data processing method and device, electronic equipment and computer readable storage medium |
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 |