Login verification method and device, storage medium and electronic equipment

Abstract

The application discloses a login verification method and device, a storage medium and an electronic device. The method comprises the following steps: obtaining a login verification request for requesting to log in a current service client by using a target user account in the current service client; sending the login verification request to a reference service client cluster associated with the current service client; receiving a verification response result returned by a reference service client in the reference service client cluster; determining a current security verification level corresponding to the current service client according to the verification response result, and starting a service function permission corresponding to the current security verification level for the current service client logged in by using the target user account. The application solves the technical problem of low security caused by the existing technology of using a local login verification mode for a mobile terminal in the case that the networking state of a server and the mobile terminal is poor.

Description

Technical Field

[0001] This application relates to the field of computers, and more specifically, to a login authentication method and apparatus, a storage medium, and an electronic device. Background Technology

[0002] In scheduling systems used to schedule various mobile terminals, in order to ensure the legitimacy of each mobile terminal's operation, each mobile terminal is often required to log in to the installed scheduling client first, and only after the user's identity is verified can it be allowed to interact with the server to complete the scheduling task.

[0003] Regarding the login verification process for mobile terminals, if the mobile terminal's connection to the server is poor, the common approach is to perform local verification after logging into the local client with an account, in order to access business data stored on the local mobile terminal. However, in this method, the local verification is easily tampered with, making it difficult to ensure the security of local verification in offline situations.

[0004] There is currently no effective solution to the above problems. Summary of the Invention

[0005] This application provides a login verification method and apparatus, storage medium and electronic device to at least solve the technical problem of low security caused by the existing technology of using local login verification for mobile terminals when the network connection between the server and the mobile terminal is poor.

[0006] According to one aspect of the embodiments of this application, a login verification method is provided, comprising: obtaining a login verification request triggered in a current business client, wherein the login verification request is used to request to log in to the current business client using a target user account; sending the login verification request to a reference business client cluster associated with the current business client, wherein the reference business clients in the reference business client cluster are located in the same distributed business verification network as the current business client, and the reference business clients record verification information for verifying the current business client;

[0007] Optionally, determining the current security verification level corresponding to the current business client based on the verification response result includes: parsing the verification result obtained from the reference business client from the verification response result; statistically analyzing the verification results of each reference business client in the reference business client cluster to obtain the current verification pass rate; and determining the current security verification level corresponding to the current business client based on the current online rate of the reference business clients in the reference business client cluster and the current verification pass rate.

[0008] Optionally, determining the current security verification level corresponding to the current business client based on the current online rate and the current verification pass rate of the reference business clients in the reference business client cluster includes: when the current online rate is greater than a first online threshold and the current verification pass rate is greater than a first pass threshold, determining the current security verification level as a first security level, wherein the first security level indicates that all business function permissions in the current business client are enabled; when the current online rate is greater than a second online threshold and the current verification pass rate is greater than a second pass threshold, determining the current security verification level as a second security level, wherein the second security level indicates that some business function permissions in the current business client are enabled. The service function permissions include: data read-only permission and sensitive business data processing permission; when the current online rate is greater than the third online threshold and the current verification pass rate is greater than the third pass threshold, the current security verification level is determined to be the third security level. The third security level indicates that certain service function permissions in the current business client are enabled. These certain service function permissions include: data read-only permission and non-sensitive business data processing permission; wherein the first online threshold is greater than the second online threshold, the second online threshold is greater than the third online threshold; the first pass threshold is greater than the second pass threshold, the second pass threshold is greater than the third pass threshold; and the scope of the sensitive business data processing permission is greater than the scope of the non-sensitive business data processing permission.

[0009] Optionally, according to the method described in claim 1, the step of sending the login verification request to the reference business client cluster associated with the current business client includes: in the case that the current business client fails to connect to the server, reading the network access address corresponding to each of the reference business clients in the reference business client cluster from the configuration file in the current business client; and sending the login verification request to the network access address.

[0010] Optionally, sending the login verification request to the network access address includes: obtaining the online status of each reference service client in the reference service client cluster; and, if the online rate of the reference service client cluster is determined to be greater than the verification trigger condition threshold based on the online status, broadcasting the login verification request to each of the network access addresses via an end-to-end protocol, wherein the login verification request includes the login information of the target user account encrypted with a key.

[0011] Optionally, after granting the business function permissions corresponding to the current security verification level to the current business client logged in using the target user account, the method further includes: receiving an object login authentication request sent by an object reference business client in the reference business client cluster, wherein the object login authentication request is used to request to log in to the object reference business client using an object user account; parsing the login information of the object user account from the object login authentication request; and verifying the login information of the object user account.

[0012] Optionally, before obtaining the login verification request triggered in the current business client, the method further includes: obtaining the login registration request triggered in the current business client; if the current business client is connected to the server, sending the login registration request to the server, wherein the server will assign a current network access address to the current business client and send the login information of the current business client to the reference business client located in the same distributed business verification network, the login information of the current business client including the current network access address; and saving the current network access address received from the server.

[0013] According to another aspect of the embodiments of this application, a login verification apparatus is also provided, comprising: a first acquisition unit, configured to acquire a login verification request triggered in a current business client, wherein the login verification request is used to request login to the current business client using a target user account; a sending unit, configured to send the login verification request to a reference business client cluster associated with the current business client, wherein the reference business clients in the reference business client cluster are located in the same distributed business verification network as the current business client, and the reference business clients record verification information for verifying the current business client; a receiving unit, configured to receive a verification response result returned by the reference business clients in the reference business client cluster; and a verification processing unit, configured to determine the current security verification level corresponding to the current business client based on the verification response result, and to enable business function permissions corresponding to the current security verification level for the current business client logged in using the target user account.

[0014] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer-readable storage medium, and the computer program is configured to execute the above-described login verification method when running.

[0015] According to another aspect of the embodiments of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to perform the login verification method described above through the computer program.

[0016] In this embodiment, a login verification request triggered in the current business client is obtained, whereby the login verification request requests login to the current business client using a target user account. Then, the login verification request is sent to a cluster of reference business clients associated with the current business client. The reference business clients in the cluster are located in the same distributed business verification network as the current business client, and each reference business client records verification information used to verify the current business client. Next, the verification response result returned by the reference business clients in the cluster is received. Furthermore, based on the verification response result, the current security verification level corresponding to the current business client is determined, and business function permissions corresponding to the current security verification level are granted to the current business client logging in using the target user account. In other words, in this embodiment, when the network condition between the current business client and the login verification server is poor, cloud login verification is performed on the user account corresponding to the current business client based on multiple reference business clients located in the same distributed business verification network as the current business client. This avoids the technical problem of low login verification security caused by the current business client performing local login verification itself, thus achieving the technical effect of improving login verification security. Attached Figure Description

[0017] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0018] Figure 1 This is a flowchart of an optional login verification method according to an embodiment of this application;

[0019] Figure 2 This is a schematic diagram of an optional login verification method according to an embodiment of this application;

[0020] Figure 3 This is a schematic diagram of another optional login verification method according to an embodiment of this application;

[0021] Figure 4 A schematic diagram of another optional login verification method according to an embodiment of this application;

[0022] Figure 5 A schematic diagram of another optional login verification method according to an embodiment of this application;

[0023] Figure 6 This is a schematic diagram of an optional login verification device according to an embodiment of this application;

[0024] Figure 7 This is a schematic diagram of the structure of an optional electronic device according to an embodiment of this application. Detailed Implementation

[0025] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0026] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0027] Alternatively, as an alternative implementation method, such as Figure 1 As shown, the login verification methods mentioned above include:

[0028] S102, obtain the login verification request triggered in the current business client, wherein the login verification request is used to request to log in to the current business client using the target user account;

[0029] It should be noted that the login verification method described above can be applied, but is not limited to, scenarios where login verification of the user account corresponding to the current business client is required when the network condition between the current business client and the server is poor. For example, in a scheduling system that schedules various business clients, there is a scenario where login verification of the user account corresponding to the current business client is required when the network condition between the current business client and the server is poor.

[0030] Taking the login verification method described above as an example of verifying the login of a user account corresponding to the current business client, the "current business client" here can be, but is not limited to, the business client that the user account to be verified wants to log in to. The target user account mentioned above is the user account to be verified.

[0031] Furthermore, a login verification request can be triggered in the current business client in the following ways, but not limited to: triggering the login control after the user enters the user's account name, password, and verification code in the current business client.

[0032] S104, send the login verification request to the reference business client cluster associated with the current business client. The reference business client in the reference business client cluster is located in the same distributed business verification network as the current business client. The reference business client records the verification information used to verify the current business client.

[0033] Optionally, as an alternative embodiment, the distributed service verification network here may be, but is not limited to, a decentralized distributed network. Specifically, the distributed service verification network may include, but is not limited to, multiple service clients, wherein each of the multiple service clients stores attribute information (such as name, ID, network address, public key information, etc.) corresponding to all service clients in the distributed service verification network.

[0034] Furthermore, the reference business client cluster associated with the current business client here can, but is not limited to, refer to a cluster of business clients other than the current business client itself within the distributed business verification network where the current business client resides. The reference business client here can, but is not limited to, refer to the business clients within the reference business client cluster.

[0035] For example, such as Figure 2 As shown, assume the distributed business verification network includes 5 business clients (i.e., business client A, business client B, business client C, business client D, and business client E). Assume business client A detects a login verification request triggered by a target user account. Business client A is the current business client mentioned above, while business clients B, C, D, and E are the reference business clients mentioned above. The business client cluster composed of business clients B, C, D, and E is the reference business client cluster mentioned above.

[0036] It should be noted that the login verification request mentioned above may, but is not limited to, carry encrypted attribute information of the target user account to be verified (such as user account nickname, user account ID, user account login password, etc.). The verification information mentioned above may, but is limited to, indicating the correct attribute information of the target user account pre-stored in the reference business client (such as user account nickname, user account ID, user account login password, whether the user account has an illegal account flag, etc.).

[0037] S106, Receive the verification response result returned by the reference service client in the reference service client cluster;

[0038] Suppose the login verification method described above is applied to a scenario where the user account corresponding to the current business client is being verified. The verification response result here can be, but is not limited to, an indication of the verification result obtained after the reference business client verifies the information carried in the login verification request. Specifically, the verification result here is used to indicate whether the target user account has passed the verification by the reference business client.

[0039] S108. Determine the current security verification level corresponding to the current business client based on the verification response result, and enable the business function permissions corresponding to the current security verification level for the current business client that logs in using the target user account.

[0040] It should be noted that business clients may correspond to multiple security verification levels, and different security verification levels correspond to different business function permissions.

[0041] The above login verification method is applied to a scenario where the network connection between the current business client and the server is poor, and login verification is required for the user account corresponding to the current business client. The following steps will provide a complete explanation of the method:

[0042] Still Figure 2 As shown in (a), assume the current business client is business client A. When business client A detects the input of the target user's account and password to be verified, as well as the selection of the login control, it obtains the attribute information of the target user's account to be verified (i.e., the login information of the target user's account, such as the user account and the user account password).

[0043] Next, the attribute information to be verified (i.e., the login information of the target user account) is encrypted and then encapsulated within the login verification request. Then, as follows... Figure 2As shown in (a), login verification requests are sent to business clients B, C, D, and E respectively. This causes business clients B, C, D, and E to respectively verify the target user account through the login verification request, obtaining verification response results B, C, D, and E, respectively. Figure 2 As shown in (b), the verification response result B, the business client C, the verification response result D, and the verification response result E are returned to the client A.

[0044] Then, after business client A obtains verification response results B, business client C, verification response results D, and verification response results E, the current security verification level corresponding to business client A is determined based on verification response results B, business client C, verification response results D, and verification response results E, and business function permissions corresponding to the current security verification level are enabled for the current business client.

[0045] In this embodiment, a login verification request triggered in the current business client is obtained, whereby the login verification request requests login to the current business client using a target user account. Next, the login verification request is sent to a cluster of reference business clients associated with the current business client. These reference business clients are located in the same distributed business verification network as the current business client, and each reference business client records verification information used to verify the current business client. Then, the verification response result returned by the reference business clients in the cluster is received. Furthermore, based on the verification response result, the current security verification level corresponding to the current business client is determined, and business function permissions corresponding to the current security verification level are granted to the current business client logging in using the target user account. In other words, in this embodiment, even when the network condition between the current business client and the login verification server is poor, cloud login verification can be performed on the user account corresponding to the current business client based on multiple reference business clients located in the same distributed business verification network. This avoids the technical problem of low login verification security caused by the current business client performing local login verification itself, thus achieving the technical effect of improving login verification security.

[0046] Optionally, as an optional implementation method, determining the current security verification level corresponding to the current business client based on the verification response result includes:

[0047] S1, Parse the verification result obtained from the reference business client from the verification response result;

[0048] It should be noted that the verification result here can be, but is not limited to, the verification result used by the reference business client to verify the login of the target user account. Specifically, if the target user account passes the login verification, the verification result can be "passed"; if the target user account fails the login verification, the verification result can be "failed".

[0049] S2, Statistically analyze the verification results of each reference service client in the reference service client cluster to obtain the current verification pass rate;

[0050] Taking the login verification method described above as an example of verifying the login of a user account corresponding to the current business client, the above statistical analysis of the verification results of each reference business client in the reference business client cluster to obtain the current verification pass rate may include, but is not limited to, the following steps: calculating the proportion of reference business clients whose verification results are passed, and using this proportion as the current verification pass rate. Specifically, the proportion of reference business clients whose verification results are passed is the ratio of the number of reference business clients with passed verification results to the total number of reference business clients.

[0051] For example, suppose the reference business clients corresponding to the current business client include: Reference Business Client 1, Reference Business Client 2, Reference Business Client 3, Reference Business Client 4, and Reference Business Client 5. The verification result for Reference Business Client 1 is passed, the verification result for Reference Business Client 2 is failed, the verification result for Reference Business Client 3 is passed, the verification result for Reference Business Client 4 is passed, and the verification result for Reference Business Client 5 is passed. Therefore, the number of reference business clients with passed verification is 4, and the total number of reference business clients is 5. Thus, the current verification pass rate = (4 ÷ 5) × 100% = 80%.

[0052] S3. Based on the current online rate and current verification pass rate of the reference business clients in the reference business client cluster, determine the current security verification level corresponding to the current business client.

[0053] Optionally, as an alternative implementation, the current online rate here can be used, but is not limited to, to indicate the proportion of reference service clients whose running status is online. Specifically, the current online rate of reference service clients can be obtained based on, but is not limited to, the following steps: counting the total number of all reference service clients and the number of reference service clients that have returned running status information; obtaining the ratio of the number of reference service clients that have returned running status information to the total number of all reference service clients; and using the ratio as the current online rate of reference service clients.

[0054] Furthermore, assuming the above login verification method is applied to a scenario of verifying login to the user account corresponding to the current business client, the following steps will provide a complete explanation of the method:

[0055] The verification response results returned by each reference service client in the reference service client cluster are analyzed to obtain the verification result corresponding to each reference service client. Next, the ratio of the number of reference service clients in the reference service client cluster whose verification results are passed to the total number of reference service clients in the cluster is obtained, and this ratio is used as the current verification pass rate. The ratio of the number of reference service clients in the reference service client cluster that returned running status information to the total number of reference service clients in the cluster is obtained, and this ratio is used as the current online rate of the reference service clients. Finally, based on the current verification pass rate and the current online rate of the reference service clients, the current security verification level corresponding to the current service client is determined.

[0056] It should be noted that, without considering the current security verification level of the current business client (i.e., all business clients have the same business function permissions), if the verification pass rate is greater than 51%, the target user account is determined to have passed the login verification.

[0057] In this embodiment, the verification result obtained by the reference service client is parsed from the verification response result. The verification results of each reference service client in the reference service client cluster are statistically analyzed to obtain the current verification pass rate. Then, based on the current online rate and current verification pass rate of the reference service clients in the reference service client cluster, the current security verification level corresponding to the current service client is determined. In other words, in this embodiment, the current security verification level corresponding to the current service client is determined by the current verification pass rate and current online rate of the reference service clients. This avoids the problem of inaccurate current security verification level corresponding to the current service client due to an insufficient number of reference service clients participating in the verification, or due to verification failures of individual reference service clients among the participating reference service clients. Thus, the technical effect of improving the accuracy of the current security verification level corresponding to the current service client is achieved.

[0058] Optionally, as an optional implementation, the current security verification level corresponding to the current business client is determined based on the current online rate and current verification pass rate of the reference business clients in the reference business client cluster, including:

[0059] S1, if the current online rate is greater than the first online threshold and the current verification pass rate is greater than the first pass threshold, determine the current security verification level as the first security level, wherein the first security level indicates that all business function permissions in the current business client are enabled;

[0060] For example, suppose the first online threshold is 80%, and the first pass threshold is 80%. If the online rate is greater than 80%, and the current verification pass rate is greater than 80%, then the current security verification level for the current business client is determined to be the first security level. The current business client can then operate on all business functions.

[0061] S2, if the current online rate is greater than the second online threshold and the current verification pass rate is greater than the second pass threshold, determine the current security verification level as the second security level. The second security level indicates that some business function permissions in the current business client are enabled. Some business function permissions include: data read-only permission and sensitive business data processing permission.

[0062] For example, suppose the second online threshold is 65%, and the second pass threshold is 65%. If the online rate is greater than 65%, and the current verification pass rate is greater than 65%, then the current security verification level for the current business client is determined to be the second security level. The current business client can view business functions and process sensitive business data.

[0063] S3, if the current online rate is greater than the third online threshold and the current verification pass rate is greater than the third pass threshold, determine the current security verification level as the third security level. The third security level indicates that some business function permissions in the current business client are enabled. Some business function permissions include: data read-only permission and non-sensitive business data processing permission.

[0064] For example, suppose the third online threshold is 50%, and the third pass threshold is 50%. If the online rate is greater than 50%, and the current verification pass rate is greater than 50%, then the current security verification level for the current business client is determined to be the third security level. The current business client can view business functions and process non-sensitive business data.

[0065] Among them, the first online threshold is greater than the second online threshold, and the second online threshold is greater than the third online threshold; the first pass threshold is greater than the second pass threshold, and the second pass threshold is greater than the third pass threshold; the scope of the permission for sensitive business data processing is greater than the scope of the permission for non-sensitive business data processing.

[0066] It should be noted that the above embodiments are merely one example for explaining the login verification method. The first online threshold, the second online threshold, the third online threshold, and the first pass threshold, the second pass threshold, and the third pass threshold can correspond to other values, and are not limited to the values ​​in the above embodiments. No limitations are imposed in this application embodiment.

[0067] In addition, it should be noted that the current security level of the current business client corresponding to the target user account verified through the central service can also be the first security level.

[0068] In the application embodiment, when the current online rate is greater than a first online threshold and the current verification pass rate is greater than a first pass threshold, the current security verification level is determined to be a first security level, wherein the first security level indicates that all business function permissions in the current business client are enabled. When the current online rate is greater than a second online threshold and the current verification pass rate is greater than a second pass threshold, the current security verification level is determined to be a second security level, wherein the second security level indicates that some business function permissions in the current business client are enabled, including: data read-only permissions and sensitive business data processing permissions. When the current online rate is greater than a third online threshold and the current verification pass rate is greater than a third pass threshold, the current security verification level is determined to be a third security level, wherein the third security level indicates that some business function permissions in the current business client are enabled, including: data read-only permissions and non-sensitive business data processing permissions. The first online threshold is greater than the second online threshold, the second online threshold is greater than the third online threshold; the first pass threshold is greater than the second pass threshold, the second pass threshold is greater than the third pass threshold; and the scope of the sensitive business data processing permissions is greater than the scope of the non-sensitive business data processing permissions. In other words, in this embodiment, the current security verification level is determined for the current business client based on the relationship between the current online rate, the current verification pass rate, and a predetermined threshold. This allows the current business client to obtain the operation permissions indicated by the current security verification level. In other words, by assigning different operation permissions to business clients with different security verification levels, this embodiment avoids the technical problem of reduced business security caused by business clients with lower security verification levels obtaining too many operation permissions. This achieves the technical effect of improving the security of business processing.

[0069] Optionally, as an optional implementation, sending the login verification request to a cluster of reference business clients associated with the current business client includes:

[0070] S1, In the event that the current business client fails to connect to the server, read the network access address corresponding to each reference business client in the reference business client cluster from the configuration file in the current business client.

[0071] It should be noted that before reading the network access addresses of each reference business client in the reference business client cluster from the configuration file in the current business client, the process also includes: pre-storing the network access addresses of all reference business clients in the reference business cluster in the current business client.

[0072] Furthermore, as an optional implementation, before reading the network access addresses corresponding to each reference business client in the reference business client cluster from the configuration file within the current business client, the method further includes: modifying the configuration file within the current business client and instructing that, in the event that the current business client fails to connect to the server, it should perform login verification through the user account to be verified by a reference business client that exists in the same distributed business verification network; and in the event that the current business client successfully connects to the server, it should perform login verification through the server for the user account to be verified.

[0073] In other words, this embodiment, by pre-configuring the configuration file of the current business client, automatically sends a login verification request to a reference business client when the business client fails to connect to the server. The reference business client then verifies the user account to be verified. This avoids the technical problem of low login verification security caused by the current business client performing local login verification based on its own user account when the current business client fails to connect to the server. Thus, the technical effect of improving login verification security is achieved.

[0074] As an alternative embodiment, in cases where network connectivity between the server and the current business client frequently fails, the configuration file within the current business client can be modified to instruct a reference business client, located in the same distributed business authentication network as the current business client, to perform login verification for the user account corresponding to the current business client. Furthermore, when the network connection between the server and the current business client is stable, the configuration file within the current business client can be modified to instruct the server to perform login verification for the user account corresponding to the current business client.

[0075] Suppose the configuration file within the current business client is modified in advance, instructing a reference business client, located in the same distributed business authentication network as the current business client, to perform login authentication for the user account corresponding to the current business client. Then, if the current business client detects login authentication, regardless of the network condition between the current business client and the server, the current business client will send the login authentication request to the reference business client, which will then perform the login authentication for the target user account. Furthermore, suppose the configuration file within the current business client is modified in advance, instructing a server, located in the same distributed business authentication network as the current business client, to perform login authentication for the user account corresponding to the current business client. Then, if the current business client detects login authentication, regardless of the network condition between the current business client and the server, the current business client will send the login authentication request to the server, which will then perform the login authentication for the target user account.

[0076] In other words, this embodiment provides multiple verification methods for the user accounts corresponding to the client by modifying the configuration file. This solves the technical problem in existing technologies where login verification is limited to a single method due to the reliance on server-side verification. Thus, it achieves the technical effect of enriching login verification methods.

[0077] S2 sends a login verification request to the network access address.

[0078] In the embodiment of the application, when the current business client fails to connect to the server, the network access address corresponding to each reference business client in the reference business client cluster is read from the configuration file within the current business client. Then, a login verification request is sent to the network access address. In other words, in this embodiment, by pre-modifying the configuration file within the current business client, in the event of a connection failure between the current business client and the server, the current business client automatically reads the network address corresponding to each reference business client in the reference business client cluster and sends a login verification request to the aforementioned network address. This avoids the technical problem of low login verification security caused by the current business client performing local login verification based on its own user account when the connection between the current business client and the server fails. Thus, the technical effect of improving login verification security is achieved.

[0079] Optionally, as an optional implementation, sending a login verification request to a network access address includes:

[0080] S1, obtain the online status of each reference service client in the reference service client cluster;

[0081] Optionally, even when a reference service client is offline, it can still return information such as its running status to the current service client. The current service client can, but is not limited to, determine the current online rate of the reference service client based on the running status information returned by the reference service client. Specifically, the number of all reference service clients and the number of reference service clients whose running status is returned as online are counted. The ratio of the number of reference service clients whose running status is returned as online to the total number of all reference service clients is obtained, and this ratio is used as the current online rate of the reference service client.

[0082] Furthermore, when the reference service client is offline and unable to return any information to the current service client, the current service client can, but is not limited to, obtain the current online rate of the reference service client based on the following steps: Specifically, count the total number of all reference service clients and the number of reference service clients that have returned runtime status information. Obtain the ratio of the number of reference service clients that have returned runtime status information to the total number of all reference service clients. Use this ratio as the current online rate of the reference service client.

[0083] S2, if the online rate of the reference service client cluster is determined to be greater than the verification trigger threshold based on the online status, a login verification request is broadcast to each network access address through an end-to-end protocol. The login verification request includes the login information of the target user account encrypted with a key.

[0084] It should be noted that the end-to-end protocol here can be used, but is not limited to, to refer to the peer-to-peer (P2P) network protocol, which is a decentralized peer-to-peer network protocol.

[0085] Taking the above login verification method as an example, in the scenario of verifying the login of the user account corresponding to the current business client, the following steps will provide a complete explanation of the above method:

[0086] The current business client determines the current online rate of the reference business client based on the running status information returned by the reference business client, or the current business client determines the current online rate of the reference business client based on the number of reference business clients that have returned running status information and the total number of all reference business clients.

[0087] If the current online rate of the reference service client is greater than the verification trigger threshold, a login verification request is broadcast to the network access address corresponding to each reference service client via the P2P protocol.

[0088] In this embodiment, the online status of each reference service client in the reference service client cluster is obtained. If the online rate of the reference service client cluster is determined to be greater than the verification trigger threshold based on the online status, a login verification request is broadcast to each network access address via an end-to-end protocol. The login verification request includes login information of the target user account encrypted with a key. In other words, in this embodiment, the login verification request is broadcast to the network access address corresponding to each reference service client via a P2P protocol only when the online rate of the reference service client cluster is greater than the trigger threshold. This avoids the technical problem of inaccurate login verification due to an insufficient number of participating service clients. This achieves the technical effect of improving the accuracy and security of login verification.

[0089] Optionally, as an optional implementation, after granting business function permissions corresponding to the current security verification level to the current business client logged in using the target user account, the method further includes:

[0090] S1, Receive object login authentication request sent by object reference service client in reference service client cluster, wherein the object login authentication request is used to request to log in to object reference service client using object user account;

[0091] S2, parse the login information of the object user account from the object login authentication request;

[0092] S3 verifies the login information of the target user account.

[0093] It should be noted that the current business client stores the public key information (i.e., public key information) corresponding to each reference business client included in the reference business client cluster, as well as the private key information (i.e., private key information) corresponding to the current business client itself. Correspondingly, each reference business client included in the reference business client cluster also stores the public key information corresponding to the current business client, as well as the private key information corresponding to each of the aforementioned reference business clients.

[0094] Optionally, as an alternative implementation, the object login authentication request sent by the aforementioned object reference business client may include, but is not limited to, information obtained by encrypting the login information of the object user account using the public key of the current business client.

[0095] Furthermore, the above-mentioned parsing of the login information of the object user account from the object login authentication request may include, but is not limited to, decrypting the information included in the object login authentication request based on the private key of the current business client to obtain the login information of the object user account.

[0096] For example, such as Figure 3 The diagram assumes that business client A is the party being verified, and business client B is the party verifying user account S. The login verification process for user account S may include the following steps:

[0097] In steps S302-S306, business client A uses the public key of business client B to encrypt the login information of user account S to obtain the encrypted login information. This encrypted login information is then encapsulated into the login authentication request for user account S.

[0098] Next, in step S306, business client A sends a login authentication request to business client B.

[0099] Then, upon receiving a login authentication request, business client B executes steps S308-S310, decrypting the encrypted login information included in the login authentication request using its own private key to obtain the login information of user account S. Next, business client B performs login verification for user account S based on the login information of user account S.

[0100] Further, in step S312, business client B sends the verification response result of user account S to business client A.

[0101] It should be noted that the above embodiment is an explanatory example of using a verified business client (i.e., client A) and a verifying business client (i.e., client B) to verify the login of the user account to be verified (i.e., user account S). In fact, all verified business clients (such as the current business client and the reference business client mentioned above) and a verifying business client (such as the current business client and the reference business client mentioned above) can use the above method to verify the user account to be verified.

[0102] Assuming the above login verification method is applied to a scenario involving login verification of the user account corresponding to the current business client, the following steps will provide a complete explanation of the method:

[0103] The current business client receives an object login authentication request (i.e., a verification request for logging into the object reference business client using an object user account) sent by an object reference business client in the reference business client cluster. The object login authentication request includes information obtained by encrypting the login information of the object user account using the current business client's public key. Then, based on the current business client's private key, the information included in the object login authentication request is decrypted to obtain the login information of the object user account (i.e., the user account to be verified and the password, etc.). The login information of the object user account is then compared with the pre-stored accurate information of the object user account to confirm whether the object user account can pass the login verification. In this embodiment, the current business client receives an object login authentication request sent by an object reference business client in the reference business client cluster, wherein the object login authentication request is used to request logging into the object reference business client using an object user account. Then, the login information of the object user account is parsed from the object login authentication request. Then, the login information of the object user account is verified. In other words, in this embodiment, the current business client, in addition to being the verified party, can also act as the verifier verifying the user accounts corresponding to other reference business clients. In other words, business clients within the same distributed business authentication network can authenticate each other. This avoids the technical problem of low login authentication security caused by the current business client attempting local login authentication based on its own user account when the connection between the current business client and the server fails. This achieves the technical effect of improving login authentication security.

[0104] Optionally, as an optional implementation, before obtaining the login verification request triggered in the current business client, the method further includes:

[0105] S1, retrieve the login / registration request triggered in the current business client;

[0106] S2, while the current business client and the server are in a connected state, a login registration request is sent to the server. The server will assign a current network access address to the current business client and send the login information of the current business client to the reference business client located in the same distributed business verification network. The login information of the current business client includes the current network access address.

[0107] S3 stores the current network access address received from the server.

[0108] It should be noted that the login and registration requests here can be used, but are not limited to, to request the addition of new business clients to the distributed business authentication network.

[0109] Assuming the above login verification method is applied to a scenario involving login verification of the user account corresponding to the current business client, the following steps will provide a complete explanation of the method:

[0110] Get Figure 4 The login / registration request is triggered in the current business client 412 (i.e., the newly added business client) shown in (a). Then, while the current business client 412 is connected to the server 414, it sends the login / registration request to the server 414. This allows the server 414 to assign a current network access address to the current business client 412, and send the login information of the current business client 412 (such as current network access address, business client ID, business client nickname, etc.) to the reference business clients 402, 404, 406, 408, and 410 located in the same distributed business verification network. The server 414 also returns the corresponding network access addresses of the reference business clients 402, 404, 406, 408, and 410, as well as the current network address of the current business client 412, to the current business client 412. Then, the current service client 412 stores the network access addresses corresponding to the reference service clients 402, 404, 406, 408, and 410, as well as its current network address, locally. This allows the current service client 412 to successfully join the aforementioned distributed service verification network.

[0111] Specifically, the aforementioned distributed business verification network, which includes the current business client, is as follows: Figure 4 As shown in (b), the system consists of the current business client 412, the server 414, and reference business clients 402, 404, 406, 408, and 410. All business clients in the distributed business verification network (i.e., including the current business client 412 and reference business clients 402, 404, 406, 408, and 410) are connected to the server 414, and all business clients in the distributed business verification network are connected to each other in pairs.

[0112] In the proposed embodiment, a login / registration request triggered in the current business client is obtained. Then, while the current business client is connected to the server, the login / registration request is sent to the server. The server assigns a current network access address to the current business client and sends the current business client's login information, including the current network access address, to a reference business client located in the same distributed business verification network. The current network access address received from the server is then saved. In other words, by broadcasting the current network client's current network access address to a reference business client located in the same distributed business verification network, the current business client can join the distributed business verification network and then have its user account verified by the reference business client within the same network. This avoids the technical problem of low login verification security caused by the current business client performing local login verification based on its own user account when the connection between the current business client and the server fails. Therefore, the technical effect of improving login verification security is achieved.

[0113] Optionally, as an alternative implementation, suppose the above login verification method is applied to a scenario of login verification for the user account corresponding to the current business client, such as... Figure 5 The following steps provide a complete explanation of the above method:

[0114] Execute steps S502-S504: After the current business client receives the login operation of the target user account, determine whether the online rate of each reference business client in the same distributed business verification network as the current business client is greater than the verification trigger condition threshold.

[0115] If the online rate of the reference business client is less than the verification trigger threshold, proceed to step S514-2 to determine that the target user account login verification failed.

[0116] If the online rate of the reference service client exceeds the verification trigger threshold, steps S506-S512 are executed. The current service client broadcasts a login verification request to each reference service client. This login verification request includes the login information of the target user account, encrypted with a key. Each reference service client then parses the login verification request and verifies the target user account. Next, each reference service client sends its verification response to the current service client, allowing the current service client to determine whether the verification was successful (i.e., whether the verification pass rate of the reference service client exceeds a predetermined threshold) based on the verification response results from each reference service client.

[0117] Then, if the verification pass rate of the reference business client is greater than the predetermined threshold, step S514-1 is executed to determine that the target user account login verification is successful. If the verification pass rate of the reference business client is greater than the predetermined threshold, step S514-2 is executed to determine that the target user account login verification fails.

[0118] In this embodiment, when the network connection between the current business client and the login verification server is poor, cloud login verification can be performed on the user account corresponding to the current business client based on multiple reference business clients located in the same distributed business verification network. This avoids the technical problem of low login verification security caused by the current business client performing local login verification on its own. Thus, the technical effect of improving login verification security is achieved.

[0119] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0120] Alternatively, as another optional embodiment, assuming the above login verification method is applied to a scenario of login verification for the user account corresponding to the current business client, the following steps will provide a complete explanation of the above method:

[0121] When a client corresponding to the scheduling system in the distributed business verification network, or a business client scheduled by the scheduling system, logs in with a user account, if it is determined that the current online rate of other clients in the distributed business verification network is lower than the verification trigger condition threshold, the running status of the client corresponding to the scheduling system, or the aforementioned business client, is set to online, and the system waits for other clients in the distributed business verification network to come online.

[0122] If the current online rate of other clients in the distributed business verification network is higher than the verification trigger threshold, login verification will be performed sequentially according to the online time of other clients in the distributed business verification network until all clients have been verified.

[0123] In this embodiment, if the current online rate of other clients in the distributed service verification network is determined to be lower than the verification trigger condition threshold, the system waits for these other clients to come online. If the current online rate of other clients in the distributed service verification network is higher than the verification trigger condition threshold, login verification is performed sequentially according to the online time of these other clients until all clients have completed verification. This is to avoid the problem of other clients in the distributed service verification network being temporarily offline, resulting in the inability to perform user account login verification for the client corresponding to the scheduling system or the business client scheduled by the scheduling system.

[0124] According to another aspect of the embodiments of this application, an apparatus for implementing the login verification method described above is also provided. For example... Figure 6 As shown, the device includes:

[0125] The first acquisition unit 602 is used to acquire a login verification request triggered in the current business client, wherein the login verification request is used to request to log in to the current business client using the target user account;

[0126] The sending unit 604 is used to send the login verification request to the reference business client cluster associated with the current business client. The reference business clients in the reference business client cluster are located in the same distributed business verification network as the current business client. The reference business clients record verification information for verifying the current business client.

[0127] The receiving unit 606 is used to receive the verification response result returned by the reference service client in the reference service client cluster;

[0128] The verification processing unit 608 is used to determine the current security verification level corresponding to the current business client based on the verification response result, and to enable the business function permissions corresponding to the current security verification level for the current business client that logs in using the target user account.

[0129] Optionally, the verification processing unit includes: a parsing module, used to parse the verification result obtained by the reference business client from the verification response result; a statistics module, used to perform statistics on the verification results of each reference business client in the reference business client cluster to obtain the current verification pass rate; and a determination module, used to determine the current security verification level corresponding to the current business client based on the current online rate and the current verification pass rate of the reference business clients in the reference business client cluster.

[0130] Optionally, the determining module is further configured to: determine the current security verification level as a first security level if the current online rate is greater than a first online threshold and the current verification pass rate is greater than a first pass threshold, wherein the first security level indicates that all business function permissions in the current business client are enabled; determine the current security verification level as a second security level if the current online rate is greater than a second online threshold and the current verification pass rate is greater than a second pass threshold, wherein the second security level indicates that some business function permissions in the current business client are enabled, including: data read-only permissions and sensitive business data processing permissions; determine the current security verification level as a third security level if the current online rate is greater than a third online threshold and the current verification pass rate is greater than a third pass threshold, wherein the third security level indicates that some business function permissions in the current business client are enabled, including: data read-only permissions and non-sensitive business data processing permissions; wherein the first online threshold is greater than the second online threshold, the second online threshold is greater than the third online threshold; the first pass threshold is greater than the second pass threshold, the second pass threshold is greater than the third pass threshold; and the scope of the sensitive business data processing permissions is greater than the scope of the non-sensitive business data processing permissions.

[0131] Optionally, the sending unit includes: a reading module, used to read the network access address corresponding to each reference business client in the reference business client cluster from the configuration file in the current business client when the connection between the current business client and the server fails; and a sending module, used to send a login verification request to the network access address.

[0132] Optionally, the sending module is also used to obtain the online status of each reference service client in the reference service client cluster; if it is determined from the online status that the online rate of the reference service client cluster is greater than the verification trigger condition threshold, a login verification request is broadcast to each network access address through an end-to-end protocol, wherein the login verification request includes the login information of the target user account encrypted with a key.

[0133] Optionally, the login verification device further includes: a first receiving unit, configured to receive an object login authentication request sent by an object reference service client in the reference service client cluster, wherein the object login verification request is used to request to log in to the object reference service client using an object user account; a parsing unit, configured to parse the login information of the object user account from the object login authentication request; and a first verification processing unit, configured to verify the login information of the object user account.

[0134] Optionally, the login verification device further includes: a second acquisition unit, used to acquire a login registration request triggered in the current business client; a first sending unit, used to send the login registration request to the server when the current business client and the server are in a connected state, wherein the server will assign a current network access address to the current business client and send the login information of the current business client to reference business clients located in the same distributed business verification network, the login information of the current business client including the current network access address; and a storage unit, used to store the current network access address received from the server.

[0135] For specific implementation examples, please refer to the examples shown in the login verification method above. These examples will not be repeated here.

[0136] According to another aspect of the embodiments of this application, an electronic device for implementing the above-described login verification method is also provided. This electronic device may be... Figure 1 The terminal device or server shown. This embodiment uses this electronic device as an example for illustration. Figure 7 As shown, the electronic device includes a memory 702 and a processor 704. The memory 702 stores a computer program, and the processor 704 is configured to execute the steps in any of the above method embodiments via the computer program.

[0137] Optionally, in this embodiment, the aforementioned electronic device may be located in at least one of a plurality of network devices in a computer network.

[0138] Optionally, in this embodiment, the processor can be configured to perform the following steps via a computer program:

[0139] S1, obtain the login verification request triggered in the current business client, where the login verification request is used to request the target user account to log in to the current business client;

[0140] S2, send the login verification request to the reference business client cluster associated with the current business client. The reference business clients in the reference business client cluster are located in the same distributed business verification network as the current business client. The reference business clients record the verification information used to verify the current business client.

[0141] S3, receive the verification response result returned by the reference service client in the reference service client cluster;

[0142] S4. Determine the current security verification level corresponding to the current business client based on the verification response result, and enable the business function permissions corresponding to the current security verification level for the current business client that logs in using the target user account.

[0143] Alternatively, as those skilled in the art will understand, Figure 7 The structure shown is for illustrative purposes only. Electronic devices can also be smartphones (such as Android phones, iOS phones, etc.), tablets, PDAs, mobile internet devices (MIDs), PADs, and other terminal devices. Figure 7 This does not limit the structure of the aforementioned electronic devices. For example, the electronic device may also include components that are more... Figure 7 The more or fewer components shown (such as network interfaces, etc.), or having the same Figure 7 The different configurations shown.

[0144] The memory 702 can be used to store software programs and modules, such as the program instructions / modules corresponding to the login verification method and apparatus in this embodiment. The processor 704 executes various functional applications and data processing by running the software programs and modules stored in the memory 702, thereby implementing the login verification method described above. The memory 702 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 702 may further include memory remotely located relative to the processor 704, and these remote memories can be connected to the terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. Specifically, the memory 702 may be used, but is not limited to, to store information such as the verification response results described above. As an example, such as... Figure 7 As shown, the memory 702 may include, but is not limited to, the first acquisition unit 602, the sending unit 604, the receiving unit 606, and the verification processing unit 608 in the login verification device. Furthermore, it may include, but is not limited to, other module units in the login verification device, which will not be elaborated upon in this example.

[0145] Optionally, the transmission device 706 described above is used to receive or send data via a network. Specific examples of the network described above may include wired networks and wireless networks. In one example, the transmission device 706 includes a Network Interface Controller (NIC), which can be connected to other network devices and a router via a network cable to communicate with the Internet or a local area network. In another example, the transmission device 706 is a radio frequency (RF) module, used for wireless communication with the Internet.

[0146] In addition, the aforementioned electronic device also includes a connection bus 708 for connecting various module components in the aforementioned electronic device.

[0147] In other embodiments, the aforementioned terminal device or server can be a node in a distributed system, wherein the distributed system can be a blockchain system, which is a distributed system formed by connecting multiple nodes through network communication. The nodes can form a peer-to-peer (P2P) network, and any form of computing device, such as a server, terminal, or other electronic device, can become a node in the blockchain system by joining this peer-to-peer network.

[0148] According to one aspect of this application, a computer-readable storage medium is provided, wherein a processor of a computer device reads computer instructions from the computer-readable storage medium, and executes the computer instructions to cause the computer device to perform the methods provided in the various alternative implementations described above.

[0149] Optionally, in this embodiment, the computer-readable storage medium may be configured to store a computer program for performing the following steps:

[0150] S1, obtain the login verification request triggered in the current business client, where the login verification request is used to request the target user account to log in to the current business client;

[0151] S2, send the login verification request to the reference business client cluster associated with the current business client. The reference business clients in the reference business client cluster are located in the same distributed business verification network as the current business client. The reference business clients record the verification information used to verify the current business client.

[0152] S3, receive the verification response result returned by the reference service client in the reference service client cluster;

[0153] S4. Determine the current security verification level corresponding to the current business client based on the verification response result, and enable the business function permissions corresponding to the current security verification level for the current business client that logs in using the target user account.

[0154] Optionally, in this embodiment, those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing the hardware related to the terminal device. The program can be stored in a computer-readable storage medium, which may include: flash drive, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0155] If the integrated units in the above embodiments are implemented as software functional units and sold or used as independent products, they can be stored in the aforementioned computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause one or more computer devices (which may be personal computers, servers, or network devices, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.

[0156] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0157] In the several embodiments provided in this application, it should be understood that the disclosed client can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection between units or modules, and may be electrical or other forms.

[0158] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0159] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0160] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A login verification method, characterized in that, include: Obtain the login verification request triggered in the current business client, wherein the login verification request is used to request to log in to the current business client using the target user account; The login verification request is sent to a cluster of reference business clients associated with the current business client. The reference business clients in the cluster are located in the same distributed business verification network as the current business client. The reference business clients record verification information for verifying the current business client. Receive the verification response result returned by the reference service client in the reference service client cluster; The verification result obtained by the reference service client is parsed from the verification response result; The verification results of each reference service client in the reference service client cluster are statistically analyzed to obtain the current verification pass rate; Based on the current online rate and the current verification pass rate of the reference service clients in the reference service client cluster, determine the current security verification level corresponding to the current service client; Enable business function permissions corresponding to the current security verification level for the current business client logged in using the target user account.

2. The method according to claim 1, characterized in that, The step of determining the current security verification level corresponding to the current service client based on the current online rate and the current verification pass rate of the reference service clients in the reference service client cluster includes: If the current online rate is greater than the first online threshold and the current verification pass rate is greater than the first pass threshold, the current security verification level is determined to be the first security level, wherein the first security level indicates that all business function permissions in the current business client are enabled; If the current online rate is greater than the second online threshold and the current verification pass rate is greater than the second pass threshold, the current security verification level is determined to be the second security level. The second security level indicates that some business function permissions in the current business client are enabled. The some business function permissions include: data read-only permission and sensitive business data processing permission. If the current online rate is greater than the third online threshold and the current verification pass rate is greater than the third pass threshold, the current security verification level is determined to be the third security level. The third security level indicates that some business function permissions in the current business client are enabled. The some business function permissions include: data read-only permission and non-sensitive business data processing permission. Wherein, the first online threshold is greater than the second online threshold, and the second online threshold is greater than the third online threshold; the first pass threshold is greater than the second pass threshold, and the second pass threshold is greater than the third pass threshold; the scope of the sensitive business data processing permission is greater than the scope of the non-sensitive business data processing permission.

3. The method according to claim 1, characterized in that, Sending the login verification request to the reference business client cluster associated with the current business client includes: If the current business client fails to connect to the server, the network access address corresponding to each of the reference business clients in the reference business client cluster is read from the configuration file in the current business client. Send the login verification request to the network access address.

4. The method according to claim 3, characterized in that, Sending the login verification request to the network access address includes: Obtain the online status of each reference service client in the reference service client cluster; If, based on the online status, the online rate of the reference service client cluster is determined to be greater than the verification trigger threshold, the login verification request is broadcast to each of the network access addresses via an end-to-end protocol. The login verification request includes the login information of the target user account encrypted with a key.

5. The method according to claim 1, characterized in that, After granting the business function permissions corresponding to the current security verification level to the current business client logged in using the target user account, the process further includes: Receive an object login authentication request sent by an object reference service client in the reference service client cluster, wherein the object login authentication request is used to request to log in to the object reference service client using an object user account; The login information of the user account of the object is parsed from the login authentication request of the object; The login information of the user account of the object is verified.

6. The method according to any one of claims 1 to 5, characterized in that, Before obtaining the login verification request triggered in the current business client, the method also includes: Retrieve the login / registration request triggered in the current business client; When the current business client and the server are in a connected state, the login registration request is sent to the server. The server will assign a current network access address to the current business client and send the login information of the current business client to the reference business client located in the same distributed business verification network. The login information of the current business client includes the current network access address. Save the current network access address received from the server.

7. A login verification device, characterized in that, include: The first acquisition unit is used to acquire a login verification request triggered in the current business client, wherein the login verification request is used to request to log in to the current business client using the target user account; The sending unit is used to send the login verification request to a reference business client cluster associated with the current business client, wherein the reference business clients in the reference business client cluster are located in the same distributed business verification network as the current business client, and the reference business clients record verification information for verifying the current business client. A receiving unit is configured to receive the verification response result returned by the reference service client in the reference service client cluster; The verification processing unit is configured to parse the verification result obtained by the reference service client from the verification response result; statistically analyze the verification results of each reference service client in the reference service client cluster to obtain the current verification pass rate; determine the current security verification level corresponding to the current service client based on the current online rate of the reference service clients in the reference service client cluster and the current verification pass rate; and enable the business function permissions corresponding to the current security verification level for the current service client logged in using the target user account.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program is executed by a processor to perform the method described in any one of claims 1 to 6.

9. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to execute the method described in any one of claims 1 to 6 through the computer program.

Images