Client verification method and device, electronic equipment and storage medium

Abstract

The invention provides a client verification method and device, electronic equipment and a storage medium, and relates to the technical field of artificial intelligence, in particular to the technical field of deep learning and network security. The specific implementation scheme is as follows: receiving a first verification request sent by a client based on a verification middle page, indicating the client as an abnormal client in response to the first verification request, and sending a first identifier to the client; receiving a first page request sent by a client; in response to the first page request, sending a verification code page to the client, and receiving a second verification request sent by the client based on the verification code page; in response to the fact that the client passes verification of the verification code, sending a second identifier to the client; receiving a second page request sent by the client; and in response to the second page request, sending a page of the to-be-accessed site to the client.

Description

Technical Field

[0001] The present disclosure relates to the field of artificial intelligence technology, specifically to the field of deep learning and network security technology, and more particularly to a client verification method, device, electronic device, and storage medium. Background Art

[0002] Human-machine intelligent recognition refers to the use of computer vision and pattern recognition technology to enable machines to automatically identify, analyze, understand and process human information. In the identification of illegal access by clients, verification codes are often used for verification and identification, and those who pass the verification are identified as legitimate clients. The accuracy of security verification is not high. Summary of the Invention

[0003] The present disclosure provides a client verification method, device, electronic device, and storage medium.

[0004] According to one aspect of the present disclosure, a client verification method is provided, comprising:

[0005] receiving a first verification request sent by a client based on a verification intermediate page, and sending a first identifier to the client in response to the first verification request indicating that the client is an abnormal client;

[0006] receiving a first page request sent by the client, where the first page request includes at least the first identifier;

[0007] In response to the first page request, sending a verification code page to the client, and receiving a second verification request sent by the client based on the verification code page;

[0008] In response to the client passing the verification code verification, sending a second identifier to the client;

[0009] receiving a second page request sent by the client, where the second page request at least includes the second identifier;

[0010] In response to the second page request, a page of the site to be visited is sent to the client.

[0011] According to another aspect of the present disclosure, another client verification method is provided, including:

[0012] Sending a first verification request to a server, and receiving a first identifier sent by the server based on the first verification request;

[0013] Sending a first page request to the server, where the first page request at least includes the first identifier;

[0014] receiving a verification code page sent by the server based on the first page request;

[0015] In response to the verification operation on the verification code page, sending a second verification request to the server, and receiving a second identifier sent by the server based on the second verification request;

[0016] Sending a second page request to the server, where the second page request at least includes the second identifier;

[0017] Receive a page of the site to be visited sent by the server based on the second page request.

[0018] According to a third aspect of the present disclosure, there is provided a client verification device, comprising:

[0019] a first receiving module configured to receive a first verification request sent by a client based on a verification intermediate page, and send a first identifier to the client in response to the first verification request indicating that the client is an abnormal client;

[0020] a second receiving module, configured to receive a first page request sent by the client, where the first page request at least includes the first identifier;

[0021] a first sending module, configured to send a verification code page to the client in response to the first page request, and receive a second verification request sent by the client based on the verification code page;

[0022] A second sending module, configured to send a second identifier to the client in response to the client passing the verification code verification;

[0023] a third receiving module, configured to receive a second page request sent by the client, where the second page request at least includes the second identifier;

[0024] The third sending module is configured to send a page of the site to be visited to the client in response to the second page request.

[0025] According to a fourth aspect of the present disclosure, another client verification device is provided, comprising:

[0026] A first sending module, configured to send a first verification request to a server, and receive a first identifier sent by the server based on the first verification request;

[0027] A second sending module is configured to send a first page request to the server, where the first page request includes at least the first identifier;

[0028] A first receiving module is configured to receive a verification code page sent by the server based on the first page request;

[0029] A second receiving module is configured to send a second verification request to the server in response to the verification operation on the verification code page, and receive a second identifier sent by the server based on the second verification request;

[0030] a third sending module, configured to send a second page request to the server, where the second page request at least includes the second identifier;

[0031] The third receiving module is configured to receive a page of the site to be visited sent by the server based on the second page request.

[0032] According to the fifth aspect of the present disclosure, an electronic device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the method described in the first aspect embodiment or the second aspect embodiment.

[0033] According to a sixth aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to enable the computer to execute the method described in the first aspect embodiment or the second aspect embodiment.

[0034] According to a seventh aspect of the present disclosure, a computer program product is provided, comprising a computer program, which implements the steps of the method described in the first aspect embodiment or the second aspect embodiment when executed by a processor.

[0035] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] The accompanying drawings are provided to facilitate a better understanding of the present invention and do not constitute a limitation of the present disclosure.

[0037] Figure 1 is a schematic diagram of a client verification method provided by an embodiment of the present disclosure;

[0038] Figure 1A This is a schematic diagram of a process of returning to a page of a site to be visited provided by an embodiment of the present disclosure;

[0039] Figure 2 is a schematic diagram of a client verification method provided by an embodiment of the present disclosure;

[0040] Figure 2A This is a schematic diagram of a process for updating a material library provided by an embodiment of the present disclosure;

[0041] Figure 2B This is a flow chart of processing a new request from a client provided by an embodiment of the present disclosure;

[0042] Figure 3 This is a logical diagram of a client verification method provided by an embodiment of the present disclosure;

[0043] Figure 4 is a schematic diagram of another client verification method provided by an embodiment of the present disclosure;

[0044] Figure 5 This is an interactive diagram of a client verification method provided by an embodiment of the present disclosure;

[0045] Figure 6 This is a schematic diagram of the structure of a client verification device provided by an embodiment of the present disclosure;

[0046] Figure 7 It is a structural diagram of another client verification device provided by an embodiment of the present disclosure;

[0047] Figure 8 is a schematic block diagram of an example electronic device for implementing an embodiment of the present disclosure. DETAILED DESCRIPTION

[0048] The following description of exemplary embodiments of the present disclosure is made in conjunction with the accompanying drawings, including various details of the embodiments of the present disclosure to facilitate understanding. These details should be considered as merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present disclosure. Similarly, for the sake of clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.

[0049] Artificial Intelligence (AI) is a new technical science that studies and develops theories, methods, technologies and application systems for simulating, extending and expanding human intelligence. It attempts to understand the essence of intelligence and produce a new intelligent machine that can respond in a similar way to human intelligence.

[0050] Deep learning is a new research direction in machine learning, introduced to bring it closer to its original purpose. Deep learning studies the inherent patterns and representational hierarchies of sample data. The information gained from this learning process is highly helpful in interpreting data such as text, images, and sound. The ultimate goal is to enable robots to acquire human-like analytical learning capabilities and recognize text, images, and sound.

[0051] Cyber ​​Security refers to the protection of the hardware, software and data of a network system from damage, alteration or leakage due to accidental or malicious reasons, ensuring that the system operates continuously, reliably and normally and that network services are not interrupted.

[0052] Figure 1 This is a schematic diagram of a client verification method provided by an embodiment of the present disclosure. Figure 1 As shown, the method includes:

[0053] S101 , receiving a first verification request sent by a client based on a verification intermediate page, and sending a first identifier to the client in response to the first verification request indicating that the client is an abnormal client.

[0054] In some embodiments, the verification intermediate page is a public fully automatic program used to distinguish whether the user is a computer or a human, that is, a function implemented by JavaScript middleware in web page development, which is mainly used to verify user input when the page is loaded; in this embodiment, the client will automatically execute JavaScript and send the client's current environment information to the server at the same time, and the verification intermediate page is the page returned by the server to the browser.

[0055] Optionally, the client may be a program that provides services to users, such as a browser or application. When the client accesses or operates, JavaScript is automatically executed to send a first verification request, which is used to request the server to perform security verification on the client.

[0056] In some embodiments, the server can call an intelligent agent or a pre-trained artificial intelligence model to perform client security identification. For example, based on the client environment information, it determines whether the client has high-frequency request behavior or abnormalities such as the client Internet Protocol (IP) address abnormality. After the server performs abnormal identification on the client based on the first verification request and determines that the client is an abnormal client, it sends a first identifier to the client. The first identifier is used to indicate that the client is an abnormal client to be verified. In this embodiment, the first identifier can be an encrypted verification upgrade cookie.

[0057] S102: Receive a first page request sent by a client.

[0058] In some embodiments, after receiving the first identifier, the client sends a first page request to the server. The first page request includes at least the first identifier. The first page request is used to request page content. The server determines whether to return the page content based on the first identifier in the first page request.

[0059] S103 , in response to the first page request, sending a verification code page to the client, and receiving a second verification request sent by the client based on the verification code page.

[0060] It can be understood that the first page includes the first identifier of the verification upgrade cookie. Therefore, after receiving the first page request from the client, the server will send a verification code page to the client according to the first page request. The client performs verification based on the verification code page and sends a second verification request to the server.

[0061] Optionally, the verification code page includes at least verification code information for verification, and the verification code can be different types of verification methods such as point selection, slider or curve drawing.

[0062] S104: In response to the client passing the verification code verification, sending a second identifier to the client.

[0063] After receiving the second verification request sent by the client based on the verification code page, the verification code entered by the client and carried in the second verification request is identified and verified to determine whether the client passes the verification code verification. When the client passes the verification code verification, a second identifier is sent to the client. In this embodiment, the second identifier can be an encrypted verification cookie.

[0064] In some embodiments, a validity period can be set for the second identification. During the validity period, the client is identified as a verified client, and the client can be directly exempted when requesting a page next time, thereby avoiding multiple repeated verifications in a short period of time.

[0065] In some embodiments, if the server determines that the client is a normal client based on the first verification request, the server may directly send a second identifier to the normal client to identify the client as a client that has passed verification.

[0066] S105: Receive a second page request sent by the client.

[0067] After receiving the second identifier, the client triggers a page refresh and sends a second page request to the server to request page content. The second page request includes at least the second identifier, and the second identifier contains a verified cookie.

[0068] S106 : In response to the second page request, sending the page of the site to be visited to the client.

[0069] It is understandable that when the server receives the second page request, it will determine that the current client is a verified client and send the page information of the site to be visited to the client to improve the security of page access.

[0070] For example, Figure 1AAs shown, when the client is identified as a normal client, the server directly returns to the page of the site to be visited after the identification. When the client is identified as an abnormal client, a verification code page pops up and returns to the page of the site to be visited after the verification is passed.

[0071] In this embodiment, the server receives the first verification request from the client and, when it determines that the client is an abnormal client based on the first verification request, sends a first identifier. The client sends a first page request carrying the first identifier. The server sends a verification code page to the client based on the first page request, and receives a second verification request sent by the client based on the verification code page. If the verification code in the second verification code request passes, the server sends a second identifier to the client to indicate that the verification passes, thereby receiving the client's second page request and returning the page of the site to be visited, thereby improving the browser's access security and verification effect.

[0072] Figure 2 This is a schematic diagram of a client verification method provided by an embodiment of the present disclosure. Figure 2 As shown, the method includes:

[0073] S201 : Receive a first verification request sent by a client based on a verification intermediate page, and send a first identifier to the client in response to the first verification request indicating that the client is an abnormal client.

[0074] In the embodiment of the present disclosure, the implementation method of step S201 can be implemented by using any of the methods in the embodiments of the present disclosure, which is not limited here and will not be described in detail.

[0075] S202: Receive a first page request sent by a client.

[0076] In the embodiment of the present disclosure, the implementation method of step S202 can be implemented by using any of the methods in the embodiments of the present disclosure, which is not limited here and will not be described in detail.

[0077] S203: In response to the first page request, determine the target risk level of the client.

[0078] In some embodiments, the traffic characteristics of the client can be extracted; the traffic characteristics can be characteristic information such as request frequency, device fingerprint, and behavior sequence; based on the traffic characteristics, the target risk level of the user device is determined; for example, the request frequency in the traffic characteristics can be counted, if the client makes high-frequency requests in a short period of time, the risk level of the user device is higher, or the behavior sequence of the user device can be analyzed to determine whether the user device has abnormal behavior and thus determine the risk level of the user device, thereby improving the accuracy of the risk level analysis.

[0079] Optionally, historical traffic characteristics can be obtained to mark risk labels. After obtaining the traffic characteristics of the user device, the traffic characteristics are compared with the historical traffic characteristics to determine the risk level label corresponding to the user device, thereby determining the target risk level of the client.

[0080] S204: Determine a target verification code corresponding to the target risk level.

[0081] In some embodiments, the target verification code type corresponding to the client can be determined according to the target risk level; the business type corresponding to the site to be visited by the client can be determined; and a set of candidate verification code types matching the business type can be determined.

[0082] In some embodiments, the verification code type may include but is not limited to click, slider, image and curve drawing types; if the site to be visited is for ordinary use, such as logging into a social platform, image verification code or slider verification code can be used as a set of candidate verification code types in the current business scenario; if the site to be visited is a transaction page, such as transfer and remittance, curve drawing or click can be used as a set of candidate verification code types in the current business scenario to improve scenario applicability.

[0083] Furthermore, the target verification code type corresponding to the client can be determined from the set of candidate verification code types according to the target risk level; in some embodiments, the difficulty of each verification code type can be differentiated, for example, the verification code types can be divided into different difficulty levels such as simple, complex and expert; when the target risk level is large, the candidate verification code type with a higher difficulty level is determined as the target verification code type, and when the target risk level is small, the candidate verification code type with a lower difficulty level is determined as the target verification code type.

[0084] Furthermore, the target verification code generator can be determined from the candidate verification code generators according to the target verification code type; each verification code generator can correspond to a verification code type, such as a click verification code generator, an image verification code generator, and a slider verification code generator; the target verification code generator is called to generate the target verification code based on the corresponding material grouping. The material grouping refers to the grouping of materials corresponding to different verification code types. Each material grouping includes multiple materials corresponding to the verification code type, thereby improving the verification code generation efficiency.

[0085] In some embodiments, each verification code type can also correspond to a different difficulty level. For example, each verification code type is divided into three levels: low, medium and high. When the target risk level is high, the target verification code generator generates a target verification code of a medium or high level in the target verification code type to improve access security. When the target risk level is low, the target verification code generator generates a target verification code of a medium or low level in the target verification code type to improve user experience.

[0086] Optionally, the material library can be grouped according to the verification code type, and the material library can be managed and updated based on the grouping. For example, image materials, point materials, and curve materials can be grouped for management and update to improve iteration efficiency.

[0087] In some embodiments, it is also possible to determine whether the material library used to generate the verification code meets the update conditions. The update conditions can be determined based on the update cycle. For example, one day is used as an update cycle. When the material library is used for one day, it is determined that the update cycle has been reached, that is, the update conditions are met.

[0088] In response to the material library used to generate the verification code meeting the update conditions, the material library is updated and the updated material library is automatically verified; updating the material library means updating the images or curve drawing line shapes and other materials in the material library to reduce the cost of attack and cracking, and automatically verifying the updated material library, for example, verifying the materials through a neural network to avoid using duplicate materials, or verifying the material encryption signature to ensure that the material has not been tampered with.

[0089] In response to the updated material library passing the verification, the updated material library is grayscale released; grayscale release is a progressive software deployment strategy that gradually opens the new version of the material library to characteristic user groups to achieve smooth transition and risk control.

[0090] In response to the grayscale release results meeting the online requirements, the updated material library will be fully released; that is, if there are no obstacles or other problems after the grayscale release of the updated material library, the updated material library will be fully released to reduce the scope of the fault impact, taking into account both stability and iteration efficiency.

[0091] For example, Figure 2A As shown, based on the length of time the material library is used, it is determined whether the update conditions are met. When the update conditions are met, the new library is downloaded to update the material library. The updated material library is automatically verified and grayscale released after the verification is passed. After the grayscale release is passed, a full release is performed and the material library version record is updated. When the verification fails, an alarm notification is issued to notify staff to intervene to avoid affecting access security verification.

[0092] S205: Determine the verification code page according to the target verification code.

[0093] A verification code page including target verification code verification is generated based on the target verification code, so that the client can perform verification code verification.

[0094] S206: Send a verification code page to the client, and receive a second verification request sent by the client based on the verification code page.

[0095] In the embodiments of the present disclosure, the implementation method of step S206 can be implemented by any one of the embodiments of the present disclosure, which will not be limited here and will not be repeated.

[0096] S207, in response to the verification of the client through the verification code, sending the second identifier to the client.

[0097] In the embodiments of the present disclosure, the implementation method of step S207 can be implemented by any one of the embodiments of the present disclosure, which will not be limited here and will not be repeated.

[0098] S208, receiving the second page request sent by the client.

[0099] In the embodiments of the present disclosure, the implementation method of step S208 can be implemented by any one of the embodiments of the present disclosure, which will not be limited here and will not be repeated.

[0100] S209, in response to the second page request, sending the page of the site to be accessed to the client.

[0101] In some embodiments, a third verification request of the client can also be received, and the request time of the third verification request is determined; the third verification request is a subsequent request of the client, and the request time of the third verification request of the client is determined.

[0102] In some embodiments, in response to the request time still being within the valid period of the second identifier, the client is exempted from verification; that is, the request time of the third verification request is within the valid period of the second identifier, which indicates that the client is still a verified client at this time, and the client is exempted from verification to avoid repeated verification in a short time; in response to the request time not being within the valid period of the second identifier, the client is re-executed the verification code verification; that is, the request time of the third verification request is far away from the last verification time, and the client is re-executed the verification code verification based on the third verification request until the client is verified.

[0103] As shown in the example, after the user equipment is first verified, a second identifier, such as a dynamic cookie, is generated, and a valid period is set for the second identifier. After the user equipment sends a new request, it is checked whether the request time is within the valid period of the second identifier. If the second identifier is not expired, the verification is exempted and the valid period is updated. If the second identifier is expired, the verification process is triggered for verification until the user equipment is verified. Figure 2B

[0104] Optionally, the updated valid period can be 1.5T0, and T0 is the initial valid period.

[0105] ​In some embodiments, in response to the request time being still within the validity period of the second identification, the target risk level of the client is re-determined; that is, although the request time of the third verification request is within the validity period of the second identification, the target risk level of the current client is still determined, and whether to perform verification is determined based on the target risk level to ensure access security.

[0106] Optionally, in response to the re-determined target risk level being greater than the set risk threshold, verification code verification is re-performed on the client; that is, when the target risk level is high, verification code verification is still performed even within the validity period of the second identification; in response to the request time being within the validity period of the second identification, and the re-determined target risk level being less than or equal to the set risk threshold, the client is exempted from verification, that is, when the target risk level is small, the client can be directly exempted from verification to improve access security.

[0107] It can be understood that every time the client passes the verification code verification, a new second identifier is generated for the client; a validity period is configured for the new second identifier, and the new second identifier and the corresponding validity period are sent to the client to determine whether to exempt or re-verify the client's subsequent verification requests, thereby improving verification efficiency.

[0108] In this embodiment, after the server receives the first page request from the client, it determines the target risk level of the client and obtains the target verification code type based on the target risk level, thereby generating the target verification code. Target verification codes of different difficulties are adaptively generated according to the target risk level of the user device, thereby improving the verification effect and access security. When the verification code is generated based on the material library of the automatic update mechanism, the probability of being cracked by access attacks is reduced, security is improved, and a validity period is set for the second identifier after the verification is passed. When other requests are made within the validity period, the verification can be directly exempted, thereby improving the user experience and avoiding repeated verifications in a short period of time, which wastes network resources. After the verification is passed, the page of the site to be visited is returned to the client to ensure the security of the page content.

[0109] Based on the above embodiments, Figure 3 This is a logical diagram of a client verification method provided by an embodiment of the present disclosure. After a client initiates a user request, a risk engine analysis is performed on the client to determine whether the client is an abnormal client. If the client is an abnormal client, a decision is made based on the risk analysis results, and a rebound code strategy is determined. If the rebound code strategy indicates that verification is required, a verification code image is generated from the resource library for return verification. The resource library also has an automatic update mechanism. If the rebound strategy code indicates that verification is exempt, the page of the site to be visited is directly returned to the client.

[0110] Figure 4This is a schematic diagram of another client verification method provided by an embodiment of the present disclosure. Figure 4 As shown, the method includes:

[0111] S401: Send a first verification request to a server, and receive a first identifier sent by the server based on the first verification request.

[0112] S402: Send a first page request to the server.

[0113] S403: Receive a verification code page sent by the server based on the first page request.

[0114] S404: In response to the verification operation on the verification code page, send a second verification request to the server, and receive a second identifier sent by the server based on the second verification request.

[0115] S405: Send a second page request to the server.

[0116] S406: Receive the page of the site to be visited sent by the server based on the second page request.

[0117] In the embodiment of the present disclosure, the implementation method of steps S401-S406 can be implemented by using any method in each embodiment of the present disclosure, which is not limited here and will not be described in detail.

[0118] In this embodiment, the server receives the first verification request from the client and, when it determines that the client is an abnormal client based on the first verification request, sends a first identifier. The client sends a first page request carrying the first identifier. The server sends a verification code page to the client based on the first page request, and receives a second verification request sent by the client based on the verification code page. If the verification code in the second verification code request passes, the server sends a second identifier to the client to indicate that the verification passes, thereby receiving the client's second page request and returning the page of the site to be visited, thereby improving the browser's access security and verification effect.

[0119] Figure 5 This is an interactive diagram of a client verification method provided by an embodiment of the present disclosure. Figure 5 As shown, the method includes:

[0120] S501: The client sends a first verification request to the server based on the verification intermediate page.

[0121] S502: The server performs client verification based on the first verification request, and in response to the client being an abnormal client, sends a first identifier to the client.

[0122] S503: The client sends a first page request to the server.

[0123] S504: The server determines the target risk level of the client based on the first page request.

[0124] S505: Determine a target verification code corresponding to the target risk level.

[0125] S506: Determine the verification code page according to the target verification code.

[0126] S507: The server sends a verification code page to the client.

[0127] S508: The client sends a second verification request to the server based on the verification operation on the verification code page.

[0128] S509: The server performs client verification based on the second verification request, and sends a second identifier to the client in response to the verification being successful.

[0129] S510: The client sends a second page request to the server.

[0130] S511 , based on the second page request, the server determines that the client has passed the authentication and sends the page of the site to be visited to the client.

[0131] In the embodiment of the present disclosure, the implementation method of steps S501-S511 can be implemented in any way in the embodiments of the present disclosure, which is not limited here and will not be described in detail.

[0132] In this embodiment, the server receives the first verification request from the client, and when it determines that the client is an abnormal client based on the first verification request, it sends a first identifier, and the client sends a first page request carrying the first identifier. After the server receives the first page request from the client, it determines the target risk level of the client, and obtains the target verification code type based on the target risk level, thereby generating a target verification code, and adaptively generates target verification codes of different difficulties based on the target risk level of the user device, thereby improving the verification effect and access security; when the verification code is generated based on the material library of the automatic update mechanism, the probability of being cracked by access attacks is reduced, security is improved, and a validity period is set for the second identifier after the verification is passed. When other requests are made within the validity period, verification can be directly exempted, thereby improving user experience, avoiding repeated verifications in a short period of time, and wasting network resources. After the verification is passed, the page of the site to be visited is returned to the client to ensure the security of the page content.

[0133] Figure 6 This is a schematic diagram of the structure of a client verification device provided by an embodiment of the present disclosure. Figure 6 As shown, the client verification device 600 includes:

[0134] A first receiving module 601 is configured to receive a first verification request sent by a client based on a verification intermediate page, and send a first identifier to the client in response to the first verification request indicating that the client is an abnormal client;

[0135] A second receiving module 602 is configured to receive a first page request sent by a client, where the first page request includes at least a first identifier;

[0136] A first sending module 603 is configured to send a verification code page to the client in response to the first page request, and receive a second verification request sent by the client based on the verification code page;

[0137] A second sending module 604 is configured to send a second identifier to the client in response to the client passing the verification code verification;

[0138] A third receiving module 605 is configured to receive a second page request sent by the client, where the second page request includes at least a second identifier;

[0139] The third sending module 606 is configured to send a page of the site to be visited to the client in response to the second page request.

[0140] In some embodiments, the first sending module 603 includes:

[0141] Determine the target risk level for the client;

[0142] Determine the target verification code corresponding to the target risk level;

[0143] Determine the verification code page based on the target verification code;

[0144] Send a verification code page to the client.

[0145] In some embodiments, the first sending module 603 includes:

[0146] Extract client traffic characteristics;

[0147] Determine the target risk level of user devices based on traffic characteristics.

[0148] In some embodiments, the first sending module 603 includes:

[0149] Determine the target verification code type corresponding to the client based on the target risk level;

[0150] Determine a target verification code generator from candidate verification code generators according to the target verification code type;

[0151] The target verification code generator is called to generate a target verification code based on the corresponding material group.

[0152] In some embodiments, the first sending module 603 further comprises:

[0153] determining a service type corresponding to the site to be accessed by the client;

[0154] determining a candidate verification code type set matching the service type;

[0155] determining a target verification code type corresponding to the client from the candidate verification code type set according to the target risk level.

[0156] In some embodiments, the apparatus 600 further comprises:

[0157] updating the material library for generating verification codes in response to the material library satisfying an update condition, and automatically verifying the updated material library;

[0158] gray publishing the updated material library in response to the updated material library passing the verification;

[0159] full publishing the updated material library in response to a publishing result of the gray publishing satisfying an online requirement.

[0160] In some embodiments, the apparatus 600 further comprises:

[0161] grouping the material library according to verification code types, and managing and updating the material library based on the grouping.

[0162] In some embodiments, the apparatus 600 further comprises:

[0163] receiving a third verification request of the client, and determining a request time of the third verification request;

[0164] exempting the client from verification in response to the request time still being within a validity period of the second identifier;

[0165] re-performing verification code verification on the client in response to the request time not being within the validity period of the second identifier.

[0166] In some embodiments, the apparatus 600 further comprises:

[0167] re-determining a target risk level of the client in response to the request time still being within the validity period of the second identifier;

[0168] re-performing verification code verification on the client in response to the re-determined target risk level being greater than a set risk threshold;

[0169] exempting the client from verification in response to the request time being within the validity period of the second identifier and the re-determined target risk level being less than or equal to the set risk threshold.

[0170] In some embodiments, the apparatus 600 further includes:

[0171] Whenever the client passes the verification code verification, a new second identifier is generated for the client;

[0172] Configure a validity period for the new second identifier, and send the new second identifier and the corresponding validity period to the client.

[0173] In this embodiment, the server receives the first verification request from the client and, when it determines that the client is an abnormal client based on the first verification request, sends a first identifier. The client sends a first page request carrying the first identifier. The server sends a verification code page to the client based on the first page request, and receives a second verification request sent by the client based on the verification code page. If the verification code in the second verification code request passes, the server sends a second identifier to the client to indicate that the verification passes, thereby receiving the client's second page request and returning the page of the site to be visited, thereby improving the browser's access security and verification effect.

[0174] Figure 7 This is a schematic diagram of the structure of another client verification device provided by the embodiment of the present disclosure. Figure 7 As shown, the client verification device 700 includes:

[0175] A first sending module 701 is configured to send a first verification request to a server and receive a first identifier sent by the server based on the first verification request;

[0176] A second sending module 702 is configured to send a first page request to a server, where the first page request includes at least a first identifier;

[0177] The first receiving module 703 is configured to receive a verification code page sent by the server based on the first page request;

[0178] The second receiving module 704 is configured to send a second verification request to the server in response to the verification operation on the verification code page, and receive a second identifier sent by the server based on the second verification request;

[0179] A third sending module 705 is configured to send a second page request to the server, where the second page request includes at least a second identifier;

[0180] The third receiving module 706 is configured to receive a page of the site to be visited sent by the server based on the second page request.

[0181] In this embodiment, the server receives the first verification request from the client and, when it determines that the client is an abnormal client based on the first verification request, sends a first identifier. The client sends a first page request carrying the first identifier. The server sends a verification code page to the client based on the first page request, and receives a second verification request sent by the client based on the verification code page. If the verification code in the second verification code request passes, the server sends a second identifier to the client to indicate that the verification passes, thereby receiving the client's second page request and returning the page of the site to be visited, thereby improving the browser's access security and verification effect.

[0182] In the technical solutions disclosed herein, the acquisition, storage, and application of user personal information involved comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0183] According to an embodiment of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium, and a computer program product.

[0184] Figure 8 is a schematic block diagram of an example electronic device used to implement an embodiment of the present disclosure. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are provided as examples only and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0185] like Figure 8 As shown, the device 800 includes a computing unit 801, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 802 or a computer program loaded from a storage unit 808 into a random access memory (RAM) 803. Various programs and data required for the operation of the device 800 can also be stored in the RAM 803. The computing unit 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0186] Various components in device 800 are connected to I / O interface 805, including an input unit 806, such as a keyboard, mouse, etc.; an output unit 807, such as various types of displays, speakers, etc.; a storage unit 808, such as a magnetic disk, optical disk, etc.; and a communication unit 809, such as a network card, modem, wireless communication transceiver, etc. The communication unit 809 allows device 800 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0187] The computing unit 801 can be a variety of general-purpose and / or specialized processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units that run machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 801 performs the various methods and processes described above, such as the client verification method. For example, in some embodiments, the client verification method can be implemented as a computer software program that is tangibly contained in a machine-readable medium, such as the storage unit 808. In some embodiments, part or all of the computer program can be loaded and / or installed on the device 800 via the ROM 802 and / or the communication unit 809. When the computer program is loaded into the RAM 803 and executed by the computing unit 801, one or more steps of the client verification method described above can be performed. Alternatively, in other embodiments, the computing unit 801 can be configured to perform the client verification method by any other suitable means (e.g., by means of firmware).

[0188] Various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system-on-chip systems (SOCs), programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0189] The program code for implementing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that when the program code is executed by the processor or controller, the functions / operations specified in the flow chart and / or block diagram are implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0190] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, device or equipment. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0191] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0192] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), and the Internet.

[0193] A computer system may include a client and a server. The client and server are generally remote from each other and typically interact through a communication network. The client-server relationship arises through computer programs running on the respective computers and having a client-server relationship with each other. The server may be a cloud server, a server in a distributed system, or a server integrated with a blockchain.

[0194] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in this disclosure can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved. This is not limited herein.

[0195] The above specific embodiments do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure shall be included within the scope of protection of this disclosure.

Claims

1. A client authentication method, comprising: receiving a first verification request sent by a client based on a verification intermediate page, and sending a first identifier to the client in response to the first verification request indicating that the client is an abnormal client; receiving a first page request sent by the client, where the first page request includes at least the first identifier; In response to the first page request, sending a verification code page to the client, and receiving a second verification request sent by the client based on the verification code page; In response to the client passing the verification code verification, sending a second identifier to the client; receiving a second page request sent by the client, where the second page request includes at least the second identifier; In response to the second page request, a page of the site to be visited is sent to the client.

2. The method according to claim 1, wherein The sending of the verification code page to the client includes: Determining a target risk level for the client; Determining a target verification code corresponding to the target risk level; Determining the verification code page according to the target verification code; Send a verification code page to the client.

3. The method according to claim 2, wherein: Determining the target risk level of the client includes: Extracting traffic characteristics of the client; A target risk level of the user equipment is determined according to the traffic characteristics.

4. The method according to claim 2, wherein: Determining the target verification code of the client according to the target risk level includes: Determining a target verification code type corresponding to the client according to the target risk level; Determining a target verification code generator from candidate verification code generators according to the target verification code type; The target verification code generator is called to generate the target verification code based on the corresponding material group.

5. The method according to claim 4, wherein The determining, according to the target risk level, a target verification code type corresponding to the client further includes: Determining the service type corresponding to the site to be accessed by the client; Determining a set of candidate verification code types that match the business type; According to the target risk level, a target verification code type corresponding to the client is determined from the candidate verification code type set.

6. The method according to claim 5, wherein: The method further comprises: In response to a material library for generating a verification code meeting an update condition, updating the material library and automatically verifying the updated material library; In response to the updated material library passing the verification, performing a phased release on the updated material library; In response to the release result of the phased release meeting the online requirements, the updated material library is fully released.

7. The method according to claim 6, wherein: The method further comprises: The material library is grouped according to the verification code type, and the material library is managed and updated based on the grouping.

8. The method according to any one of claims 1 to 7, wherein: The method further comprises: receiving a third verification request from the client, and determining a request time of the third verification request; In response to the request time still being within the validity period of the second identifier, exempting the client from verification; In response to the request time not being within the validity period of the second identifier, re-performing verification code verification on the client.

9. The method according to claim 8, wherein: The method further comprises: In response to the request time still being within the validity period of the second identifier, re-determining the target risk level of the client; In response to the re-determined target risk level being greater than a set risk threshold, re-performing verification code verification on the client; In response to the request time being within the validity period of the second identifier and the re-determined target risk level being less than or equal to the set risk threshold, the client is exempted from verification.

10. The method according to claim 9, wherein: The method further comprises: Whenever the client passes the verification code verification, a new second identifier is generated for the client; A validity period is configured for the new second identifier, and the new second identifier and the corresponding validity period are sent to the client.

11. A client authentication method, wherein: The method comprises: Sending a first verification request to a server, and receiving a first identifier sent by the server based on the first verification request; Sending a first page request to the server, where the first page request includes at least the first identifier; Receiving a verification code page sent by the server based on the first page request; In response to the verification operation on the verification code page, sending a second verification request to the server, and receiving a second identifier sent by the server based on the second verification request; Sending a second page request to the server, where the second page request at least includes the second identifier; Receive a page of the site to be visited sent by the server based on the second page request.

12. A client verification device, comprising: a first receiving module configured to receive a first verification request sent by a client based on a verification intermediate page, and send a first identifier to the client in response to the first verification request indicating that the client is an abnormal client; a second receiving module, configured to receive a first page request sent by the client, where the first page request at least includes the first identifier; a first sending module, configured to send a verification code page to the client in response to the first page request, and receive a second verification request sent by the client based on the verification code page; A second sending module, configured to send a second identifier to the client in response to the client passing the verification code verification; a third receiving module, configured to receive a second page request sent by the client, where the second page request at least includes the second identifier; The third sending module is configured to send a page of the site to be visited to the client in response to the second page request.

13. A client verification device, comprising: A first sending module, configured to send a first verification request to a server, and receive a first identifier sent by the server based on the first verification request; A second sending module is configured to send a first page request to the server, where the first page request includes at least the first identifier; A first receiving module is configured to receive a verification code page sent by the server based on the first page request; A second receiving module is configured to send a second verification request to the server in response to the verification operation on the verification code page, and receive a second identifier sent by the server based on the second verification request; a third sending module, configured to send a second page request to the server, where the second page request at least includes the second identifier; The third receiving module is configured to receive a page of the site to be visited sent by the server based on the second page request.

14. An electronic device comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 10 or 11.

15. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to cause the computer to execute the method according to any one of claims 1-10 or 11.

16. A computer program product comprising a computer program, which, when executed by a processor, implements the steps of the method according to any one of claims 1 to 10 or 11.

Images