WO2019165675A1 - Login verification method and apparatus, computer device, and storage medium - Google Patents

Abstract

Disclosed in the present application are a login verification method and apparatus, a computer device, and a storage medium, the login verification method comprising: acquiring an identity verification request sent by a client terminal, the identity verification request comprising identity feature information and terminal identification information; if the identity feature information does not pass identity verification, then acquiring the number of historical login times corresponding to the identity feature information and the terminal identification information; and, if the number of historical login times reaches a verification times threshold, then pushing a second verification method to the client terminal. In the present method, when the number of historical login times corresponding to the identity feature information and the terminal identification information reaches a verification times threshold, a second verification method is pushed to the client terminal, enabling a good user experience by verifying the user by means of another identity verification method, and achieving the objectives of preventing the client terminal from violently attacking and breaching the server and ensuring login security.

Description

Login verification method, device, computer device and storage medium

The present application is based on the Chinese Patent Application No. 20110116398, filed on Feb. 27, 2018, entitled "Login Verification Method, Apparatus, Computer Equipment, and Storage Medium", and claims priority.

Technical field

The present application relates to the field of identity verification, and in particular, to a login verification method, apparatus, computer device, and storage medium.

Background technique

Currently, the establishment of a secure connection between the client and the server is generally implemented by the client entering the login password. Such an authentication method has security risks. If a malicious client brutes the login password to the server, it may invade the server, causing information leakage.

To prevent malicious attacks on the client, the server needs to set up measures to prevent malicious attacks on the client when the user logs in to the server. However, these measures require the user to input multiple information to log in for security verification, which makes the user experience poor, especially for information input. Mobile terminal.

Summary of the invention

The embodiment of the present application provides a login verification method, device, computer device, and storage medium, so as to solve the problem that the current user logs in to avoid information leakage caused by malicious attacks.

In a first aspect, the embodiment of the present application provides a login verification method, including:

Obtaining an authentication request sent by the client, where the identity verification request includes identity feature information and terminal identification information;

If the identity feature information is not authenticated, obtaining a historical login number corresponding to the identity feature information and the terminal identification information;

If the number of historical logins reaches the authentication threshold, the second verification mode is pushed to the client;

Obtain a secondary verification request input by the client based on the second verification mode, and perform login verification based on the secondary verification request.

In a second aspect, the embodiment of the present application provides a login verification apparatus, including:

Obtaining an authentication request module, configured to obtain an authentication request sent by the client, where the identity verification request includes identity feature information and terminal identification information;

Obtaining a historical login number module, configured to obtain a historical login number corresponding to the identity feature information and the terminal identification information if the identity feature information does not pass the identity verification;

Pushing the second verification mode module, if the historical login times reach the authentication number threshold, pushing the second verification mode to the client;

The login verification module is configured to obtain a secondary verification request input by the client according to the second verification mode, and perform login verification based on the secondary verification request.

A third aspect of the present application provides a computer device comprising a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, the processor executing the computer readable instructions Implement the following steps:

Obtaining an authentication request sent by the client, where the identity verification request includes identity feature information and terminal identification information;

If the identity feature information is not authenticated, obtaining a historical login number corresponding to the identity feature information and the terminal identification information;

If the number of historical logins reaches the authentication threshold, the second verification mode is pushed to the client;

Obtain a secondary verification request input by the client based on the second verification mode, and perform login verification based on the secondary verification request.

A fourth aspect of the present application provides one or more non-transitory readable storage mediums storing computer readable instructions, the computer readable instructions being executed by one or more processors such that the one or more processes Perform the following steps:

Obtaining an authentication request sent by the client, where the identity verification request includes identity feature information and terminal identification information;

If the identity feature information is not authenticated, obtaining a historical login number corresponding to the identity feature information and the terminal identification information;

If the number of historical logins reaches the authentication threshold, the second verification mode is pushed to the client;

Obtain a secondary verification request input by the client based on the second verification mode, and perform login verification based on the secondary verification request.

The login verification method, device, computer device and storage medium provided by the embodiments of the present application can obtain a malicious attack from the client more completely and comprehensively by acquiring the historical login times corresponding to the identity feature information and the terminal identification information at the same time; The feature information and the terminal identification information history registration times reach the authentication number threshold, and the second verification mode is pushed to the client to authenticate the user by another identity verification manner, so as to prevent the client from brute force attacking and cracking the server, thereby achieving the protection login. The purpose of security.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the description of the embodiments of the present application will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present application. Other drawings may also be obtained from those of ordinary skill in the art based on these drawings without the inventive labor.

1 is a flowchart of a login verification method in Embodiment 1 of the present application;

2 is another specific flowchart of the login verification method in Embodiment 1 of the present application;

3 is another specific flowchart of the login verification method in Embodiment 1 of the present application;

4 is another specific flowchart of the login verification method in Embodiment 1 of the present application;

5 is a schematic block diagram of a login verification apparatus in Embodiment 2 of the present application;

FIG. 6 is a schematic diagram of a computer device in Embodiment 4 of the present application.

Detailed ways

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the drawings in the embodiments of the present application. It is obvious that the described embodiments are a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

Example 1

FIG. 1 shows a flow chart of a login verification method in this embodiment. This embodiment is applied between a client and a server that exchange information through the Internet, wherein the client includes but is not limited to a browser and a software login port. The client in this embodiment is preferably a mobile terminal such as a smart phone. The server is a management terminal that receives a request from a client and allocates an application service based on the request. The following login verification method takes the server as the execution subject. As shown in FIG. 1, the login verification method includes the following steps:

S10. Acquire an authentication request sent by the client, where the identity verification request includes identity feature information and terminal identification information.

Specifically, the authentication request is a request that is initiated to the server when the client needs to connect to the server, and is used for authentication. The authentication request includes identity feature information and terminal identification information to enable the server to verify the identity based on the identity feature information and the terminal identification information therein to determine whether the client can establish a secure connection with the server.

The identity information is information that is provided to the server to identify the identity of the user. The terminal identification information is environment information provided to the server for identifying the client.

Specifically, after receiving the identity verification request sent by the client, the server performs identity verification based on the identity feature information. If the identity feature information passes the identity verification, step S50 is performed; if the identity feature information does not pass the identity verification, Step S20 is performed. There are many methods for authentication, including but not limited to: shared key based authentication, biological feature based authentication, and public key encryption based authentication. This step first authenticates the identity of the user through the authentication request, and initially ensures the security of the connection between the server and the client.

S20. If the identity feature information does not pass the identity verification, obtain the number of historical logins corresponding to the identity feature information and the terminal identification information.

Specifically, the number of historical logins is the number of times the number of times the specific feature item is logged into the server among the feature items indicating the identity feature information and the terminal identification information. For example, the feature items of the identity information include, but are not limited to, the registration ID, and the feature items of the terminal identification information include, but are not limited to, the device ID and the login IP, and among the registration ID, the device ID, and the login IP, the number of times the login server is the highest It is the number of historical logins. The registration ID is information that can be uniquely identified when the user logs in to the server, such as a user name, a mobile phone number, and an ID number. The device ID is the global unique production device number of the hardware used for client login. For example, the device ID of the mobile phone is the production serial number of the mobile phone, and the device ID of the desktop computer may be the MAC address of the network card. The login IP address is the address or private IP address assigned by the public network when the client accesses the Internet.

Further, the number of historical logins of the user login server is examined by using the identity information and the terminal identification information, so that the user login to the server can be more comprehensively and truly investigated. For example, if the same registration ID is used and the server is repeatedly logged in through different smartphones, the registered registration ID has the highest number of logins, so it is determined as the number of historical logins. Or, if the same smart phone repeatedly logs in to the server with different registration IDs, the identified device ID has the highest number of logins, so it is determined as the number of historical logins. Or, if different smartphones repeatedly log in to the server with different registration IDs under the network corresponding to different login IPs, the number of logins of the identified login IPs is the largest, and thus the number of historical logins is determined. Therefore, determining the number of historical logins by using the identity information and the terminal identification information is beneficial to prevent malicious clients from attacking the server to a certain extent, to avoid information leakage, thereby ensuring information security.

The number of historical logins mentioned in this embodiment may be the number of logins corresponding to the registration ID, the device ID, and the login IP recorded in the server within a preset time period, and the number of logins with the highest number of times is determined as the number of historical logins.

S30. If the number of historical logins reaches the threshold of the number of authentications, the second verification mode is pushed to the client.

The authentication number threshold is the maximum number of logins that can be logged into the server for the number of historical logins of the identity information and the terminal identification information. For example, the number of authentication times is 5, that is, when the number of historical logins is 5, the server no longer accepts the same type of authentication request, and instead adopts the second authentication mode.

Specifically, the second verification method includes, but is not limited to, a slider, a puzzle, a letter, a number, and the like, and a verification method with a subjective feeling.

The method of forcibly switching to the second authentication mode with human subjective feeling can effectively determine the authenticity of the client and prevent the client from invading the server through malicious means of brute force.

S40. Acquire a secondary verification request input by the client based on the second verification mode, and perform login verification based on the secondary verification request.

Specifically, the secondary verification request is a verification request that the client responds to the second verification mode.

The server verifies the secondary verification request sent by the client. For example, if the client sends back a secondary verification request with text for the text in the graphic verification code, the server determines the correctness of the text to complete the login verification. In this embodiment, the server performs login verification on the second verification request sent by the client based on the second authentication mode feedback, so as to prevent the client from launching a malicious attack on the server through the brute force attacking machine, so that the server is cracked and the information is leaked. .

Preferably, after the step S10, that is, after the step of acquiring the identity verification request sent by the client, the login verification method further includes the following steps:

S50. If the identity feature information is authenticated, a secure connection is established with the client through the authentication request.

It can be understood that when the server verifies the authentication request sent by the client, the server can confirm the security of the identity information of the client through the information stored in the database, thereby establishing a secure connection with the client. After this step, the client and the server have established a secure connection, so that the client can further obtain the specific service information provided by the server.

Preferably, after the step S20, that is, after the step of acquiring the number of historical logins corresponding to the identity feature information and the terminal identification information, the method for verifying the login further includes the following steps:

S60. If the number of historical logins does not reach the authentication threshold, the client is prompted to resend the authentication request.

Specifically, the number of authentication times threshold is the maximum number of logins that can be logged into the server for the number of historical logins of the identity feature information and the terminal identification information. For example, the threshold of the number of authentication times is 5, that is, when the number of historical logins is 5, the server no longer accepts the same type of authentication request, and instead adopts other authentication methods.

Further, the number of historical logins does not reach the threshold of the number of cognitions established by the server, indicating that the server can again accept the same type of authentication request sent by the client, and enhance the flexibility of the server to authenticate the client. The login verification method provided by the embodiment of the present invention can obtain a malicious attack from the client more completely and comprehensively by acquiring the historical login times corresponding to the identity feature information and the terminal identification information; when the historical login times reach the threshold of the authentication times, Pushing the second verification mode to the client to authenticate the user through another authentication method, so as to prevent the client from brute force attacking and cracking the server, thereby achieving the purpose of securing login security, and obtaining a good user experience, especially For mobile terminal users who are inconvenient to input information.

In a specific implementation, the identity feature information includes a registration ID, and the terminal identification information includes a device ID and a login IP. As shown in FIG. 2, in step S20, a historical login corresponding to the identity feature information and the terminal identification information is acquired. The number of times includes the following steps:

S21. The historical login data in the preset time period is calculated, and the first login number, the second login number, and the third login number corresponding to the registration ID, the device ID, or the login IP are respectively obtained.

The historical login data is related data of the registration ID, the device ID, and the login IP login server in a preset time period, including the respective login times, login time, and the like. The server stores all historical login data in advance. Each historical login data corresponds to a registration ID, a device ID, and a login IP, and is also stored in association with the login time. It can be understood that the first login number refers to the number of times the registration ID logs in to the server within a preset time period, and the second login number refers to the number of times the device ID logs in to the server within a preset time period, and the third login number is the login IP address. The number of times the server was logged in during the preset time period. The preset time period in this embodiment may be a period of time from the time when the identity verification request is obtained or the current time of the system is reversed, and may be set to 1 day or 1 week.

S22. Select a maximum value from the first login count, the second login count, and the third login count as the historical login count.

For example, the first login number, the second login number, and the third login number corresponding to the registration ID, the device ID, or the login IP are 3, 5, and 8, respectively, and the historical login number is the third login number corresponding to the historical login number, that is, 8 times.

In order to fully defend the client of the login server, it is necessary to examine the situation of the client login server from three perspectives. As shown in this example, the first login number corresponding to the registration ID is only 3 times, and the login IP used by the login IP has been used 8 times. For security reasons, the third login number corresponding to the login IP is determined as history. The number of logins in order to better achieve security defense against the server. By examining the situation of the client login server from multiple perspectives, the information security in the server can be more comprehensively and effectively protected.

Preferably, after the step S22, that is, after the step of selecting the maximum value as the number of historical logins from the first number of logins, the second number of logins, and the third number of logins, the login verification method further includes:

S23. If the number of historical logins does not reach the authentication number threshold, the number of times corresponding to the first login number, the second login number, and the third login number is incremented by one, and the number of historical logins is updated.

It can be understood that the server receives the authentication request sent by the client, that is, the registration ID, the device ID, and the login IP of the client are registered again, and the first login number, the second login number, and the corresponding number should be given. The number of three logins is increased by 1, and the corresponding number of historical logins is updated.

For example, if the authentication threshold is 5, the following is a record table of the number of historical logins after the server receives three authentication requests:

	Registration ID	Device ID	Login IP
Authentication request 1	0	1	1
Authentication request 2	1	1	0
Authentication request 3	0	1	1

Registration ID	Device ID	Login IP		Historical logins
1	3	2	3

At this time, the number of historical logins is 3, and the number of authentication times threshold 5 is not reached. Therefore, when the server receives four authentication requests, the record of the number of historical logins is changed to:

Registration ID	Device ID	Login IP	Historical logins
2	4	3	4

In order to fully protect the client of the login server, the present embodiment starts from the registration ID of the registration ID, the device ID, and the login IP, and comprehensively examines the situation of the client login server, so that the server can be more comprehensively and effectively protected. Moreover, the historical login number is updated in time according to the identity verification request of the client login server, and the true validity of the server data is maintained.

In a specific embodiment, as shown in FIG. 3, before the step S21, that is, before the step of counting the historical login data in the preset time period, the login verification method further includes the following steps:

S70. The historical login data stored in the RED-DATA database in the form of KEY-VALUE, the registration ID, the device ID, and the login IP are used as the KEY, and the first login number, the second login number, and the third login number are respectively used as the corresponding VALUE.

Specifically, the embodiment uses the REDIS database to store historical login data. REDIS is a high-performance KEY-VALUE database that complements relational databases. The type of REDIS median is not limited to strings. It also supports the following abstract data types: string lists, unordered string collections, ordered non-repeating string collection keys, and hash tables with values as strings. The type of value determines the operations supported by the value itself. REDIS supports advanced unordered, ordered lists, unordered, ordered sets of intersections, unions, and other advanced server-side atomic operations.

In this embodiment, the historical login data stored in the KEY-VALUE format in the EDIS database has the registration ID, the device ID, and the login IP as the KEY, and the first login number, the second login number, and the third login number are respectively corresponding. VALUE, as shown in the following table.

Registration ID	First logins
X1	5

Device ID	Second login
00-01-6C-06-A6-29	6

Login IP	Third login count
183.53.240.209	9

In this implementation, the registration ID, the device ID, and the historical login data of the login IP involved in the authentication request are stored in the KEY-VALUE format, which is concise and clear, and facilitates the server to obtain the corresponding login information in time.

S80. Obtain historical login data between the current time and the preset time period of the system, and use the KEY-VALUE query method to obtain the first login number, the second login number, and the third corresponding to the registration ID, the device ID, or the login IP respectively. The number of logins.

Specifically, the preset time period is a time period in which the server specifies the refresh data and clears the relevant data. In order to maintain the timeliness of the authentication request, the server specifies a preset time period to clear the data stored in the database. In this embodiment, the data corresponding to the KEY can be set to a preset time end, for example, 24 hours, and the data in the KEY is cleared every 24 hours.

It can be understood that, according to the registration ID, the device ID, or the login IP stored by the KEY key, the server can directly obtain the corresponding value of the corresponding stored VALUE: first login number, second login number, and third login number, which is simple and quick.

In this embodiment, the REDA database is used to store the registration ID, the device ID, and the historical login data of the login IP involved in the authentication request in a KEY-VALUE format, which is concise and clear, and facilitates the server to obtain corresponding login information in time; and according to the preset time. The segment clears the data in the database to effectively guarantee the timeliness of the authentication request.

In an embodiment, the identity information includes a registration ID and a client verification code. As shown in FIG. 4, in step S20, if the identity feature information does not pass the identity verification, the method includes the following steps:

S24. Acquire a corresponding server verification code based on the registration ID.

Specifically, the registration ID is information that can be uniquely identified when the user logs in to the server, such as a user name, a mobile phone number, and an ID number.

The server verification code includes, but is not limited to, a registration password or a verification code corresponding to the registration ID held in the server.

By storing the server verification code corresponding to the registration ID, the server can be used to compare the client verification code sent by the client to determine the authenticity of the corresponding identity of the client, thereby ensuring the security of the connection between the server and the client.

S25. If the verification server verification code and the client verification code match inconsistency, the identity feature information fails to pass the verification.

It can be understood that if the verification server verification code and the client verification code match inconsistency, the server cannot determine the authenticity of the client, and the client needs to perform further or re-authentication, that is, the identity feature information fails to pass the verification.

In this embodiment, the authenticity of the client is verified by the registration ID and the server verification code, which is simple, fast, and highly reliable.

The login verification method provided by the embodiment of the present invention can obtain a malicious attack from the client more completely and comprehensively by acquiring the historical login times corresponding to the identity feature information and the terminal identification information; only when the historical login times reach the authentication number threshold Only the second verification method is pushed to the client, and a good user experience can be obtained, especially for a mobile terminal user who is inconvenient to input information.

In order to comprehensively protect the client of the login server, this embodiment also comprehensively examines the situation of the client login server from multiple perspectives, and can more fully and effectively protect the server. Moreover, the historical login number is updated in time according to the identity verification request of the client login server, and the true validity of the server data is maintained.

In this embodiment, the REDA database is used to store the registration ID, the device ID, and the historical login data of the login IP involved in the authentication request in a KEY-VALUE format, which is concise and clear, and facilitates the server to obtain corresponding login information in time; and, according to the preset The time period clears the data in the database to effectively guarantee the timeliness of the identity verification request.

It should be understood that the size of the sequence of the steps in the above embodiments does not mean that the order of execution is performed. The order of execution of each process should be determined by its function and internal logic, and should not be construed as limiting the implementation process of the embodiments of the present application.

Example 2

Fig. 5 is a block diagram showing the principle of the registration verification apparatus corresponding to the registration verification method in the first embodiment. As shown in FIG. 5, the login verification device includes an acquisition identity verification request module 10, a history registration number acquisition module 20, a second verification mode module 30, and a login verification module 40. The method of obtaining the authentication requesting module 10, obtaining the historical login number module 20, and pushing the second verification mode module 30 and performing the login verification module 40 correspond to the steps corresponding to the login verification method in the embodiment, in order to avoid redundancy, This embodiment will not be described in detail.

The authentication request module 10 is configured to obtain an identity verification request sent by the client, where the identity verification request includes identity feature information and terminal identification information.

The historical login number module 20 is configured to acquire the historical login times corresponding to the identity feature information and the terminal identification information if the identity feature information does not pass the identity verification.

The second verification mode module 30 is configured to push the second verification mode to the client if the number of historical logins reaches the authentication threshold.

The login verification module 40 is configured to obtain a secondary verification request input by the client according to the second verification mode, and perform login verification based on the secondary verification request.

Preferably, the login verification device further includes establishing a secure connection module 50.

The security connection module 50 is configured to establish a secure connection with the client through the identity verification request if the identity feature information is authenticated.

Preferably, the login verification device further includes a resend identity verification request module 60.

The re-send authentication request module 60 is configured to prompt the client to resend the identity verification request if the historical login number does not reach the authentication number threshold.

Preferably, the identity feature information includes a registration ID, and the terminal identification information includes a device ID and a login IP.

The acquisition history login number module 20 further includes a statistical history login data unit 21 and a selection history login number unit 22.

The statistics history registration data unit 21 is configured to collect historical login data in a preset time period, and obtain a first login number, a second login number, and a third login number corresponding to the registration ID, the device ID, or the login IP, respectively.

The historical login number unit 22 is selected to select the maximum value from the first login number, the second login number, and the third login number as the historical login times.

Preferably, the acquisition history login count module 20 further includes an update history login count unit 23.

The update history registration count unit 23 is configured to increase the number of times corresponding to the first login count, the second login count, and the third login count by 1 if the historical login count does not reach the authentication count threshold, and update the historical login count.

Preferably, the login verification device further includes a statistical history login data module 70 and an acquisition history login data module 80.

The statistical history login data module 70 is configured to collect historical login data stored in the RED-DATA database in the form of KEY-VALUE, and use the registration ID, the device ID, and the login IP as the KEY, and the first login number, the second login number, and the third login. The number of times is taken as the corresponding VALUE.

The historical login data module 80 is configured to obtain historical login data between the current time and the preset time period of the system, and obtain a first login number corresponding to the registration ID, the device ID, or the login IP by using a KEY-VALUE query manner. The second login count and the third login count.

Preferably, the identity feature information includes a registration ID and a client verification code.

The acquisition history login number module 20 further includes an acquisition server verification code unit 24 and a failure verification unit 25.

The server verification code unit 24 is configured to acquire a corresponding server verification code based on the registration ID.

If the verification server verification code and the client verification code match are inconsistent, the identity feature information fails to pass the verification.

Example 3

This embodiment provides one or more non-volatile readable storage media having computer readable instructions stored thereon. The one or more non-volatile readable storage mediums storing computer readable instructions, when executed by one or more processors, causing one or more processors to perform the login verification method of Embodiment 1 To avoid repetition, we will not repeat them here. Alternatively, when the computer readable instructions are executed by the processor, the functions of the modules/units in the login verification apparatus in Embodiment 2 are implemented. To avoid repetition, details are not described herein again.

It will be understood that one or more non-volatile readable storage media storing computer readable instructions may comprise: any entity or device capable of carrying the computer readable instruction code, a recording medium, a USB flash drive, a mobile hard drive, Disk, optical disk, computer memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier signals, and telecommunications signals.

Example 4

FIG. 6 is a schematic diagram of a computer device according to an embodiment of the present application. As shown in FIG. 6, computer device 90 of this embodiment includes a processor 91, a memory 92, and computer readable instructions 93 stored in memory 92 and executable on processor 91. The processor 91 executes the steps of the login verification method in the first embodiment, such as steps S10 to S40 shown in FIG. 1, when the computer readable instructions 93 are executed. Alternatively, when the processor 91 executes the computer readable instructions 93, the functions of the modules/units in the foregoing device embodiments are implemented. For example, the identity authentication request module 10 is obtained as shown in FIG. 5, the historical login number module 20 is acquired, and the second verification mode is pushed. The module 30 and the function of the login verification module 40 are performed.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the division of each functional unit and module described above is exemplified. In practical applications, the above functions may be assigned to different functional units as needed. The module is completed by dividing the internal structure of the device into different functional units or modules to perform all or part of the functions described above.

The embodiments described above are only used to explain the technical solutions of the present application, and are not limited thereto. Although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that the technical solutions described in the foregoing embodiments may be modified or equivalently substituted for some of the technical features. Modifications or substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the scope of the present application.

Claims (20)

1. A login verification method, comprising:

   Obtaining an authentication request sent by the client, where the identity verification request includes identity feature information and terminal identification information;

   Obtaining, according to the identity feature information, the number of historical logins corresponding to the identity feature information and the terminal identification information;

   If the number of historical logins reaches the number of authentication times, the second verification mode is pushed to the client;

   Obtaining a secondary verification request input by the client based on the second verification manner, and performing login verification based on the secondary verification request.
2. The login verification method according to claim 1, wherein after the step of acquiring the number of historical logins corresponding to the identity feature information and the terminal identification information, the login verification method further comprises:

   If the number of historical logins does not reach the threshold of the number of authentication times, the client is prompted to resend the identity verification request.
3. The login verification method according to claim 1, wherein the identity feature information comprises a registration ID, and the terminal identification information comprises a device ID and a login IP;

   And obtaining the number of historical logins corresponding to the identity feature information and the terminal identification information, including:

   Counting the historical login data in the preset time period, respectively acquiring the first login number, the second login number, and the third login number corresponding to the registration ID, the device ID, or the login IP;

   The maximum value is selected from the first login count, the second login count, and the third login count as the historical login count.
4. The login verification method according to claim 3, wherein the maximum value is selected from the first login count, the second login count, and the third login count as the historical login number After the step, the login verification method further includes:

   If the number of historical logins does not reach the threshold for the number of authentication times, the number of times corresponding to the first number of logins, the second number of logins, and the third number of logins is increased by one, and the number of historical logins is updated.
5. The login verification method according to claim 3, wherein before the step of the historical login data in the statistical preset time period, the login verification method further comprises:

   The historical login data stored in the RED-VALUE database in the form of a KEY-VALUE is used, and the registration ID, the device ID, and the login IP are used as KEYs, and the first login number, the second login number, and the third login number are respectively taken as Corresponding VALUE;

   Acquiring the historical login data between the current time of the system and the preset time period, and acquiring the first login number and the second login corresponding to the registration ID, the device ID, or the login IP by using a KEY-VALUE query manner. The number of times and the third number of logins.
6. The login verification method according to claim 1, wherein after the step of acquiring the identity verification request sent by the client, the login verification method further comprises:

   If the identity feature information is authenticated, a secure connection is established with the client through the identity verification request.
7. The login verification method according to claim 1, wherein the identity feature information comprises a registration ID and a client verification code;

   If the identity feature information is not authenticated, the method includes:

   Obtaining a corresponding server verification code based on the registration ID;

   If it is verified that the server verification code and the client verification code match inconsistency, the identity feature information fails to pass the verification.
8. A login verification device, comprising:

   Obtaining an identity verification request module, configured to obtain an identity verification request sent by the client, where the identity verification request includes identity feature information and terminal identification information;

   Obtaining a historical login number module, configured to acquire a historical login number corresponding to the identity feature information and the terminal identification information if the identity feature information does not pass the identity verification;

   Pushing the second verification mode module, if the number of historical logins reaches the authentication number threshold, pushing the second verification mode to the client;

   And performing a login verification module, configured to acquire a secondary verification request input by the client according to the second verification manner, and perform login verification based on the secondary verification request.
9. A computer device comprising a memory, a processor, and computer readable instructions stored in the memory and operative on the processor, wherein the processor executes the computer readable instructions as follows step:

   Obtaining an authentication request sent by the client, where the identity verification request includes identity feature information and terminal identification information;

   Obtaining, according to the identity feature information, the number of historical logins corresponding to the identity feature information and the terminal identification information;

   If the number of historical logins reaches the number of authentication times, the second verification mode is pushed to the client;

   Obtaining a secondary verification request input by the client based on the second verification manner, and performing login verification based on the secondary verification request.
10. The terminal device according to claim 9, wherein said processor executes said computer readable after said step of acquiring a history registration number corresponding to said identity feature information and said terminal identification information The instructions also implement the following steps:

    If the number of historical logins does not reach the threshold of the number of authentication times, the client is prompted to resend the identity verification request.
11. The terminal device according to claim 9, wherein the identity feature information comprises a registration ID, and the terminal identification information comprises a device ID and a login IP;

    And obtaining the number of historical logins corresponding to the identity feature information and the terminal identification information, including:

    Counting the historical login data in the preset time period, respectively acquiring the first login number, the second login number, and the third login number corresponding to the registration ID, the device ID, or the login IP;

    The maximum value is selected from the first login count, the second login count, and the third login count as the historical login count.
12. The terminal device according to claim 11, wherein the step of selecting the maximum value from the first number of logins, the second number of logins, and the third number of logins as the number of historical logins Thereafter, the processor further implements the following steps when the computer readable instructions are executed:

    If the number of historical logins does not reach the threshold for the number of authentication times, the number of times corresponding to the first number of logins, the second number of logins, and the third number of logins is increased by one, and the number of historical logins is updated.
13. The terminal device according to claim 11, wherein the processor further implements the following steps when the processor executes the computer readable instructions before the step of registering historical login data within the statistical preset time period:

    The historical login data stored in the RED-VALUE database in the form of a KEY-VALUE is used, and the registration ID, the device ID, and the login IP are used as KEYs, and the first login number, the second login number, and the third login number are respectively taken as Corresponding VALUE;

    Acquiring the historical login data between the current time of the system and the preset time period, and acquiring the first login number and the second login corresponding to the registration ID, the device ID, or the login IP by using a KEY-VALUE query manner. The number of times and the third number of logins.
14. The terminal device according to claim 11, wherein after the step of acquiring the identity verification request sent by the client, the processor further implements the following steps when the computer readable instruction is executed:

    If the identity feature information is authenticated, a secure connection is established with the client through the identity verification request.
15. One or more non-transitory readable storage mediums storing computer readable instructions, wherein when the computer readable instructions are executed by one or more processors, cause the one or more processors to execute The following steps:

    Obtaining an authentication request sent by the client, where the identity verification request includes identity feature information and terminal identification information;

    Obtaining, according to the identity feature information, the number of historical logins corresponding to the identity feature information and the terminal identification information;

    If the number of historical logins reaches the number of authentication times, the second verification mode is pushed to the client;

    Obtaining a secondary verification request input by the client based on the second verification manner, and performing login verification based on the secondary verification request.
16. The non-volatile readable storage medium according to claim 15, wherein said computer is operable after said step of acquiring a history registration number corresponding to said identity feature information and said terminal identification information When the read instruction is executed by one or more processors, the one or more processors further perform the following steps:

    If the number of historical logins does not reach the threshold of the number of authentication times, the client is prompted to resend the identity verification request.
17. The non-volatile readable storage medium according to claim 15, wherein the identity feature information comprises a registration ID, and the terminal identification information comprises a device ID and a login IP;

    And obtaining the number of historical logins corresponding to the identity feature information and the terminal identification information, including:

    Counting the historical login data in the preset time period, respectively acquiring the first login number, the second login number, and the third login number corresponding to the registration ID, the device ID, or the login IP;

    The maximum value is selected from the first login count, the second login count, and the third login count as the historical login count.
18. The non-volatile readable storage medium according to claim 17, wherein said maximum value is selected as said from said first number of logins, said second number of logins, and said third number of logins After the step of recording the number of historical logins, the computer readable instructions are executed by one or more processors such that the one or more processors further perform the following steps:

    If the number of historical logins does not reach the threshold for the number of authentication times, the number of times corresponding to the first number of logins, the second number of logins, and the third number of logins is increased by one, and the number of historical logins is updated.
19. A non-volatile readable storage medium as recited in claim 17, wherein said computer readable instructions are by one or more processors prior to said step of historically registering data within said statistical preset time period When executed, the one or more processors are further configured to perform the following steps:

    The historical login data stored in the RED-VALUE database in the form of a KEY-VALUE is used, and the registration ID, the device ID, and the login IP are used as KEYs, and the first login number, the second login number, and the third login number are respectively taken as Corresponding VALUE;

    Acquiring the historical login data between the current time of the system and the preset time period, and acquiring the first login number and the second login corresponding to the registration ID, the device ID, or the login IP by using a KEY-VALUE query manner. The number of times and the third number of logins.
20. A non-volatile readable storage medium as recited in claim 15, wherein said computer readable instructions are executed by one or more processors after said step of obtaining an authentication request sent by a client Having the one or more processors further perform the following steps:

    If the identity feature information is authenticated, a secure connection is established with the client through the identity verification request.

Images