Interface authentication method, computing device and machine-readable storage medium

Abstract

The present application discloses an interface authentication method, a computing device and a machine-readable storage medium, and relates to the field of computer technology. The method includes receiving an interface access request sent by a client, the interface access request includes a termination token and a first hash token; determining a target number of times based on the termination token; performing a hash chain operation based on the first hash token and a preset hash function until any hash chain node obtained by the hash chain operation hits the termination token or the number of hash operations included in the hash chain operation reaches the target number of times; when any hash chain node hits the termination token, determining whether the number of operations to be determined performed by any hash chain node obtained by the hash chain operation is greater than the preset number of operations; when the number of operations to be determined is greater than the preset number of operations, determining that the interface access request is legal, updating the preset number of operations, and performing double verification on the interface access request based on the hash chain operation and the preset number of operations to improve the security of interface authentication.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to an interface authentication method, a computing device, and a machine-readable storage medium. Background Art

[0002] Interface authentication refers to the authentication and permission check of users when accessing API (Application Programming Interface) to ensure the security and reliability of API. It is an important means to ensure API security. The security of API should be fully considered in its design to ensure the confidentiality, integrity and reliability of data. Interface authentication measures in the prior art mainly include key-based verification, username and password-based authentication, identity authentication and authorization through tokens, or authentication requests with identity information carried by cookies. Although the above methods can achieve secure access control of API to a certain extent, with the increase in the number of users, the improvement in security requirements, and the improvement in adaptability requirements to different scenarios, the above methods have gradually failed to meet the ever-changing user needs. Summary of the invention

[0003] In view of the above-mentioned deficiencies in the prior art, the purpose of the embodiments of the present application is to provide an interface authentication method, a computing device and a machine-readable storage medium.

[0004] In order to achieve the above-mentioned object, the first aspect of the present application provides an interface authentication method, which is applied to a server. The interface authentication method includes:

[0005] Receiving an interface access request sent by a client, wherein the interface access request includes a termination token and a first hash token;

[0006] Determine a target number of times based on the termination token;

[0007] Performing a hash chain operation based on the first hash token and a preset hash function until any hash chain node obtained by the hash chain operation hits the termination token or the number of hash operations included in the hash chain operation reaches a target number;

[0008] In the case where any hash chain node hits the termination token, determining whether the number of hash operations to be determined performed by any hash chain node obtained through the hash chain operation is greater than the preset number of operations;

[0009] When the number of operations to be determined is greater than the preset number of operations, the interface access request is determined to be legal, and the preset number of operations is updated so that the value of the updated preset number of operations is greater than the value of the preset number of operations before the update.

[0010] In the embodiment of the present application, the interface authentication method further includes:

[0011] When the number of hash operations included in the hash chain operation reaches the target number and any hash chain node obtained by the hash chain operation still does not hit the termination token, it is determined that the interface access request is illegal;

[0012] Alternatively, when any hash chain node hits the termination token but the number of operations to be determined is less than or equal to the preset number of operations, the interface access request is determined to be illegal.

[0013] In the embodiment of the present application, updating the preset number of operations includes:

[0014] Increase the preset number of operations by one and store it.

[0015] In the embodiment of the present application, before the step of receiving the interface access request sent by the client, the method further includes:

[0016] In response to the access count request received from the client, determine the type of the access count request;

[0017] When the type of the access count application is the first token generation type, obtaining the request count and the termination token in the access count application;

[0018] Determine the target number based on the number of requests;

[0019] Associating and storing the termination token with the target number;

[0020] Initialize the preset number of operations corresponding to the termination token;

[0021] The successful application information of the number of times is returned to the client, and the successful application information of the number of times includes the termination token and the target number of times.

[0022] In the embodiment of the present application, the interface authentication method further includes:

[0023] In response to a request for increasing the number of times of a termination token sent by a client, determining the number of times to be increased based on the request for increasing the number of times;

[0024] Update the target number based on the number to be increased;

[0025] The credit limit increase success information is returned to the client, and the credit limit increase success information includes the updated target number of times.

[0026] In the embodiment of the present application, the interface authentication method further includes:

[0027] In response to the access count request received from the client, determine the type of the access count request;

[0028] When the type of the access count application is the second token generation type, obtaining the number of requests in the access count application;

[0029] In response to the access count application, a corresponding initial token is generated;

[0030] Performing a hash chain operation based on the initial token and a preset hash function to generate a corresponding authentication hash chain, wherein the number of hash chain nodes included in the authentication hash chain is greater than the number of requests;

[0031] Determine the hash chain node in the authentication hash chain that hits the termination token of the authentication hash chain through the hash chain operation including the request number hash operation as the second hash token;

[0032] Determine the target number based on the number of requests;

[0033] Associating and storing the termination token with the initial token and the target number;

[0034] Initialize the preset number of operations corresponding to the termination token;

[0035] The number of successful application requests is returned to the client, and the number of successful application requests includes the termination token, the target number of times, and the second hash token.

[0036] In the embodiment of the present application, the interface authentication method further includes:

[0037] In response to a request for increasing the number of times of a termination token sent by a client, determining the number of times to be increased based on the request for increasing the number of times;

[0038] Update the target number based on the number to be increased;

[0039] Performing a hash chain operation based on the initial token and a preset hash function to generate an authentication hash chain, and determining the hash chain node in the authentication hash chain that hits the termination token of the authentication hash chain through the hash chain operation including the updated target number of hash operations as the third hash token;

[0040] Return the credit limit increase success information to the client, which includes the updated target number and the third hash token.

[0041] The second aspect of the present application provides an interface authentication method, which is applied to a client. The interface authentication method includes:

[0042] Determine the type of access request based on the input access request requirement;

[0043] When the access count application type is the first token generation type, obtain the initial token and request count in the access count application requirement;

[0044] Performing a hash chain operation based on the initial token and a preset hash function to generate a corresponding authentication hash chain, wherein the number of hash chain nodes included in the authentication hash chain is greater than the number of requests;

[0045] Determine all hash chain nodes in the authentication hash chain as first hash tokens;

[0046] storing the first hash token and the termination token of the authentication hash chain;

[0047] Generate an access count application based on the termination token and the request count, and send it to a server in an interface authentication method as described in the above embodiment;

[0048] When receiving the number of successful application information returned by the server, storing the target number of successful application information;

[0049] generating an interface access request based on the stored first hash token and the termination token;

[0050] Send an interface access request to the server.

[0051] In the embodiment of the present application, the interface authentication method further includes:

[0052] Determine the number of times to be increased based on the input number of times increase demand;

[0053] Generate a request for increasing the number of times based on the number of times to be increased and send it to the server;

[0054] Accept the credit limit increase success information returned by the server and store the target number of times in the credit limit increase success information.

[0055] In the embodiment of the present application, the interface authentication method further includes:

[0056] When the access count application type is the second token generation type, obtain the initial token and request count in the access count application requirement;

[0057] Generate access count application based on initial token and request count, and send to server;

[0058] When receiving the number of successful application information returned by the server, storing the termination token, the target number of times and the second hash token in the number of successful application information;

[0059] generating an interface access request based on the second hash token and the termination token;

[0060] Send an interface access request to the server.

[0061] In the embodiment of the present application, the interface authentication method further includes:

[0062] Determine the number of times to be increased based on the input number of times increase demand;

[0063] Generate a request for increasing the number of times based on the number of times to be increased and send it to the server;

[0064] Accept the credit limit increase success information returned by the server, and store the target number of times and the third hash token in the credit limit increase success information.

[0065] A third aspect of the present application provides a computing device, including:

[0066] a memory configured to store instructions;

[0067] The processor is configured to call instructions from the memory and implement the interface authentication method applied to the server as described in the above embodiment, or the interface authentication method applied to the client as described in the above embodiment when executing the instructions.

[0068] The fourth aspect of the present application provides a machine-readable storage medium, which stores instructions for enabling a machine to execute an interface authentication method applied to a server as described in the above embodiment, or an interface authentication method applied to a client as described in the above embodiment.

[0069] Through the above technical scheme, an interface access request sent by a client is received, wherein the interface access request includes a termination token and a first hash token; a target number of times is determined based on the termination token; a hash chain operation is performed based on the first hash token and a preset hash function until any hash chain node obtained by the hash chain operation hits the termination token or the number of hash operations included in the hash chain operation reaches the target number of times; in the case where any hash chain node hits the termination token, it is determined whether the number of hash operations to be determined performed by any hash chain node obtained by the hash chain operation is greater than the preset number of operations; in the case where the number of operations to be determined is greater than the preset number of operations, it is determined that the interface access request is legal, and the preset number of operations is updated so that the value of the updated preset number of operations is greater than the value of the preset number of operations before the update. The number of times the client accesses the server is limited based on the target number of times, the server's control over the interface access is improved, and the interface access request is double-verified based on the hash chain operation and the preset number of operations, while improving the security of interface authentication, ensuring that the client fully uses the interface access resources, and improving the resource utilization of the interface access.

[0070] Other features and advantages of the embodiments of the present application will be described in detail in the subsequent specific implementation section. BRIEF DESCRIPTION OF THE DRAWINGS

[0071] The accompanying drawings are used to provide a further understanding of the embodiments of the present application and constitute a part of the specification. Together with the following specific implementations, they are used to explain the embodiments of the present application, but do not constitute a limitation on the embodiments of the present application. In the accompanying drawings:

[0072] Figure 1 A schematic diagram of a flow chart of an interface authentication method according to an embodiment of the present application is shown;

[0073] Figure 2 A flow chart of an interface authentication method according to another embodiment of the present application is schematically shown. DETAILED DESCRIPTION

[0074] In order to make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the specific implementation methods described herein are only used to illustrate and explain the embodiments of the present application, and are not used to limit the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0075] It should be noted that if the embodiments of the present application involve directional indications (such as up, down, left, right, front, back...), such directional indications are only used to explain the relative position relationship, movement status, etc. between the components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.

[0076] In addition, if there are descriptions involving "first", "second", etc. in the embodiments of the present application, the descriptions of "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or suggesting their relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in the field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by this application.

[0077] Figure 1 The following schematically shows a flow chart of an interface authentication method according to an embodiment of the present application. Figure 1 As shown, the embodiment of the present application provides an interface authentication method, which is applied to a server. The interface authentication method may include the following steps:

[0078] Step 101, receiving an interface access request sent by a client, wherein the interface access request includes a termination token and a first hash token;

[0079] In this embodiment, it should be noted that interface authentication refers to the process of checking the user's authority when accessing the specified interface. The main purpose of interface authentication is to verify whether the requester has the authority to access the specified interface to ensure the security and reliability of the specified interface. In interface authentication, hash chains can be used to generate and verify a series of time-sensitive or sequence-sensitive authentication tokens, thereby enhancing the security of interface access. A hash chain is a data structure in which each node is calculated based on the hash value of the previous node, forming a unidirectional chain structure. The security of the hash chain depends on the unidirectionality of the hash function, that is, it is difficult to reversely derive the previous hash value from a hash value in the hash chain; but forward calculation, that is, calculating the subsequent hash value from a hash value, is easy. This characteristic of the hash chain makes the hash chain an effective security mechanism. In this embodiment, a hash chain-based interface authentication method is provided, which improves the security of interface authentication by utilizing the unidirectional characteristics of the hash chain.

[0080] It should be noted that the hash chain is a chain structure based on the initial token that continuously performs hash calculations to obtain hash values. Each node in the hash chain is the hash value of the previous node, and the hash value corresponding to the last node of the hash chain is the termination token. Any node in the hash chain can obtain a termination token by performing a hash operation through a preset hash function. In this embodiment, the hash chain used for interface authentication is an authentication hash chain, and the hash values ​​corresponding to each node in the authentication hash chain are used as hash tokens, which are used as authentication identifiers during interface authentication. Specifically, the client pre-stores a hash token, that is, a first hash token. When the client needs to access the specified interface of the server, it sends an interface access request to the server by carrying the first hash token, so that the server determines whether the current interface access request is a legitimate request based on the first hash token. Specifically, before accessing the server, the client will apply for or purchase an interface access service on the server. When the client applies for or purchases an interface access service on the server, it will agree with the server on a preset hash algorithm and a termination token. The agreed termination token is the last hash value of the hash chain calculated based on the preset hash algorithm, and the server stores the termination token. The client stores the first hash token corresponding to each node of the calculated hash chain. When the client sends an interface access request to the server, it can carry the first hash token and the termination token to the server. The server can determine whether the current interface access request is legal based on the termination token and the first hash token. Specifically, when the server receives the interface access request sent by the client, it will determine the termination token and the first hash token in the interface access request.

[0081] Step 102, determining a target number of times based on the termination token;

[0082] It should be noted that in some application scenarios, such as paid services, where access times are limited, the number of times a client accesses a designated server interface needs to be limited. In this embodiment, the client pre-applies to the server for a target number of times to access the designated server interface, and accesses the server based on the target number of times.

[0083] Step 103, performing a hash chain operation based on the first hash token and a preset hash function until any hash chain node obtained by the hash chain operation hits a termination token or the number of hash operations included in the hash chain operation reaches a target number;

[0084] It should be noted that the preset hash function can be determined based on the actual application scenario, for example, MD5 (Message-Digest Algorithm 5), SHA-1 (Secure Hash Algorithm 1), SHA-256 (Secure Hash Algorithm 256-bit), etc. Hash chain operation refers to the process of generating the next hash token based on the hash token as input through the preset hash function, and generating the entire hash chain by analogy. Hash operation refers to the process of generating the next hash token through the preset hash function as input. The server also verifies whether the first hash token in the interface access request can hit the termination token and whether the number of accesses corresponding to the interface access request is within the target number. Specifically, the server performs a hash chain operation on the first hash token based on the preset hash function, and the maximum number of hash chain operations is the target number. When the number of operations of the hash chain operation is within the target number, if any hash chain node obtained by the hash chain operation hits the termination token, it can be determined that the first hash token in the interface access request is one of the hash chains agreed with the server. However, in some cases, some illegal users may crack one or more hash tokens in the hash chain through illegal means, that is, the illegal user may obtain the first hash token, and then pretend to be a legitimate user to send an interface access request to the server based on the first hash token. In this embodiment, in order to further improve the security of interface authentication, the interface access request is further verified by a preset number of operations.

[0085] Step 104, when any hash chain node hits the termination token, determining whether the number of hash operations to be determined performed by any hash chain node obtained through the hash chain operation is greater than a preset number of operations;

[0086] Step 105 , when the number of operations to be determined is greater than the preset number of operations, determine that the interface access request is legal, and update the preset number of operations so that the value of the updated preset number of operations is greater than the value of the preset number of operations before the update.

[0087] Specifically, in one embodiment, updating the preset number of operations includes:

[0088] Increase the preset number of operations by one and store it.

[0089] Specifically, in one embodiment, the interface authentication method further includes:

[0090] When the number of hash operations included in the hash chain operation reaches the target number and any hash chain node obtained by the hash chain operation still does not hit the termination token, it is determined that the interface access request is illegal;

[0091] Alternatively, when any hash chain node hits the termination token but the number of operations to be determined is less than or equal to the preset number of operations, the interface access request is determined to be illegal.

[0092] It should be noted that the hash chain function is unidirectional. The hash token corresponding to each node of the hash chain determined based on the preset hash function can continue to perform hash chain operations based on the preset hash function to obtain the hash token corresponding to the node after the node in the hash chain. However, no node can infer the hash token corresponding to the node before the node based on the preset hash function. In this embodiment, after the client applies for access rights for the target number of times from the server, the first hash token of the target number of times will be stored based on the nodes of the hash chain agreed with the server.

[0093] It should be noted that in order to further improve the security of interface authentication, this embodiment expects to limit the client to use all the first hash tokens in reverse order based on the order in the hash chain agreed with the server when using the first hash token, so as to reduce the probability of illegal users calculating the first hash token. For example, the hash chain is ABCDEF, assuming that the termination token is F, and the target number is 5, then the first hash tokens stored by the client are A, B, C, D, and E. Based on the preset hash function, it can be inferred from A to F to obtain all the first hash tokens from A to F; but based on the preset hash function, it is not possible to infer from E to A to obtain any first hash token from F to A. The reverse order is to use D, C, B, and A in sequence starting from E. In this embodiment, the order restriction on the use of the first hash token by the client is realized by presetting the number of operations. The initial value of the preset number of operations is 0. When the first hash token is E, a hash operation based on the preset hash function can hit the termination token F once. At this time, the number of operations to be determined when the first hash token E performs the hash operation is 1. At this time, 1 is greater than the preset number of operations 0, and it can be determined that the interface access request is legal. At this time, the preset number of operations will be updated so that the value of the preset number of operations after the update is greater than the value of the preset number of operations before the update, that is, the preset number of operations after the update will be greater than 0. In this embodiment, the update of the preset number of operations can be based on the preset amplitude. The preset number of operations is superimposed on the preset number of operations. For example, if the preset amplitude is 1, the preset number of operations is increased by one each time it is updated. The preset amplitude can be adaptively adjusted based on the actual application scenario. In this embodiment, the preset number of operations is updated by adding one to the preset number of operations and storing it.

[0094] Furthermore, if the client does not use the first hash token in reverse order, assuming that the client uses the first hash token A for the first time, it can hit the termination token by performing five hash operations based on the preset hash function. At this time, the number of operations to be determined when the first hash token A performs the hash operation is 5. At this time, 5 is greater than the preset number of operations 0, and the interface access request can be determined to be legal. At this time, the preset number of operations will be updated so that the value of the updated preset number of operations is greater than the value of the preset number of operations before the update. That is, the updated preset number of operations will be updated to 1. However, when the client sends an interface access request next time, if the first hash token E is used, the first hash token E can hit the termination token by performing a hash operation based on the preset hash function once, but at this time, the number of operations to be determined when the first hash token E performs the hash operation is 1, and 1 is equal to the updated preset number of operations 1, then the interface access request is determined to be illegal. The client will lose the right to use the first hash token E, that is, the client will lose some resources for interface access. And if the user uses the first hash token A for the first time, after being intercepted by an illegal user, B, C, D, and E can be inferred based on the first hash token A and the preset hash function, and the security of the interface authentication will be threatened to a certain extent. In this embodiment, the order in which the client uses the first hash token is restricted by the preset number of operations, which can improve the security of the interface authentication while ensuring that the client can fully use the interface to access resources.

[0095] Furthermore, when the number of hash operations included in the hash chain operation reaches the target number and any hash chain node obtained by the hash chain operation still does not hit the termination token, the interface access request is determined to be illegal. For example, the authentication hash chain is ABCDEF, assuming that the termination token is F, and the target number is 5, the client performs a hash operation based on any one of the first hash tokens A, B, C, D, and E, and when the number of hash operations reaches 5, the termination token F will definitely be hit. However, if the interface access request is illegal, even if the number of hash operations reaches 5, the termination token F will not be hit.

[0096] In this embodiment, an interface access request sent by a client is received, wherein the interface access request includes a termination token and a first hash token; a target number of times is determined based on the termination token; a hash chain operation is performed based on the first hash token and a preset hash function until any hash chain node obtained by the hash chain operation hits the termination token or the number of hash operations included in the hash chain operation reaches the target number of times; in the case where any hash chain node hits the termination token, it is determined whether the number of hash operations to be determined performed by any hash chain node obtained by the hash chain operation is greater than the preset number of operations; in the case where the number of operations to be determined is greater than the preset number of operations, it is determined that the interface access request is legal, and the preset number of operations is updated so that the value of the updated preset number of operations is greater than the value of the preset number of operations before the update. The number of times the client accesses the server is limited based on the target number of times, the server's control over the interface access is improved, and the interface access request is double-verified based on the hash chain operation and the preset number of operations, while improving the security of interface authentication, ensuring that the client fully uses the interface access resources, and improving the resource utilization of the interface access.

[0097] In one embodiment, before the step of receiving the interface access request sent by the client, the method further includes:

[0098] In response to the access count request received from the client, determine the type of the access count request;

[0099] When the type of the access count application is the first token generation type, obtaining the request count and the termination token in the access count application;

[0100] Determine the target number based on the number of requests;

[0101] Associating and storing the termination token with the target number;

[0102] Initialize the preset number of operations corresponding to the termination token;

[0103] The successful application information of the number of times is returned to the client, and the successful application information of the number of times includes the termination token and the target number of times.

[0104] It should be noted that in some application scenarios, such as paid services, where there is a demand for a limit on the number of accesses, it is necessary to limit the number of times the client accesses the designated interface of the server. The server will only provide the client with resources for interface access after receiving the number of accesses request issued by the client and the application is successful. In this embodiment, by using the hash value corresponding to each node in the hash chain as a hash token, which is used as an authentication identifier during interface authentication, the hash chain is the authentication hash chain, and the authentication hash chain can be generated by the client itself or on the server. The hash chain can be generated by the user based on the number of accesses request issued by the client.

[0105] In the case where the type of access count application is the first token generation type, it is determined that the authentication hash chain is generated by the client itself. The client performs a hash chain operation based on a preset hash function. After obtaining the authentication hash chain, it will generate an access count application based on the termination token corresponding to the authentication hash chain and the number of requests for access to the server's specified interface, and send the access count application to the server. It should be noted that when the client generates the authentication hash chain itself, the server will only receive the termination token. Based on the unidirectionality of the hash chain, the server cannot deduce the hash tokens corresponding to other nodes of the authentication hash chain based on the termination token, which reduces the probability of the server leaking the hash token. The client does not need to consider the server's ability to keep the hash token confidential, thereby further improving the security of the client's interface access.

[0106] It should be noted that when the server receives an access count application from a client and determines that the type of the access count application is the first token generation type, it stores the number of requests and the termination token in the access count application. The server determines the target number of times that can be returned to the client based on the number of requests. For access count applications for paid services, when the server receives the access count application, it will also generate a payment order based on the determined target number of times and send it to the client. After the client completes the payment activity, the termination token in the access count application corresponding to the client will be associated with the target number and stored. The preset number of operations corresponding to the termination token is initialized to ensure that the client can use the purchased complete access resources. The server will also return the number of successful applications to the client, and the number of successful applications will include the termination token and the target number.

[0107] In this embodiment, based on different types of access count applications, the server adopts different client interface access resource management methods, thereby improving the security of interface authentication while improving the ability to meet the diverse needs of the client.

[0108] In one embodiment, the interface authentication method further includes:

[0109] In response to a request for increasing the number of times of a termination token sent by a client, determining the number of times to be increased based on the request for increasing the number of times;

[0110] Update the target number based on the number to be increased;

[0111] The credit limit increase success information is returned to the client, and the credit limit increase success information includes the updated target number of times.

[0112] In this embodiment, it should be noted that the hash chain operation can be performed multiple times, and each hash operation can add a node of the authentication hash chain, that is, the length of the authentication hash chain can be freely limited. In order to improve the adaptability to complex application scenarios, in this embodiment, when performing hash chain operations, an authentication hash chain including more nodes can be generated as much as possible based on actual conditions. When there are enough nodes in the authentication hash chain, after the client uses up the target number of access times in the access times application, the access times can be increased based on the hash tokens corresponding to other nodes of the authentication hash chain. Specifically, for the client to generate the access times application for the authentication hash chain itself, that is, when the type of the access times application is the first token generation type, the client can, after the target number of times is used up, send a request to the server for the number of times of the termination token of the authentication hash chain stored by itself to increase the number of times of the termination token, so as to apply to the server for more interface access times. The server responds to the request for increasing the number of accesses for the termination token received from the client, determines the number of accesses to be increased based on the request, updates the target number based on the number of accesses to be increased, associates and stores the termination token in the access application corresponding to the client with the updated target number, and returns a successful increase message to the client, which includes the updated target number. For access application for paid services, when the server receives the request for increasing the number of accesses, it will also generate a payment order based on the determined number of accesses to be increased, and send it to the client. After the client completes the payment activity, the termination token in the access application corresponding to the client will be associated and stored with the updated target number.

[0113] In this embodiment, based on the controllable length of the hash chain operation, the interface access resources that the client can apply for are flexibly adjusted, the adaptability of the interface authentication is improved, and the occurrence of multiple generation of authentication hash chains corresponding to the same client is reduced. Based on a single authentication hash chain, the client's demand for expanding the quota of interface access resources can be met.

[0114] In one embodiment, the interface authentication method further includes:

[0115] In response to the access count request received from the client, determine the type of the access count request;

[0116] When the type of the access count application is the second token generation type, obtaining the number of requests in the access count application;

[0117] In response to the access count application, a corresponding initial token is generated;

[0118] Performing a hash chain operation based on the initial token and a preset hash function to generate a corresponding authentication hash chain, wherein the number of hash chain nodes included in the authentication hash chain is greater than the number of requests;

[0119] Determine the hash chain node in the authentication hash chain that hits the termination token of the authentication hash chain through the hash chain operation including the request number hash operation as the second hash token;

[0120] Determine the target number based on the number of requests;

[0121] Associating and storing the termination token with the initial token and the target number;

[0122] Initialize the preset number of operations corresponding to the termination token;

[0123] The number of successful application requests is returned to the client, and the number of successful application requests includes the termination token, the target number of times, and the second hash token.

[0124] In this embodiment, it should be noted that, when the type of the access number application is the second token generation type, the authentication hash chain is determined to be generated by the server. The server generates a corresponding initial token in response to the access number application. The initial token can be carried in the access number application, or can be generated based on the code carried by the access number application combined with the timestamp of the time when the access number application is received, or can be generated based on the serial number corresponding to the access number application, etc., and there is no strict restriction. The server performs a hash chain operation based on the initial token and the preset hash function to obtain the authentication hash chain, and then determines the hash chain node in the authentication hash chain that hits the termination token of the authentication hash chain through the hash chain operation including the request number hash operation as the second hash token. For example, the authentication hash chain is ABCDEF, assuming that the termination token is F, the number of requests is 4, and the hash chain operation realized by 4 hash operations in the authentication hash chain can hit the hash chain node of the termination token F of the authentication hash chain is B, and at this time B is determined to be the second hash token.

[0125] It should be noted that when the server generates an authentication hash chain, the server will have the initial token. The server can deduce the hash tokens corresponding to other nodes of the authentication hash chain based on the initial token, thereby improving the flexibility of the server management interface to access resources. The server determines the target number of times that can be returned to the client based on the number of requests. For the access number application for paid services, when the server receives the access number application, it will also generate a payment order based on the determined target number of times and send it to the client. After the client completes the payment activity, the termination token in the access number application corresponding to the client will be associated with the initial token and the target number and stored. The preset number of operations corresponding to the termination token is initialized to ensure that the client can use the purchased complete access resources. The server will also return the number of successful applications to the client, and the number of successful applications includes the termination token, the target number and the second hash token.

[0126] In this embodiment, based on different types of access count applications, the server adopts different client interface access resource management methods, thereby improving the security of interface authentication while improving the ability to meet the diverse needs of the client.

[0127] In one embodiment, the interface authentication method further includes:

[0128] In response to a request for increasing the number of times of a termination token sent by a client, determining the number of times to be increased based on the request for increasing the number of times;

[0129] Update the target number based on the number to be increased;

[0130] Performing a hash chain operation based on the initial token and a preset hash function to generate an authentication hash chain, and determining the hash chain node in the authentication hash chain that hits the termination token of the authentication hash chain through the hash chain operation including the updated target number of hash operations as the third hash token;

[0131] Return the credit limit increase success information to the client, which includes the updated target number and the third hash token.

[0132] In this embodiment, it should be noted that when generating a hash chain operation, an authentication hash chain including more nodes can be generated as much as possible based on actual conditions. When there are enough nodes in the authentication hash chain, after the client uses up the target number of access requests, the number of accesses can be increased based on the hash tokens corresponding to other nodes in the authentication hash chain. Specifically, when the server generates an access request for the authentication hash chain, that is, when the type of the access request is the second token generation type, the client can, after the target number of accesses is used up, send a request to the server for an increase in the number of times the termination token is stored, so as to apply to the server for more interface accesses.

[0133] The server responds to the request for increasing the number of times for the termination token issued by the client, determines the number of times to be increased based on the request for increasing the number of times, updates the target number of times based on the number of times to be increased, performs a hash chain operation based on the initial token and the preset hash function to generate an authentication hash chain, and determines the hash chain node that hits the termination token of the authentication hash chain through the hash chain operation containing the updated target number of hash operations in the authentication hash chain as the third hash token. For example, the authentication hash chain is ABCDEF, assuming that the termination token is F, the updated target number of times is 5, and the hash chain operation that can hit the termination token F of the authentication hash chain through 5 hash operations in the authentication hash chain is A, and A is determined as the third hash token. It can be understood that when the server generates the authentication hash chain for the first time, it can store the entire authentication hash chain, or it can only store the initial token. When receiving the request for increasing the number of times for the termination token issued by the client, the authentication hash chain is regenerated based on the initial token to determine the third hash token.

[0134] Furthermore, the server associates and stores the termination token in the access count application corresponding to the client with the updated target count, and returns a successful increase information to the client, which includes the updated target count and the third hash token. For access count applications for paid services, when the server receives a request for an increase in the count, it will also generate a payment order based on the determined number of times to be increased, and send it to the client. After the client completes the payment activity, the server will associate and store the termination token in the access count application corresponding to the client with the updated target count, and then return a successful increase information to the client, which includes the updated target count and the third hash token.

[0135] It should be noted that the first hash token, the second hash token and the third hash token all refer to hash tokens that can be used for interface authentication. The first, second and third are used to distinguish the method and generation time of the hash tokens.

[0136] In this embodiment, based on the controllable length of the hash chain operation, the interface access resources that the client can apply for are flexibly adjusted, the adaptability of the interface authentication is improved, and the occurrence of multiple generation of authentication hash chains corresponding to the same client is reduced. Based on a single authentication hash chain, the client's demand for expanding the quota of interface access resources can be met.

[0137] Figure 2 The following schematically shows a flow chart of an interface authentication method according to another embodiment of the present application. Figure 2 As shown, the embodiment of the present application provides an interface authentication method, which is applied to a client. The interface authentication method may include the following steps:

[0138] Step 201, determining the type of access number application based on the input access number application requirement;

[0139] Step 202, when the access count application type is the first token generation type, obtain the initial token and request count in the access count application requirement;

[0140] Step 203, performing a hash chain operation based on the initial token and a preset hash function to generate a corresponding authentication hash chain, wherein the number of hash chain nodes included in the authentication hash chain is greater than the number of requests;

[0141] Step 204, determining all hash chain nodes except the termination node in the authentication hash chain as the first hash token;

[0142] Step 205, storing the first hash token and the termination token of the authentication hash chain;

[0143] Step 206, generating an access count application based on the termination token and the request count, and sending the application to a server in an interface authentication method as described in the above embodiment;

[0144] Step 207, when receiving the number of successful application information returned by the server, storing the target number of successful application information;

[0145] Step 208, generating an interface access request based on the stored first hash token and the termination token;

[0146] Step 209: Send the interface access request to the server.

[0147] In this embodiment, it should be noted that when the client interacts with the server, the interface authentication process of the server can refer to the interface authentication method applied to the server. In this embodiment, a hash chain-based interface authentication method is provided, which improves the security of interface authentication by utilizing the one-way characteristics of the hash chain. It should be noted that the hash chain is a chain structure that continuously performs hash calculations based on the initial token to obtain a hash value. Each node in the hash chain is the hash value of the previous node, and the hash value corresponding to the last node of the hash chain is the termination token. Any node in the hash chain can be hashed by a preset hash function to obtain a termination token. In this embodiment, a hash chain is generated as an authentication hash chain by using the input number of application requirements, and the hash values ​​corresponding to each node in the authentication hash chain are used as hash tokens, which are used as authentication identifiers during interface authentication. The authentication hash chain can be generated by the client itself or by the server. The authentication hash chain can be generated based on the input number of application requirements.

[0148] It should be noted that the input number of application requirements is information determined by the user based on actual needs, including the type of desired number of access applications, the initial token, and the number of requests. In the case where the type of number of access applications is the first token generation type, it is determined that the authentication hash chain is generated by the client itself. The client obtains the initial token in the number of application requirements, which can be carried in the number of application requirements, or can be generated based on the code carried by the number of application requirements combined with the timestamp of the time when the number of application requirements is received, or can be generated based on the serial number corresponding to the number of application requirements, etc., and there are no strict restrictions.

[0149] It should be noted that, in one embodiment, the number of application requirements may also include the number of required operations, which includes the number of hash operations performed by the client input according to the number of application requirements, that is, the length of the authentication hash chain may be limited by the number of required operations.

[0150] The client performs a hash chain operation based on the initial token and the preset hash function. After obtaining the authentication hash chain, all hash chain nodes except the termination node in the authentication hash chain are determined as the first hash token, and the termination token and the first hash token are associated and stored. For example, the authentication hash chain is ABCDEF, assuming that the termination token is F, and A, B, C, D, and E are the first hash tokens.

[0151] Furthermore, after the client performs a hash chain operation based on a preset hash function and obtains an authentication hash chain, it will generate an access count application based on the termination token corresponding to the authentication hash chain and the number of requests for accessing the specified interface of the server, and send the access count application to the server. It should be noted that when the client generates the authentication hash chain by itself, the server will only receive the termination token. Based on the unidirectionality of the hash chain, the server cannot calculate the hash tokens corresponding to other nodes of the authentication hash chain based on the termination token, which reduces the probability of the server leaking the hash token. The client does not need to consider the server's ability to keep the hash token confidential, thereby further improving the security of the client's interface access.

[0152] Furthermore, when the server receives the access count application of the first token generation type, it will determine the target number of times that can be used and return it to the client based on the number of requests. For the access count application of the paid service, the server will also generate a payment order based on the determined target number of times and send it to the client. After the client receives the payment order returned by the server, it will generate a payment channel based on the payment order to enable the user to pay. After the client completes the payment activity, the client will receive a successful application information, which includes the termination token and the target number of times.

[0153] In this embodiment, based on different types of access count applications, different hash chain generation methods for interface authentication are adopted to improve the ability to meet diverse client demands.

[0154] In one embodiment, the interface authentication method further includes:

[0155] Determine the number of times to be increased based on the input number of times increase demand;

[0156] Generate a request for increasing the number of times based on the number of times to be increased and send it to the server;

[0157] Accept the credit limit increase success information returned by the server and store the target number of times in the credit limit increase success information.

[0158] In this embodiment, it should be noted that the hash chain operation can be performed multiple times, and each hash operation can add a node of the authentication hash chain, that is, the length of the authentication hash chain can be freely limited. In order to improve the adaptability to complex application scenarios, in this embodiment, when performing the hash chain operation, an authentication hash chain including more nodes can be generated as much as possible based on the actual situation. When there are enough nodes in the authentication hash chain, after the client uses up the target number of times in the access number application, the access number can be increased based on the hash tokens corresponding to other nodes of the authentication hash chain. Specifically, for the client to generate the access number application of the authentication hash chain, that is, when the type of the access number application is the first token generation type, the client can, after the target number of times is used up, send a request for the number of times of the termination token to the server for the stored termination token of the authentication hash chain to apply for more interface access times to the server. Specifically, the number of times to be increased is determined based on the input number of times increase demand, the number of times increase request is generated based on the number of times to be increased, and sent to the server, the success information of the increase returned by the server is accepted, and the target number of times in the success information of the increase is associated with the termination token and stored. For the request to increase the number of paid services, the server will also generate a payment order based on the number of times to be increased and send it to the client. After the client receives the payment order returned by the server, it will generate a payment channel based on the payment order to enable the user to pay. After the client completes the payment activity, the client will receive a successful increase information.

[0159] In this embodiment, based on the controllability of the length of the hash chain operation, the interface access resources that can be applied by the client are flexibly adjusted to improve the adaptability of the interface authentication.

[0160] In one embodiment, the interface authentication method further includes:

[0161] When the access count application type is the second token generation type, obtain the initial token and request count in the access count application requirement;

[0162] Generate access count application based on initial token and request count, and send to server;

[0163] When receiving the number of successful application information returned by the server, storing the termination token, the target number of times and the second hash token in the number of successful application information;

[0164] generating an interface access request based on the second hash token and the termination token;

[0165] Send an interface access request to the server.

[0166] In this embodiment, it should be noted that, when the type of access number application is the second token generation type, it is determined that the authentication hash chain is generated by the server. The client obtains the initial token and the number of requests in the access number application requirement, and generates an access number application based on the initial token and the number of requests, and sends it to the server. The server determines the target number of times that can be used and returns it to the client based on the number of requests in the access number application. For access number applications for paid services, the server will also generate a payment order based on the determined target number of times, and send it to the client. After the client receives the payment order returned by the server, it generates a payment channel based on the payment order to enable the user to pay. After the client completes the payment activity, the client will receive a successful application number information, which includes the termination token and the target number of times and the second hash token.

[0167] It can be understood that the second hash token is a hash chain node of the authentication hash chain generated by the server, which hits the termination token of the authentication hash chain through a hash chain operation including a hash operation of the number of requests. That is, after receiving the second hash token and the determined target number of times, the client can perform a hash chain operation based on a preset hash function to obtain all hash tokens that can be used for interface authentication. Then, based on all the hash tokens that can be used for interface authentication and the termination token, an interface access request is generated and sent to the server.

[0168] In this embodiment, based on different types of access count applications, different hash chain generation methods for interface authentication are adopted to improve the ability to meet diverse client demands.

[0169] In one embodiment, the interface authentication method further includes:

[0170] Determine the number of times to be increased based on the input number of times increase demand;

[0171] Generate a request for increasing the number of times based on the number of times to be increased and send it to the server;

[0172] Accept the credit limit increase success information returned by the server, and store the target number of times and the third hash token in the credit limit increase success information.

[0173] In this embodiment, it should be noted that, specifically, for the application of the number of accesses generated by the server for the authentication hash chain, that is, when the type of the application of the number of accesses is the second token generation type, the client can, after the target number of times is used up, send a request for an increase in the number of times for the stored termination token of the authentication hash chain to the server, so as to apply to the server for more interface access times. Specifically, the number of times to be increased is determined based on the input increase demand, and the request for an increase in the number of times is generated based on the number of times to be increased, and sent to the server, and the increase success information returned by the server is accepted, and the stored termination token is associated with the target number of times in the increase success information and the third hash token and stored. For the request for an increase in the number of times for paid services, the server will also generate a payment order based on the number of times to be increased, and send it to the client. After the client receives the payment order returned by the server, it generates a payment channel based on the payment order to enable the user to pay. After the client completes the payment activity, the client will receive a successful increase information.

[0174] It is understandable that after the server updates the target number of times based on the number of times to be increased, and performs a hash chain operation based on the initial token and the preset hash function to generate an authentication hash chain, the hash chain node that hits the termination token of the authentication hash chain through the hash chain operation containing the updated target number of hash operations in the authentication hash chain is determined as the third hash token. That is, after the client receives the third hash token and the target number of times included in the successful increase information, it can perform a hash chain operation based on the preset hash function to obtain all hash tokens that can be used for interface authentication. Then, based on all the hash tokens that can be used for interface authentication and the termination token, an interface access request is generated and sent to the server.

[0175] In this embodiment, based on the controllability of the length of the hash chain operation, the interface access resources that can be applied by the client are flexibly adjusted to improve the adaptability of the interface authentication.

[0176] The present application also provides a computing device, including:

[0177] a memory configured to store instructions;

[0178] The processor is configured to call instructions from the memory and implement the interface authentication method applied to the server as described in the above embodiment, or the interface authentication method applied to the client as described in the above embodiment when executing the instructions.

[0179] An embodiment of the present application also provides a machine-readable storage medium, on which instructions are stored, and the instructions are used to enable a machine to execute the interface authentication method applied to the server as described in the above embodiment, or the interface authentication method applied to the client as described in the above embodiment.

[0180] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0181] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0182] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0183] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0184] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0185] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0186] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0187] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0188] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. An interface authentication method, characterized in that: Applied to the server, the interface authentication method includes: Receiving an interface access request sent by a client, wherein the interface access request includes a termination token and a first hash token; determining a target number of times based on the termination token; Performing a hash chain operation based on the first hash token and a preset hash function until any hash chain node obtained by the hash chain operation hits the termination token or the number of hash operations included in the hash chain operation reaches the target number; In the case that any of the hash chain nodes hits the termination token, determining whether the number of operations to be determined of the hash operation performed by any of the hash chain nodes obtained by the hash chain operation is greater than a preset number of operations, wherein an initial value of the preset number of operations is 0; When the to-be-determined number of operations is greater than the preset number of operations, the interface access request is determined to be legal, and the preset number of operations is updated so that the updated value of the preset number of operations is greater than the value of the preset number of operations before the update.

2. The interface authentication method according to claim 1, characterized in that: Also includes: In a case where the number of hash operations included in the hash chain operation reaches the target number and any hash chain node obtained by the hash chain operation still does not hit the termination token, determining that the interface access request is illegal; Alternatively, when any of the hash chain nodes hits the termination token but the number of operations to be determined is less than or equal to the preset number of operations, it is determined that the interface access request is illegal.

3. The interface authentication method according to claim 1, characterized in that: The updating of the preset number of operations comprises: The preset number of operations is increased by one and stored.

4. The interface authentication method according to claim 1, characterized in that: Before the step of receiving the interface access request sent by the client, the method further includes: In response to a request for access number received from a client, determine a type of the request for access number; In a case where the type of the access count application is the first token generation type, obtaining the number of requests and the termination token in the access count application; determining a target number of times based on the number of requests; Associating and storing the termination token with the target number of times; Initialize the preset number of operations corresponding to the termination token; Return the number of application success information to the client, and the number of application success information includes the termination token and the target number of times.

5. The interface authentication method according to claim 4, characterized in that: Also includes: In response to a request for increasing the number of times of the termination token sent by the client, determining the number of times to be increased based on the request for increasing the number of times; Updating the target number of times based on the number of times to be increased; Return the credit limit increase success information to the client, wherein the credit limit increase success information includes the updated target number of times.

6. The interface authentication method according to claim 1, characterized in that: Also includes: In response to a request for access number received from a client, determine a type of the request for access number; When the type of the access number application is the second token generation type, obtaining the number of requests in the access number application; In response to the access count, a corresponding initial token is generated; Performing a hash chain operation based on the initial token and the preset hash function to generate a corresponding authentication hash chain, wherein the number of hash chain nodes included in the authentication hash chain is greater than the number of requests; Determine the hash chain node of the authentication hash chain that hits the termination token of the authentication hash chain through the hash chain operation including the request number hash operation as the second hash token; determining a target number of times based on the number of requests; Associating and storing the termination token with the initial token and the target number of times; Initialize the preset number of operations corresponding to the termination token; Return the number of application success information to the client, and the number of application success information includes the termination token, the target number of times and the second hash token.

7. The interface authentication method according to claim 6, characterized in that: Also includes: In response to a request for increasing the number of times of the termination token sent by the client, determining the number of times to be increased based on the request for increasing the number of times; Updating the target number of times based on the number of times to be increased; Performing a hash chain operation based on the initial token and the preset hash function to generate the authentication hash chain, and determining the hash chain node of the authentication hash chain that hits the termination token of the authentication hash chain through the hash chain operation including the updated target number of hash operations as the third hash token; Returning credit limit increase success information to the client, the credit limit increase success information including the updated target number of times and the third hash token.

8. An interface authentication method, characterized in that: Applied to the client, the interface authentication method includes: Determine the type of access request based on the input access request requirement; In the case where the type of the access number application is the first token generation type, obtaining the initial token and the request number in the number application requirement; Performing a hash chain operation based on the initial token and a preset hash function to generate a corresponding authentication hash chain, wherein the number of hash chain nodes included in the authentication hash chain is greater than the number of requests; Determine all hash chain nodes except the termination node in the authentication hash chain as first hash tokens; storing the first hash token and the termination token of the authentication hash chain; Generate an access count application based on the termination token and the request count, and send the application to a server in an interface authentication method according to any one of claims 1 to 7; When receiving the number of successful application information returned by the server, storing the target number of successful application information; generating an interface access request based on the stored first hash token and the termination token; The interface access request is sent to the server.

9. The interface authentication method according to claim 8, characterized in that: Also includes: Determine the number of times to be increased based on the input number of times increase demand; Generate a request for increasing the number of times based on the number of times to be increased, and send it to the server; Accept the credit limit increase success information returned by the server, and store the target number of times in the credit limit increase success information.

10. The interface authentication method according to claim 8, characterized in that: Also includes: In the case where the type of the access number application is the second token generation type, obtaining the initial token and the request number in the number application requirement; Generate an access count application based on the initial token and the request count, and send the application to the server; When receiving the number of successful application information returned by the server, storing the termination token, the target number of times and the second hash token in the number of successful application information; generating an interface access request based on the second hash token and the termination token; The interface access request is sent to the server.

11. The interface authentication method according to claim 10, characterized in that: Also includes: Determine the number of times to be increased based on the input number of times increase demand; Generate a request for increasing the number of times based on the number of times to be increased, and send it to the server; Accept the credit limit increase success information returned by the server, and store the target number of times and the third hash token in the credit limit increase success information.

12. A computing device, characterized in that: include: a memory configured to store instructions; A processor is configured to call the instruction from the memory and implement the interface authentication method according to any one of claims 1 to 7, or the interface authentication method according to any one of claims 8 to 11 when executing the instruction.

13. A machine-readable storage medium, characterized in that: The machine-readable storage medium stores instructions, which are used to enable a machine to execute the interface authentication method according to any one of claims 1 to 7, or the interface authentication method according to any one of claims 8 to 11.

Images