CN108763889A - A kind of login validation method, device, equipment and readable storage medium storing program for executing - Google Patents

Abstract

The invention discloses a login verification method, which comprises the following steps: when the login verification request sent by the target user is obtained, reading the user login verification failure record file under the specified configuration file directory; finding and judging the target user login verification Whether the login verification failure record of the target user has been recorded in the failure record file; if it has been recorded, then use the preset conditions to determine whether the target user has the login verification qualification; if not, directly determine that the target user has the login verification qualification; if the target user If the user is qualified for login verification, the user data in the preset database is used to process the login verification request. Use the user login verification failure file to solve illegal users' violent cracking of username and password, and at the same time reduce the number of visits to the database. Improve login verification efficiency and enhance user experience. The invention also discloses a login verification device, equipment and a readable storage medium, which have corresponding technical effects.

Description

A login verification method, device, equipment and readable storage medium

technical field

The invention relates to the technical field of safety assurance, in particular to a login verification method, device, equipment and a readable storage medium.

Background technique

In order to strengthen the verification of user identity legality, more and more GUI (Graphical User Interface, Graphical User Interface) software has added authentication failure processing function to user login verification, so as to prevent illegal users from violently cracking username and password, and damage the system or user. Information wreaks havoc.

Currently, in order to prevent illegal users from violently cracking usernames and passwords, user login records are added to the database user information table, so that when each user initiates a login request, these records are used to prevent illegal users from cracking usernames and passwords violently. In this way, the data in the database is frequently accessed and processed, and the performance of the database is degraded. Especially when there is a large number of user login visits, the performance of the database will also deteriorate, and database queries will appear, and the update speed will be slow, which will lead to slow verification of user identity validity and affect user experience.

To sum up, how to effectively improve the efficiency of user login verification is a technical problem urgently needed to be solved by those skilled in the art.

Contents of the invention

The purpose of the present invention is to provide a login verification method, device, equipment and readable storage medium, so as to improve the efficiency of user login verification and improve user experience.

In order to solve the above technical problems, the present invention provides the following technical solutions:

A login verification method, comprising:

When the login verification request sent by the target user is obtained, read the user login verification failure record file under the specified configuration file directory;

Finding and judging whether the target user's login verification failure record has been recorded in the target user's login verification failure record file;

If it has been recorded, using preset conditions to determine whether the target user has login verification qualifications;

If not recorded, directly determine that the target user has the login verification qualification;

If the target user has the login verification qualification, the user data in a preset database is used to process the login verification request; wherein the user data includes login verification information of a legitimate user.

Preferably, before reading the user login verification failure record file under the specified configuration file directory, it also includes:

Import the user login verification failure record file into the designated configuration file directory; wherein, the user login verification record file records the number of login verification failures and the latest verification failure time of the user who failed the login verification.

Preferably, the use of preset conditions to determine whether the target user has login verification qualifications includes:

Reading the number of login verification failures of the target user, and judging whether the number of login verification failures exceeds a preset threshold;

If so, use the latest verification failure time of the target user to determine whether the login verification request falls outside the preset account lockout period, and determine the target user if it falls outside the preset account lockout period Qualified for login verification;

If not, it is determined that the target user is qualified for login verification.

Preferably, the processing of the login verification request using user data in a preset database includes:

When the login verification fails, update or add the target user's login verification failure record in the user login verification failure record file.

Preferably, the processing of the login verification request using user data in a preset database includes:

When the login verification is successful, the target user's login verification failure record is deleted from the user login verification failure record file.

A login verification device, comprising:

The file reading module is used to read the user login verification failure record file under the specified configuration file directory when the login verification request sent by the target user is obtained;

A login verification failure record search and judgment module, used to search and judge whether the target user's login verification failure record has been recorded in the target user's login verification failure record file;

The login verification qualification determination module is used to determine whether the target user has the login verification qualification if the target user's login verification failure record has been recorded in the target user's login verification failure record file by using preset conditions; If the login verification failure record of the target user is not recorded in the user login verification failure record file, it is directly determined that the target user has the login verification qualification;

A login verification request processing module, configured to use user data in a preset database to process the login verification request if the target user has the login verification qualification; wherein, the user data includes the login verification of a legal user information.

Preferably, it also includes:

The user login verification failure record file import module is used to import the user login verification failure record file into the specified configuration file directory before reading the user login verification failure record file under the specified configuration file directory; wherein the user The login verification record file records the number of login verification failures and the latest verification failure time of the user who failed the login verification.

Preferably, the login verification request processing module is specifically configured to update or add the target user's login verification failure record in the user login verification failure record file when the login verification fails.

A login verification device, comprising:

memory for storing computer programs;

A processor, configured to implement the steps of the above login verification method when executing the computer program.

A readable storage medium, where a computer program is stored on the readable storage medium, and when the computer program is executed by a processor, the steps of the above login verification method are realized.

Apply the method provided by the embodiment of the present invention, when the login verification request sent by the target user is obtained, read the user login verification failure record file under the specified configuration file directory; find and judge whether the target user login verification failure record file has Record the login verification failure record of the target user; if it has been recorded, use the preset conditions to determine whether the target user has the login verification qualification; if it is not recorded, directly determine that the target user has the login verification qualification; if the target user has the login verification qualification, Then use the user data in the preset database to process the login verification request; wherein, the user data includes the login verification information of the legal user. Before processing the login verification request, first use the user login verification failure record file under the specified configuration file directory to determine whether the target user has the login verification qualification. Only when the target user is qualified for login verification, the target user's login verification request is processed using a preset database. That is to say, while using the user login verification failure file to solve the problem of illegal users violently cracking the username and password, it can also reduce the number of visits to the database. Improve the verification efficiency of legitimate users and improve user experience.

Correspondingly, the embodiments of the present invention also provide a login verification device, equipment, and readable storage medium corresponding to the above login verification method, which have the above technical effects and will not be repeated here.

Description of drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

Fig. 1 is the implementation flowchart of a kind of login verification method in the embodiment of the present invention;

FIG. 2 is a flow chart of another login verification method in an embodiment of the present invention;

3 is a schematic diagram of a specific application flow of a login verification method in an embodiment of the present invention;

4 is a schematic structural diagram of a login verification device in an embodiment of the present invention;

Fig. 5 is a schematic structural diagram of a login verification device in an embodiment of the present invention.

Detailed ways

In order to enable those skilled in the art to better understand the solution of the present invention, the present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. Apparently, the described embodiments are only some of the embodiments of the present invention, but not all of them. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

Embodiment one:

Please refer to FIG. 1. FIG. 1 is a flow chart of a login verification method in an embodiment of the present invention. The method includes the following steps:

S101. When the login verification request sent by the target user is obtained, read the user login verification failure record file under the specified configuration file directory.

The target user can send a login verification request through GUI software or a command line terminal, and the login verification request can include a user name (or account number) and identity verification information (such as a password). When the login verification request sent by the target user is obtained, the user login verification failure file under the specified configuration file directory can be read. Specifically, the user login verification failure file is record information that records the user login verification failure of the specified software system. For example, information such as the number of failed logins, the time of failed logins, and the reason for failed logins can be recorded.

S102 Search and determine whether the target user's login verification failure record has been recorded in the target user's login verification failure record file.

After reading the user login verification failure file, you can determine whether there is a login verification failure record for the target user by searching and traversing the user login failure records in the user login verification failure file. If there is a log-in verification failure record, go to step S103; if there is no log-in verification failure record, go to step S104.

S103. Using preset conditions, determine whether the target user has login verification qualifications.

In this embodiment, conditions for judging whether the user has login verification qualifications may be preset. The specific content of the preset condition can be determined in advance, or can be confirmed and adjusted according to the actual situation, which is not limited here.

When the user login verification failure record file records the target user's login failure verification record, preset conditions can be used to determine whether the target user has the login verification qualification.

S104. Directly determine that the target user is qualified for login verification.

When the target user's login failure verification record is not recorded in the user login verification failure file, it can be considered that the target user is not suspected of brute force cracking, and at this time, the target user can be considered to have the login verification qualification.

S105. If the target user has the login verification qualification, process the login verification request by using the user data in the preset database.

Wherein, the user data includes the login verification information of the legal user.

After it is determined that the target user has the login verification qualification, the login verification request can be processed by using the user data in the preset database. Wherein, the preset database includes login verification information of legitimate users, that is, the login verification information of the target user can be used to judge and process the login verification request of the target user, and finally determine whether the target user successfully logs in.

Apply the method provided by the embodiment of the present invention, when the login verification request sent by the target user is obtained, read the user login verification failure record file under the specified configuration file directory; find and judge whether the target user login verification failure record file has Record the login verification failure record of the target user; if it has been recorded, use the preset conditions to determine whether the target user has the login verification qualification; if it is not recorded, directly determine that the target user has the login verification qualification; if the target user has the login verification qualification, Then use the user data in the preset database to process the login verification request; wherein, the user data includes the login verification information of the legal user. Before processing the login verification request, first use the user login verification failure record file under the specified configuration file directory to determine whether the target user has the login verification qualification. Only when the target user is qualified for login verification, the target user's login verification request is processed using a preset database. That is to say, while using the user login verification failure file to solve the problem of illegal users violently cracking the username and password, it can also reduce the number of visits to the database. Improve the verification efficiency of legitimate users and improve user experience.

It should be noted that, based on the first embodiment above, the embodiment of the present invention also provides a corresponding improvement solution. In subsequent embodiments, the same steps as in the first embodiment above or corresponding steps may be referred to each other, and the corresponding beneficial effects may also be referred to each other, and will not be repeated in the improved embodiments below.

Embodiment two:

Please refer to Figure 2, Figure 2 is a flowchart of another login verification method in an embodiment of the present invention, the method includes the following steps:

S201. Import the user login verification failure record file into a specified configuration file directory.

Wherein, the user login verification record file records the number of login verification failures and the latest verification failure time of the user who failed the login verification.

Specifically, a new user login verification failure record file can be created first, and information such as the number of login verification failures of the login verification failure user, the latest verification failure time (ie the last login verification failure time) and the like can be recorded in the user login failure record file. Then import the user login verification failure record file to the specified configuration file directory. If the current system has a configuration file directory, directly import the user login verification failure record file directly into this directory. Log files are imported into it. Since the configuration file is not in the database, accessing the login authentication failure record file will not interfere with the normal use of the database.

S202. When the login verification request sent by the target user is obtained, read the user login verification failure record file under the specified configuration file directory.

S203. Find and determine whether the target user's login verification failure record has been recorded in the target user's login verification failure record file.

If it has been recorded, go to step S204, if not, go to step S207.

S204. Read the number of login verification failures of the target user, and determine whether the number of login verification failures exceeds a preset threshold.

In this embodiment, in order to prevent illegal users from brute force cracking the user name and password, a threshold for limiting the number of login verification failures may be preset. Specifically, the specific value of the preset threshold may be predetermined, or may be determined and adjusted according to actual conditions, and is not limited here.

After reading the number of login verification failures of the target user, judge the number of login verification failures and the preset threshold.

If it exceeds the preset threshold, it means that the current target user may be suspected of brute force cracking the user name and password, then enter step S205; If there is no log-in verification failure record, and there is no suspicion of cracking the user name and password with huge profits, go to step S206,

S205. Using the latest verification failure time of the target user, determine whether the login verification request is outside the preset account lockout period, and determine that the target user is qualified for login verification if it is outside the preset account lockout period.

In this embodiment, the user account may also be locked after the number of login times of the user exceeds a preset threshold. Specifically, the interval between the last failed login verification and the next normal login verification can be set as the account lockout period. Specifically, the length of the preset account locking period can be predetermined, or can be determined and adjusted according to actual conditions, which is not limited here.

Using the latest verification time of the target user, it can be determined whether the initiation time of the currently obtained login verification request is outside the preset account lockout time. If it is outside the preset account lockout time, the login sent by the target user is considered Authentication requests undergo normal authentication processing. If the initiation time of the login verification request is within the preset account lockout time, it is considered that the target user sends too frequent login verification requests, and no processing may be performed to ensure the security of the user account.

S206. Determine that the target user is qualified for login verification.

If the number of login verification failures does not exceed the preset threshold, it indicates that the current target user may have a login verification failure record due to common reasons such as entering a wrong password, and there is no suspicion of cracking the username and password with huge profits for the time being. It can be considered that the target user is qualified for login verification.

S207. Directly determine that the target user is qualified for login verification.

S208. If the target user is qualified for login verification, process the login verification request by using the user data in the preset database.

Preferably, when the login verification request is processed, the user login verification failure record file can also be modified and adjusted so as to better match the actual application requirements. That is, when the login verification fails, the log-in verification failure record of the target user is updated or added in the user login verification failure record file. And/or, when the login verification is successful, the target user's login verification failure record is deleted from the user login verification failure record file.

That is to say, after the target user's login verification request is successfully verified, it can be considered that the log-in verification failure record about the target user in the login verification failure file may be that the target user enters the wrong user name or password when the normal login verification fails, and records it. of. Therefore, after it is determined that the target user has been successfully authenticated, the corresponding login verification failure record may be deleted from the user login verification failure record, so as to speed up the next login verification processing flow of the target user.

When the login verification request of the target user is verified and the verification fails, it can be considered that the target user is suspected of brute force cracking the user name and password, so the login verification failure needs to be recorded. Specifically, when the target user's failed login verification record has been recorded in the user login verification failure file, it is only necessary to add 1 to the number of failed login verifications in the file, and update the latest login verification time to the time of this login verification failure. When the failed login verification record of the target user is not recorded in the user login verification failure file, a login verification failure record needs to be created for the target user.

In order to facilitate those skilled in the art to better understand the technical solution provided by the embodiment of the present invention, the technical solution provided by the embodiment of the present invention will be described in detail below in conjunction with a specific login verification process.

In order to strengthen the verification of the validity of the user identity, more and more GUI software has added an authentication failure processing function for the validity of the user identity. The system is protected by limiting the number of login attempts, locking accounts for frequent login failures, and setting a lockout time to prevent illegal users from violently cracking usernames and passwords and causing damage to the system.

In order to realize this function, the existing solution is: the user enters the user name and password on the web login interface, and sends the user name and password to the logical processing layer, and the logical processing layer reads the user name, password, whether Login information such as lock, number of logins, last login failure time, etc., and use these login information to judge, and according to the judgment result, decide whether the user enters the system home page or prompts the corresponding error message on the login page. This function needs to add the last login failure time and login failure times fields in the database user information table. At the same time, this solution will frequently perform database query, update and other operations. Every time the database is operated, the data needs to be read into the memory and processed by the CPU. After the data is processed, the result is returned to the memory, and the memory is written into the database. Frequent data processing will cause the performance of the database to degrade. The verification becomes slower and affects the user experience.

The performance of the database is generally limited by the hardware configuration of the physical server. If the hardware configuration is high, the database performance will be good, and the database operation will return the verification result quickly, and the user experience will be good; if the hardware configuration is low, the physical server will not be able to respond to front-end requests, and the system will The illusion of being stuck greatly weakens the user experience. Another aspect that affects database performance is the size of each data table in the database. When the database table is large, the speed of reading the database table into the memory becomes slower, and only part of the table data can be read at a time. If the table data in the memory is read The retrieved data is not included, and the remaining data of the table needs to be loaded into the memory for retrieval until the data is retrieved.

Increasing the hardware configuration of the physical server will inevitably increase the hardware cost. If the size of the database is reduced and the number of operations on the database is reduced, the performance of the database can be improved, and the response speed when operating the database must be improved.

The technical solution provided by the embodiment of the present invention is to reduce the load on the database to achieve the purpose of optimizing performance without increasing the hardware configuration, thereby improving the processing efficiency of identifying users. Specifically, the technical solution provided by this embodiment of the present invention needs to add a user login failure record file to save the user login failure record result. After the Web layer sends the username and password to the logic processing layer, the logic processing layer retrieves the user login failure record file. Failure file, retrieve user login information, if the user has logged in more than 5 times (of course, in other embodiments of the present invention, it can also be other values) and the time of last login failure is not more than 30 minutes (of course, in the present invention In other embodiments, it can also be other durations), then the user is directly refused to log in without operating the database. Instant response can be achieved by retrieving user login failure files without operating the database. If the last login time and this login time exceed 30 minutes, query the database to obtain the user name and password comparison, and if it passes the verification, clear the user information in the user login failure record file. In this way, the frequent operation of the database is reduced, the number of login failures Error_time and the Last_log_time field of the last login failure time are reduced in the user information table, the database table stores less information, the database table loads into memory faster, and the retrieval data efficiency becomes faster. The optimized solution improves the processing efficiency of identifying the legitimacy of user identities by reducing database operations and performing partial verification at the logic processing layer.

Please refer to FIG. 3 for its specific processing flow. FIG. 3 is a schematic diagram of a specific application flow of a login verification method in an embodiment of the present invention.

S1. Enter the web system address in the browser to enter the system login page;

S2. The user enters the user name and password, and sends the user name and password to the logical processing layer;

S3, the logical processing layer reads the user login failure record file;

S4, find whether there is login user information (as the user name of the user who currently requests to log in) in the log-in failure record file, if there is no step S5, and if there is step S9;

S5, the logical processing layer queries the username and password, and compares it with the username and password of the Web layer;

Specifically, the logic processing layer queries the user name and password as the user name and password in the database.

S6, whether the verification of the username and password of the Web layer is passed;

Go to step S7 after passing the verification, otherwise go to step S8;

S7, complete the login on the system homepage;

S8. Record the login user information in the format of User_ErrorTime_Last_log_time;

S9. Retrieve the user login verification failure record file, and obtain the user's Error_time and Last_log_time;

S10, judging whether Error_time is greater than or equal to 5;

If yes, then enter step S11, if no, then enter step S13;

S11. The difference between the current time and the last login failure time, whether the time is greater than 30 minutes;

If yes, then enter step S20; if no, then enter step S12;

S12. Prompt the user on the login page that the account has been locked and login is prohibited;

S13, the logic processing layer queries the user name and password of the database, and verifies;

S14, judging whether the verification is passed;

If yes, enter step S15; if no, enter step S17;

S15. Complete the login on the system home page;

S16, delete the user information in the user login failure record file Login_error_record file;

S17. Modify the user information in the Login_error_record file, add 1 to ErrorTime, update Last_log_time to Current_time;

S18, query the database to obtain the user name and password, and compare with the user name and password of the Web layer;

If the verification is passed, then enter step S15; if the verification fails, then enter step S19;

S19. Modify the user information in the Login_error_record file, add 1 to Error_time, and update Last_log_time to Current_time.

Corresponding to the above method embodiments, an embodiment of the present invention also provides a login verification device, and the login verification device described below and the login verification method described above can be referred to in correspondence.

Referring to shown in Figure 4, the device includes the following modules:

The file reading module 101 is used to read the user login verification failure record file under the specified configuration file directory when the login verification request sent by the target user is obtained;

Login verification failure record search judgment module 102, for searching and judging whether the login verification failure record of the target user has been recorded in the target user login verification failure record file;

Login verification qualification determination module 103, for if the log-in verification failure record of the target user has been recorded in the target user login verification failure record file, then utilize preset conditions to determine whether the target user has login verification qualification; if the user login verification failure record file If the login verification failure record of the target user is not recorded in , it is directly determined that the target user has the login verification qualification;

The login verification request processing module 104 is configured to use user data in a preset database to process the login verification request if the target user has the login verification qualification; wherein, the user data includes login verification information of legal users.

Apply the device provided by the embodiment of the present invention, when the login verification request sent by the target user is obtained, read the user login verification failure record file under the specified configuration file directory; find and judge whether the target user login verification failure record file has Record the login verification failure record of the target user; if it has been recorded, use the preset conditions to determine whether the target user has the login verification qualification; if it is not recorded, directly determine that the target user has the login verification qualification; if the target user has the login verification qualification, Then use the user data in the preset database to process the login verification request; wherein, the user data includes the login verification information of the legal user. Before processing the login verification request, first use the user login verification failure record file under the specified configuration file directory to determine whether the target user has the login verification qualification. Only when the target user is qualified for login verification, the target user's login verification request is processed using a preset database. That is to say, while using the user login verification failure file to solve the problem of illegal users violently cracking the username and password, it can also reduce the number of visits to the database. Improve the verification efficiency of legitimate users and improve user experience.

In a specific embodiment of the present invention, it also includes:

The user login verification failure record file import module is used to import the user login verification failure record file into the specified configuration file directory before reading the user login verification failure record file under the specified configuration file directory; wherein, the user login verification record file Records the number of login authentication failures and the latest authentication failure time of the user whose login authentication failed.

In a specific embodiment of the present invention, the login verification request processing module 104 is specifically configured to update or add the target user's login verification failure record in the user login verification failure record file when the login verification fails.

In a specific implementation manner of the present invention, the login verification request processing module 104 is specifically used to

When the login verification succeeds, the target user's login verification failure record is deleted from the user login verification failure record file.

In a specific implementation manner of the present invention, the login verification qualification determination module 103 includes:

The failed login verification times judging unit is used to read the failed login verification times of the target user, and judge whether the failed login verification times exceed a preset threshold;

The account lock judging unit is used to determine whether the login verification request is outside the preset account lock period by using the latest verification failure time of the target user if the number of failed login verifications of the target user exceeds the preset threshold, and if it belongs to the preset account When the lockout period is outside, determine that the target user is qualified for login verification;

The login verification qualification determination unit is configured to determine that the target user has the login verification qualification if the number of failed login verifications of the target user does not exceed a preset threshold.

Corresponding to the above method embodiment, the embodiment of the present invention also provides a login verification device, and a login verification device described below and a login verification method described above can be referred to in correspondence.

As shown in Figure 5, the login verification device includes:

memory D1 for storing computer programs;

The processor D2 is configured to implement the steps of the login verification method in the above method embodiment when executing the computer program.

Corresponding to the above method embodiment, the embodiment of the present invention also provides a readable storage medium, and a readable storage medium described below and a login verification method described above can be referred to in correspondence.

A readable storage medium. A computer program is stored on the readable storage medium. When the computer program is executed by a processor, the steps of the login verification method in the above method embodiment are implemented.

The computer-readable storage medium may specifically be a USB flash drive, a mobile hard disk, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and other various storage devices that can store program codes. readable storage media.

Each embodiment in this specification is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same or similar parts of each embodiment can be referred to each other. As for the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and for the related information, please refer to the description of the method part.

Professionals can further realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software or a combination of the two. In order to clearly illustrate the possible For interchangeability, in the above description, the composition and steps of each example have been generally described according to their functions. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present invention.

The steps of the methods or algorithms described in connection with the embodiments disclosed herein may be directly implemented by hardware, software modules executed by a processor, or a combination of both. Software modules can be placed in random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other Any other known storage medium.

In this paper, specific examples are used to illustrate the principles and implementation methods of the present invention, and the descriptions of the above embodiments are only used to help understand the technical solutions and core ideas of the present invention. It should be pointed out that for those skilled in the art, without departing from the principles of the present invention, some improvements and modifications can also be made to the present invention, and these improvements and modifications also fall within the protection scope of the claims of the present invention.

Claims (10)

1. a kind of login validation method, which is characterized in that including：

When getting the login authentication request of target user's transmission, the user login validation under specified configuration file directory is read Failure record file；

Search and judge whether to have recorded in target user's login authentication failure record file the login of the target user Authentication failed records；

If recorded, preset condition is utilized, determines whether the target user has login authentication qualification；

If do not recorded, directly determine that the target user has the login authentication qualification；

If the target user has the login authentication qualification, using the user data in presetting database to the login Checking request is handled；Wherein, the user data includes the login authentication information of validated user.

2. login validation method according to claim 1, which is characterized in that under the reading specified configuration file directory User login validation failure record file before, further include：

User login validation failure record file is imported under specified configuration file directory；Wherein, the user login validation The login authentication frequency of failure of login authentication failure user, newest authentication failed time have been recorded in record file.

3. login validation method according to claim 2, which is characterized in that it is described to utilize preset condition, determine the mesh Mark whether user has login authentication qualification, including：

The login authentication frequency of failure of the target user is read, and judges whether the login authentication frequency of failure is more than default Threshold value；

If it does, then utilizing the newest authentication failed time of the target user, judge whether the login authentication request belongs to It is locked except the period in default account, and when belonging to except the default account locking period, determines target user's tool There is login authentication qualification；

If be less than, it is determined that the target user has login authentication qualification.

4. login validation method according to any one of claims 1 to 3, which is characterized in that described to utilize presetting database In user data to the login authentication request handle, including：

When login authentication fails, then the target user is updated or added in the user login validation failure record file Login authentication failure record.

5. login validation method according to any one of claims 1 to 3, which is characterized in that described to utilize presetting database In user data to the login authentication request handle, including：

When login authentication success, the login authentication failure record of the target user is unsuccessfully remembered from the user login validation It is deleted in record file.

6. a kind of login authentication device, which is characterized in that including：

File read module, for when getting the login authentication request of target user's transmission, reading specified configuration file mesh User login validation failure record file under record；

Login authentication failure record searches judgment module, for searching and judging target user's login authentication failure record text Whether the login authentication failure record of the target user has been recorded in part；

Login authentication qualification determining module, if for having recorded the mesh in target user's login authentication failure record file The login authentication failure record of user is marked, then utilizes preset condition, determines whether the target user has login authentication qualification； If not recording the login authentication failure record of the target user in the user login validation failure record file, directly really The fixed target user has the login authentication qualification；

Login authentication request processing module utilizes present count if having the login authentication qualification for the target user Login authentication request is handled according to the user data in library；Wherein, the user data includes stepping on for validated user Record verification information.

7. login authentication device according to claim 6, which is characterized in that further include：

User login validation failure record file import modul is stepped on for the user under the reading specified configuration file directory Before recording authentication failed record file, user login validation failure record file is imported under specified configuration file directory；Its In, the login authentication frequency of failure of login authentication failure user has been recorded in user login validation record file, newest has been tested Demonstrate,prove Time To Failure.

8. the login authentication device described according to claim 6 or 7, which is characterized in that login authentication request processing module, specifically For when login authentication fails, then the target user being updated or adding in the user login validation failure record file Login authentication failure record.

9. a kind of login authentication equipment, which is characterized in that including：

Memory, for storing computer program；

Processor, realizing the login validation method as described in any one of claim 1 to 5 when for executing the computer program Step.

10. a kind of readable storage medium storing program for executing, which is characterized in that be stored with computer program, the meter on the readable storage medium storing program for executing It is realized when calculation machine program is executed by processor as described in any one of claim 1 to 5 the step of login validation method.