CN111680279A

CN111680279A - Login verification method, device and system

Info

Publication number: CN111680279A
Application number: CN202010497863.XA
Authority: CN
Inventors: 张良
Original assignee: Dongpu Software Co Ltd
Current assignee: Dongpu Software Co Ltd
Priority date: 2020-06-04
Filing date: 2020-06-04
Publication date: 2020-09-18
Anticipated expiration: 2040-06-04
Also published as: CN111680279B

Abstract

The invention discloses a login verification method, a login verification device and a login verification system, wherein the method comprises the following steps: receiving a login request; matching the user identity information with the user identity information in the first storage device; if the user identity information is successfully matched with at least one piece of user identity information of the first storage device, matching the login password with the login password in the first storage device; otherwise, matching the user identity information with the user identity information in the second storage device; if the user identity information is successfully matched with at least one user identity information in the second storage device, matching the login password with the login password in the second storage device; otherwise, sending out prompt information without user identity information to the user. The login verification method, the device and the system provided by the invention can solve the technical problem that the login verification effect in the prior art is not ideal.

Description

Login verification method, device and system

Technical Field

The present invention relates to the field of login verification technologies, and in particular, to a login verification method, device and system.

Background

With the development of technologies such as electronic commerce, social networks, commercial APPs and the like, Internet products are rapidly popularized, and a large number of users are accumulated. Especially, mobile phone software (mainly referring to software installed on a smart phone) can improve the defects of the original system, so that the functions of the mobile phone are more complete and personalized configuration is met, thereby providing richer use experience for users.

When logging in mobile phone software, a login user needs to be authenticated in order to ensure security. On one hand, the data security of the user can be ensured; on the other hand, normal use of the user can be guaranteed, and illegal use is prevented.

At present, when mobile phone software is logged in, only a password or a short message of a mobile phone is verified, which is not enough to meet strict requirements of some industries. Due to the defects in the prior art, the login verification effect is not ideal enough.

Disclosure of Invention

The invention aims to provide a login authentication method, a login authentication device and a login authentication system, which aim to solve the technical problem that the login authentication effect is not ideal.

The purpose of the invention is realized by adopting the following technical scheme:

a first aspect of the present invention provides a login authentication method, including:

receiving a login request, wherein the login request comprises user identity information and a login password;

matching the user identity information with the user identity information in the first storage device;

if the user identity information is successfully matched with at least one piece of user identity information of the first storage device, matching the login password with the login password in the first storage device; otherwise, matching the user identity information with the user identity information in the second storage device;

if the user identity information is successfully matched with at least one piece of user identity information in the second storage device, matching the login password with the login password in the second storage device; otherwise, sending out prompt information without user identity information to the user.

Matching the user identity information with the user identity information in the first storage device; if the user identity information is successfully matched with at least one piece of user identity information of the first storage device, matching the login password with the login password in the first storage device; otherwise, matching the user identity information with the user identity information in the second storage device; if the user identity information is successfully matched with at least one piece of user identity information in the second storage device, matching the login password with the login password in the second storage device; otherwise, sending a prompt message without the user identity information to the user; therefore, the situation that the first storage device or the second storage device is overloaded due to the fact that the user identity information and the login password are only matched from the first storage device or the second storage device can be avoided, the situation that login authentication fails due to the fact that the user identity information and the login password stored in the first storage device are incomplete can also be avoided, and therefore the login authentication effect is improved.

Optionally, the method further comprises:

verifying whether the login password is an initial password;

and if the password is the initial password, sending prompt information for modifying the password to the user.

Whether the login password is an initial password or not is verified; if the password is the initial password, prompt information for modifying the password is sent to the user, so that the user can be prompted to modify the initial password in time, and the use safety of the account is improved.

Optionally, the method further comprises:

if the login password is successfully matched with at least one login password in the first storage device or the second storage device, sending prompt information that the password is correct to the user; otherwise, sending out prompt information of user password error to the user.

When the login password is successfully matched with at least one login password in the first storage device or the second storage device, prompt information that the password is correct is sent to a user; and when the login password is unsuccessfully matched with the login password in the first storage device or the second storage device, sending prompt information of user password error to the user, so that the user can be prompted to input the password correctly or incorrectly, the user is guided to complete login operation, and the experience of login verification is enhanced.

Optionally, the login request further includes device information, and the method further includes:

matching the equipment information with the equipment information in the first storage device;

if the equipment information is successfully matched with at least one piece of equipment information in the first storage device, sending prompt information of successful equipment information matching to the user; otherwise, matching the equipment information with the equipment information in the second storage device;

if the equipment information is successfully matched with at least one piece of equipment information in the second storage device, sending prompt information of successful equipment information matching to the user; otherwise, sending out prompt information that the equipment information is not matched to the user.

By matching device information with device information in the first storage means; if the equipment information is successfully matched with at least one piece of equipment information in the first storage device, sending prompt information of successful equipment information matching to the user; otherwise, matching the equipment information with the equipment information in the second storage device; if the equipment information is successfully matched with at least one piece of equipment information in the second storage device, sending prompt information of successful equipment information matching to the user; otherwise, sending out prompt information that the equipment information is not matched to the user, so that the safety and the compliance of the account use can be improved, and the condition that the matching fails due to incomplete equipment information stored in the first storage device can be avoided.

Optionally, the method further comprises:

inquiring whether the first storage device has the company name and the area of the user according to the user identity information;

if the company name and the area of the user exist in the first storage device, acquiring the company name and the area of the user; otherwise, inquiring whether the company name and the region of the user exist in the second storage device according to the user identity information;

and if the company name and the area of the user exist in the second storage device, acquiring the company name and the area of the user from the second storage device and storing the company name and the area of the user in the first storage device.

Inquiring whether the first storage device has the company name and the area of the user according to the user identity information; if the company name and the area of the user exist in the first storage device, acquiring the company name and the area of the user; otherwise, inquiring whether the company name and the region of the user exist in the second storage device according to the user identity information; if the company name and the area of the user exist in the second storage device, the company name and the area of the user are obtained from the second storage device, so that the condition that the inquiry is failed due to the fact that the company name and the area of the user stored in the first storage device are not complete can be avoided. The problem that the company name and the area of the user in the first storage device are inconsistent can be solved by storing the company name and the area of the user in the first storage device, which are acquired from the second storage device, in the first storage device, and the data in the second storage device is used as basic data to update the data in the first storage device, so that the first storage device can automatically update the data.

Optionally, the method further comprises:

providing a plurality of usage records for selection by the user, wherein at least one usage record matches a pre-stored usage record;

acquiring the use record selected by the user;

matching the user-selected usage record with the pre-stored usage record;

and if the usage record selected by the user is not matched with the pre-stored usage record, determining that the user login is abnormal.

Providing a plurality of usage records for selection by the user, wherein at least one usage record matches a pre-stored usage record; acquiring the use record selected by the user; matching the user-selected usage record with the pre-stored usage record; and if the usage record selected by the user is not matched with the pre-stored usage record, determining that the user is logged in abnormally, so that the use safety and the compliance of the account can be further improved.

Optionally, the method further comprises:

recording the times of login requests, and sending prompt information with excessive login times to the user or carrying out login limiting processing on the login requests when the times reach a preset value.

By recording the times of login requests and sending prompt information with excessive login times to the user or carrying out login limiting processing on the login requests when the times reach a preset value, the occupation of repeated invalid login on resources is avoided.

Optionally, the first storage device is a Redis server, and the second storage device is a MySQL database.

Because the first storage device is a Redis server and the second storage device is a MySQL database, the advantage that the Redis server serves as a cache can be utilized, the login verification speed is improved, the advantage that the MySQL database serves as a persistent database can be taken into consideration, and the comprehensiveness of user data is guaranteed.

A second aspect of the present invention provides a login authentication apparatus, the apparatus comprising:

the system comprises a receiving module, a sending module and a processing module, wherein the receiving module is used for receiving a login request, and the login request comprises user identity information and a login password;

the first user identity information matching module is used for matching the user identity information with the user identity information in the first storage device;

the first login password matching module is used for matching the login password with the login password in the first storage device if the user identity information is successfully matched with at least one piece of user identity information in the first storage device;

the second user identity information matching module is used for matching the user identity information with the user identity information in the second storage device if the user identity information is not matched with any user identity information in the first storage device;

the second login password matching module is used for matching the login password with the login password in the second storage device if the user identity information is successfully matched with at least one piece of user identity information in the second storage device;

and the non-user identity information prompting module is used for sending prompting information without user identity information to the user if the user identity information is not matched with any user identity information in the second storage device.

Optionally, the apparatus further comprises:

the initial password checking module is used for checking whether the login password is an initial password or not;

and the password modification prompting module is used for sending prompting information of password modification to the user if the password is the initial password.

Optionally, the apparatus further comprises:

the password correct prompting module is used for sending prompt information that the password is correct to the user if the login password is successfully matched with at least one login password in the first storage device or the second storage device;

and the password error prompting module is used for sending out prompting information of user password error to the user if the login password is unsuccessfully matched with the login password in the first storage device or the second storage device.

Optionally, the login request further includes device information, and the apparatus further includes:

the first equipment information matching module is used for matching the equipment information with the equipment information in the first storage device;

the first device information matching success prompting module is used for sending prompting information that the device information is successfully matched to the user if the device information is successfully matched with at least one piece of device information in the first storage device;

the second equipment information matching module is used for matching the equipment information with the equipment information in the second storage device if the equipment information is unsuccessfully matched with the equipment information in the first storage device;

the second device information matching success prompting module is used for sending a prompting message of successful device information matching to the user if the device information is successfully matched with at least one piece of device information in the second storage device;

and the device information mismatch prompting module is used for sending out device information mismatch prompting information to the user if the device information is unsuccessfully matched with the device information in the second storage device.

By matching device information with device information in the first storage means; if the equipment information is successfully matched with at least one piece of equipment information in the first storage device, sending prompt information of successful equipment information matching to the user; otherwise, matching the equipment information with the equipment information in the second storage device; if the equipment information is successfully matched with at least one piece of equipment information in the second storage device, sending prompt information of successful equipment information matching to the user; otherwise, sending out prompt information that the equipment information is not matched to the user, so that the safety and the compliance of the account use can be improved, and the condition that the matching fails because the equipment information stored in the first storage device is incomplete can be avoided.

Optionally, the apparatus further comprises:

the first company name and located area query module is used for querying whether the first storage device has the company name and the located area of the user according to the user identity information;

a first company name and located area obtaining module, configured to obtain a company name and a located area of the user if the company name and the located area of the user exist in the first storage device;

the second company name and located area query module is used for querying whether the company name and the located area of the user exist in the second storage device according to the user identity information;

and the second company name and located area acquisition module is used for acquiring the company name and the located area of the user from the second storage device and storing the company name and the located area of the user into the first storage device if the company name and the located area of the user exist in the second storage device.

Optionally, the apparatus further comprises:

a usage record providing module for providing a plurality of usage records for selection by the user, wherein at least one usage record matches a pre-stored usage record;

the use record acquisition module is used for acquiring the use record selected by the user;

the usage record matching module is used for matching the usage record selected by the user with the pre-stored usage record;

and the login abnormity identification module is used for identifying that the user logs in abnormally if the usage record selected by the user is not matched with the pre-stored usage record.

Optionally, the apparatus further comprises:

and the login request control module is used for recording the times of login requests and sending prompt information of excessive login times to the user or carrying out login limiting processing on the login requests when the times reach a preset value.

A third aspect of the present invention provides a login verification system, where the system includes the login verification apparatus provided in the second aspect of the present invention, and the system further includes a first storage apparatus and a second storage apparatus, where the first storage apparatus is a Redis server, and the second storage apparatus is a MySQL database.

A fourth aspect of the invention provides an electronic device comprising a processor and a memory, said memory being configured to store executable instructions of said processor, said processor being configured to perform the steps of the above-mentioned login authentication method via execution of said executable instructions.

A fifth aspect of the present invention provides a computer-readable storage medium having stored thereon a computer program which, when executed, performs the steps of the login authentication method described above.

A sixth aspect of the invention provides a computer program product comprising instructions which, when run on a computer, cause the computer to carry out the above-mentioned login authentication method.

Drawings

The present application is further described below with reference to the drawings and examples.

Fig. 1 is a schematic flowchart of a login authentication method according to an embodiment of the present application;

fig. 2 is a schematic flowchart of another login authentication method provided in an embodiment of the present application;

fig. 3 is a schematic flowchart of another login authentication method provided in an embodiment of the present application;

fig. 4 is a schematic flowchart of another login authentication method provided in an embodiment of the present application;

fig. 5 is a schematic flowchart of another login authentication method provided in an embodiment of the present application;

fig. 6 is a schematic flowchart of another login authentication method provided in the embodiment of the present application;

fig. 7 is a schematic flowchart of another login authentication method provided in an embodiment of the present application;

fig. 8 is a schematic structural diagram of a login authentication device according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of another login authentication device provided in the embodiment of the present application;

fig. 10 is a schematic structural diagram of another login authentication device provided in the embodiment of the present application;

fig. 11 is a schematic structural diagram of another login authentication device provided in the embodiment of the present application;

fig. 12 is a schematic structural diagram of another login authentication device provided in the embodiment of the present application;

fig. 13 is a schematic structural diagram of another login authentication device according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of another login authentication device provided in the embodiment of the present application;

fig. 15 is a schematic structural diagram of a login authentication system according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of another login authentication system provided in the embodiment of the present application;

fig. 17 is a schematic flowchart of another login authentication method provided in the embodiment of the present application;

fig. 18 is a block diagram of an electronic device according to an embodiment of the present application.

Fig. 19 is a schematic structural diagram of a program product for implementing a login authentication method according to an embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the present application. It will be apparent, however, to one skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail.

In order to explain the technical means of the present invention, the following description will be given by way of specific examples.

Fig. 1 illustrates a login authentication method of the present application. As shown in fig. 1, the method may include:

and step S1, receiving a login request, wherein the login request comprises user identity information and a login password. The user identity information may be an account number, a user name, a mobile phone number, an identification number, and the like. Any information that can represent the identity of the user can be the user identity information in this application.

Step S2, matching the user identity information with the user identity information in the first storage device. Wherein the first storage device may be a Redis server. The user identity information in the first storage device is the user identity information of a legal registered user which is stored in advance, and can be obtained directly through the registration operation of the user or imported from other storage devices or equipment.

Step S3, if the user identity information matches successfully with at least one user identity information of the first storage device, matching the login password with the login password in the first storage device; otherwise, matching the user identity information with the user identity information in the second storage device. The login password in the first storage device may be a static password stored in the first storage device and corresponding to the user identity information; it may also be a dynamic password stored in the first storage device and randomly generated in response to the login request, the dynamic password being generated using a random algorithm, for example, using a hardware random number chip for selection of a random number seed, or using a true random number seed of a Linux kernel. The second storage may be a MySQL database. In general, there is only one user identity information in the first storage means that can be matched with the user identity information in the login request, and the user identity information in the login request will be successfully matched with the one user identity information in the first storage means. In a few cases, due to repeated data entry and the like, there may be a plurality of user identity information in the first storage device that can be matched with the user identity information in the login request, and the user identity information in the login request will be successfully matched with the plurality of user identity information in the first storage device. When the login password is a static password, the login password in the first storage device is a login password of a legal registered user, which is stored in advance, and the login password can be obtained directly through the registration operation of the user or can be imported from other storage devices or equipment. The user identity information in the second storage device is the user identity information of the legal registered user which is stored in advance, and can be obtained directly through the registration operation of the user or imported from other storage devices or equipment.

Step S4, if the user identity information is successfully matched with at least one user identity information in the second storage device, matching the login password with the login password in the second storage device; otherwise, sending out prompt information without user identity information to the user. The login password in the second storage device may be a static password stored in the second storage device and corresponding to the user identity information; it may also be a dynamic password stored in the second storage device and randomly generated in response to the login request, the dynamic password being generated using a random algorithm, for example, using a hardware random number chip for selection of a random number seed, or using a true random number seed of a Linux kernel. Likewise, in general, there is only one user identity information in the second storage means that can be matched with the user identity information in the login request, which will be successfully matched with the one user identity information of the second storage means. In a few cases, due to repeated data entry and the like, there may be a plurality of user identity information in the second storage device that can be matched with the user identity information in the login request, and the user identity information in the login request will be successfully matched with the plurality of user identity information in the second storage device. When the login password is a static password, the login password in the second storage device is a login password of a legal registered user which is stored in advance, and the login password can be directly obtained through the registration operation of the user or can be imported from other storage devices or equipment. The sending of the prompt information that the user identity information does not exist to the user may specifically be sending the prompt information of "no user identity information does not exist" to a login interface of the user.

Matching the user identity information with the user identity information in the first storage device; if the user identity information is successfully matched with at least one piece of user identity information of the first storage device, matching the login password with the login password in the first storage device; otherwise, matching the user identity information with the user identity information in the second storage device; if the user identity information is successfully matched with at least one piece of user identity information in the second storage device, matching the login password with the login password in the second storage device; otherwise, sending a prompt message without the user identity information to the user; therefore, the situation that the first storage device or the second storage device is overloaded due to the fact that the user identity information and the login password are only matched from the first storage device or the second storage device can be avoided, the situation that login authentication fails due to the fact that the user identity information and the login password stored in the first storage device are incomplete can also be avoided, and therefore the login authentication effect is improved. In addition, the first storage device is a Redis server, and the second storage device is a MySQL database, so that the advantage of the Redis server as a cache can be utilized, the login verification speed is improved, the advantage of the MySQL database as a persistent database can be taken into consideration, and the comprehensiveness of user data is ensured.

As an alternative embodiment, as shown in fig. 2, the method may further include:

and step S5, verifying whether the login password is an initial password. Specifically, the login password may be matched with a pre-stored initial password of the user, and if the matching is successful, the login password is determined to be the initial password; and if the matching is unsuccessful, the login password is determined not to be the initial password. As another embodiment, it may also be verified whether the login password meets a pre-configured password rule, and if so, the login password is determined to be an initial password; if not, the login password is determined not to be the initial password.

And step S6, if the password is the initial password, sending prompt information for modifying the password to the user. The sending of the prompt information for modifying the password to the user may specifically be sending the prompt information for "modifying the password" to the login interface of the user.

As an alternative embodiment, as shown in fig. 3, the method may further include:

step S7, if the login password is successfully matched with at least one login password in the first storage device or the second storage device, sending prompt information that the password is correct to the user; otherwise, sending out prompt information of user password error to the user. In general, there is only one login password in the first storage device or the second storage device that can be matched with the login password in the login request, and the login password in the login request will be successfully matched with the login password in the first storage device or the second storage device. In a few cases, due to repeated entry of data, etc., there may be a plurality of login passwords in the first storage device or the second storage device that can be matched with the login password in the login request, which will be successfully matched with the plurality of login passwords of the first storage device or the second storage device. Sending prompt information that the password is correct to the user, wherein the prompt information that the password is correct can be specifically pushed to a login interface of the user; sending a prompt message of the user password error to the user, specifically, sending a prompt message of 'password error' to a login interface of the user.

As an optional implementation manner, the login request may further include device information. As shown in fig. 4, the method may further include:

and step S8, matching the device information with the device information in the first storage device. The device information in the first storage device is the device information of a legal registered user stored in advance, and can be obtained directly through the registration operation of the user or imported from other storage devices or devices.

Step S9, if the device information is successfully matched with at least one device information in the first storage device, sending a prompt message indicating that the device information is successfully matched to the user; otherwise, matching the equipment information with the equipment information in the second storage device. In general, there is only one device information in the first storage apparatus that can be matched with the device information in the login request, and the device information in the login request will be successfully matched with the one device information in the first storage apparatus. In a few cases, due to repeated data entry and the like, there may be a plurality of pieces of device information in the first storage apparatus that can be matched with the device information in the login request, which will be successfully matched with the plurality of pieces of device information in the first storage apparatus. The device information in the second storage device is the device information of the legal registered user stored in advance, and can be obtained directly through the registration operation of the user or imported from other storage devices or devices. The prompt message that the device information matching is successful is sent to the user, and specifically, the prompt message that the device information matching is successful is pushed to a login interface of the user.

Step S10, if the device information is successfully matched with at least one device information in the second storage device, sending a prompt message indicating that the device information is successfully matched to the user; otherwise, sending out prompt information that the equipment information is not matched to the user. In general, there is only one device information in the second storage apparatus that can be matched with the device information in the login request, and the device information in the login request will be successfully matched with the one device information in the second storage apparatus. In a few cases, due to repeated data entry and the like, there may be a plurality of pieces of device information in the second storage apparatus that can be matched with the device information in the login request, and the device information in the login request will be successfully matched with the plurality of pieces of device information in the second storage apparatus. The prompt message that the device information matching is successful is sent to the user, and specifically, the prompt message that the device information matching is successful is pushed to a login interface of the user. Sending out prompt information that the device information is not matched to the user, which may specifically be pushing prompt information that the device information is not matched to a login interface of the user.

As another embodiment, before the step S8, it may be checked whether the device information is legal, and the step S8 may be executed under the condition that the device information is legal. And if the equipment information is illegal, directly determining that the user is abnormal in login. Wherein, whether the equipment information is legal or not is verified, which can be realized by the following method: checking whether the equipment information accords with a preset equipment information rule, and if so, determining that the equipment information is legal; if not, the equipment information is determined to be illegal.

As an alternative embodiment, as shown in fig. 5, the method may further include:

step S11, querying whether the first storage device has the company name and the area of the user according to the user identity information. The area where the user is located may be the name of the provincial and urban area where the user is located, or may be specific to the name of the community where the user is located. The company name and the location area in the first storage device are the company name and the location area of the legal registered user, which are stored in advance, and can be obtained directly through the registration operation of the user or can be imported from other storage devices or equipment.

Step S12, if the first storage device has the company name and the area, the company name and the area of the user are obtained; otherwise, inquiring whether the company name and the region of the user exist in the second storage device according to the user identity information. Similarly, the company name and the location area in the second storage device are the company name and the location area of the legal registered user, which are stored in advance, and can be obtained directly through the registration operation of the user, or can be imported from another storage device or equipment

Step S13, if the second storage device has the company name and the location area of the user, obtaining the company name and the location area of the user from the second storage device and storing the company name and the location area of the user in the first storage device. If the company name and the area of the user do not exist in the second storage device, the user can be considered to be logged in abnormally.

As an alternative embodiment, as shown in fig. 6, the method may further include:

step S14, providing a plurality of usage records for selection by the user, wherein at least one usage record matches a pre-stored usage record.

And step S15, acquiring the use record selected by the user. For example, the user selects the C selection.

And step S16, matching the usage record selected by the user with the pre-stored usage record. In particular, the amount of the solvent to be used,

and step S17, if the usage record selected by the user is not matched with the pre-stored usage record, determining that the user is logged in abnormally.

The usage record may be, among other things, a document recently sent by the user, an address, a recipient, a time, etc. In one embodiment, the following prompt messages may be pushed on the login interface of the user: please select the following order information sent within the previous week:

selecting a type;

b, selecting an option;

c, selecting an option;

and D, selecting.

When the type A is matched with the pre-stored use record and other types are not matched, if the user selects the type B, the type C or the type D, the user is determined to be logged abnormally; if the user selects the A selection type, the login verification of the current step is passed.

When the A selection type and the B selection type are matched with the pre-stored usage record, and the other selection types are not matched. And if the user selects the C type or the D type, determining that the user login is abnormal. If the user selects the A-type option and the B-type option, the login verification of the current step is passed.

As an alternative embodiment, as shown in fig. 7, the method may further include:

and step S18, recording the times of login requests, and sending prompt information of excessive login times to the user or carrying out login limiting processing on the login requests when the times reach a preset value. The preset value may be 4 times, 5 times, and the like, and may be specifically determined according to actual needs.

It should be understood that, the sequence numbers of the steps in the above embodiments do not mean the execution sequence, and the execution sequence of each process should be determined by the function and the inherent logic thereof, and should not constitute any limitation to the implementation process of the present application.

Fig. 8 shows a login authentication device provided in the present application. As shown in fig. 8, the apparatus may include:

the receiving module M1 is configured to receive a login request, where the login request includes user identity information and a login password;

the first user identity information matching module M2 is configured to match the user identity information with the user identity information in the first storage device. Wherein the first storage device may be a Redis server.

A first login password matching module M3, configured to match the login password with the login password in the first storage device if the user identity information is successfully matched with at least one user identity information of the first storage device.

And a second user identity information matching module M4, configured to match the user identity information with the user identity information in the second storage device if the user identity information is not matched with any user identity information in the first storage device. Wherein the second storage device may be a MySQL database.

A second login password matching module M5, configured to match the login password with the login password in the second storage device if the user identity information is successfully matched with at least one user identity information in the second storage device.

And the non-existing user identity information prompting module M6 is configured to send a prompting message to the user that the user identity information does not exist if the user identity information is not matched with any user identity information in the second storage device.

As an alternative embodiment, as shown in fig. 9, the apparatus may further include:

an initial password verifying module M7, configured to verify whether the login password is an initial password;

and a modified password prompting module M8, configured to send a prompt message for modifying the password to the user if the password is the initial password.

As an alternative embodiment, as shown in fig. 10, the apparatus may further include:

a password correctness prompting module M9, configured to send a prompt message that a password is correct to the user if the login password is successfully matched with at least one login password in the first storage device or the second storage device;

and the password error prompting module M10 is configured to send a user password error prompting message to the user if the login password is unsuccessfully matched with the login password in the first storage device or the second storage device.

As an optional implementation manner, the login request further includes device information. As shown in fig. 11, the apparatus may further include:

a first device information matching module M11, configured to match the device information with the device information in the first storage apparatus;

a first device information matching success prompting module M12, configured to send a notification message to the user that device information matching is successful if the device information is successfully matched with at least one device information in the first storage apparatus;

a second device information matching module M13, configured to match the device information with the device information in the second storage apparatus if the device information is unsuccessfully matched with the device information in the first storage apparatus;

a second device information matching success prompting module M14, configured to send a notification message that device information matching is successful to the user if the device information is successfully matched with at least one device information in the second storage apparatus;

and the device information mismatch prompting module M15 is configured to send a notification to the user that the device information does not match the device information in the second storage device if the device information does not match the device information in the second storage device successfully.

As an alternative embodiment, as shown in fig. 12, the apparatus may further include:

a first company name and location area query module M16, configured to query, according to the user identity information, whether the first storage device has the company name and the location area of the user;

a first company name and location area obtaining module M17, configured to obtain the company name and the location area of the user if the company name and the location area of the user exist in the first storage device;

a second company name and location area query module M18, configured to query, according to the user identity information, whether the company name and the location area of the user exist in the second storage device;

a second company name and location area obtaining module M19, configured to, if the company name and the location area of the user exist in the second storage device, obtain the company name and the location area of the user from the second storage device, and store the company name and the location area of the user in the first storage device.

As an alternative embodiment, as shown in fig. 13, the apparatus further includes:

a usage record providing module M20 for providing a plurality of usage records for selection by the user, wherein at least one usage record matches a pre-stored usage record;

a usage record obtaining module M21, configured to obtain the usage record selected by the user;

a usage record matching module M22, configured to match the usage record selected by the user with the pre-stored usage record;

a login exception determining module M23, configured to determine that the user login is abnormal if the usage record selected by the user does not match the pre-stored usage record.

As an alternative embodiment, as shown in fig. 14, the apparatus may further include:

and the login request control module M24 is configured to record the number of times of login requests, and send a prompt message indicating that the number of login times is too large to the user or perform login limiting processing on the login request when the number of times reaches a preset value.

It should be noted that the function implementation of each module in the login verification apparatus corresponds to each step in the login verification method embodiment, and the function and implementation process thereof are not described in detail here.

Fig. 15 shows a login authentication system provided in the present application. As shown in fig. 15, the system includes the login authentication device 100 provided in the above-described embodiment of the present invention. In addition, the system further comprises a first storage device 200 and a second storage device 300, wherein the first storage device 200 is a Redis server, and the second storage device 300 is a MySQL database.

Further, as shown in fig. 16, the system also includes a terminal device 400, which may be a cell phone, a handheld PC, a personal digital assistant, a portable media player, and various other devices. Generally, a device installed with application software can be understood as a terminal device of the present application.

Fig. 17 illustrates a login authentication method provided in the present application. As shown in fig. 17, the method includes:

and the login times are checked and the login times are + 1. After the login time verification module receives a login request of a terminal, the login service module firstly sends login time verification to the login time verification service module, the login time verification service module enables the login time to be +1, and the login time verification service module obtains the current login time from the Redis server. And the login time number verification service module performs login time number verification. And if the login times are excessive, a limit prompt is sent. Specifically, a login times verification module box Redis server sends login times +1, and the Redis server sends the current login times to a login times verification module; when the login times are too many, for example, more than 5 times, the response result is fed back to the login service module: the login frequency is too many; if the number of times of response exceeds the limit number, the response result is fed back: landing. Typically, it may not be displayed to the user.

And checking whether the user account/mobile phone state is correct. And the mobile phone verification module calls and verifies the user information data and verifies the equipment. Firstly, user information of a user is acquired from a Redis server according to a login account/mobile phone number of the user so as to acquire whether the account/mobile phone number exists or not. If the user information exists in the Redis database and is successfully acquired, the login password is verified, and if the login password is correct, the response result is as follows: the password is correct; otherwise, responding to the password error. Meanwhile, the terminal verification module calls user information from the MySQL database. If the user information is not acquired from the Redis server, calling a MySQL database to acquire the user information by using the mobile phone number, and checking whether the calling of the database is successful or not, wherein the data may be a new account after the calling is successful; then, the terminal verification module verifies whether the data exist, and responds to the result: with or without data. And then, whether the password is the initial password or not is verified, and a response result is fed back (if the password is the initial password, the password is prompted to be modified). After the user logs in, the user also needs to verify whether the device number is the same as that during registration.

Verifying whether the device number is legal and acquiring the device number (or the mobile phone number). Similarly, the device number is obtained in the Redis server, and whether the device numbers match is checked. And if not, acquiring the equipment number from the MySQL server and then checking. Firstly, the login service module requests the device verification module to verify whether the device number of the login device is legal or not, then the device verification module requests the Redis server to inquire device data corresponding to the account, the Redis server feeds back the device data, whether the verification device data is matched with the login device or not is verified, and the login service module feeds back that the device number is matched or not. And if the Redis server does not acquire the equipment number, the equipment checking module requests the MySQL database to call the database to inquire the equipment number, and checks and feeds back the matching or mismatching of the equipment number.

The user company name and the provincial and urban area names are obtained. Specifically, address information in the cache exists in a cache table, whether the data exist or not is judged in the cache, if the data do not exist, a MySQL database is called to obtain a company name and a provincial and urban area name, and user information is loaded into a Redis server after the data are verified to be not empty. For example, the account registration of the user is in the XX area of the XX website of Shanghai city, and the user automatically feeds back the information when logging in.

And performing work verification by using the content of the previous time of the user. And verifying the content related to the service used by the user in the previous period, and judging whether the user is abnormal or not according to the use state of the user. For example, the user uses the data of documents, addresses, recipients, time and the like sent by the APP in the last week as an authentication title for the user to select when logging in. By way of example only, please pick out the following order information that was sent within the previous week: A. b, C, D option, multiple choice.

According to the steps of the login verification method, the Redis server and the MySQL database can be well utilized to acquire and verify information, the information acquisition of a newly registered user is perfected, meanwhile, the problem that the information of the Redis server and the MySQL database is not uniform can be solved, the MySQL database can be used as basic data to update data to the Redis server, and the self-updating of the Redis server is achieved. In addition, the login verification of the user service information is newly added, so that the use safety and the compliance of the account can be improved.

Referring to fig. 18, the present application provides an electronic device 3, the electronic device 3 comprising at least one memory unit 31, at least one processing unit 32 and a bus 33 connecting different platform systems.

The storage unit 31 may include readable media in the form of volatile storage units, such as a random access memory unit (RAM)311 and/or a cache memory unit 312, and may further include a read only memory unit (ROM) 313.

Wherein the storage unit 31 further stores a program product 4, the program product 4 being executable by the processing unit 32, such that the processing unit 32 performs the steps of the login authentication method in the above embodiments (as shown in fig. 1-7). The storage unit 31 may also include a program/utility 314 having a set (at least one) of program modules 315, including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.

Accordingly, the processing unit 32 may execute the program product 4 described above, and may execute the program/utility 314.

Bus 33 may be one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

The electronic device 3 may also communicate with one or more external devices 34, such as a keyboard, pointing device, bluetooth device, etc., and may also communicate with one or more devices capable of interacting with the electronic device 3, and/or with any device (e.g., router, modem, etc.) that enables the electronic device 3 to communicate with one or more other computing devices. Such communication may be through input/output (I/O) interfaces 35. Also, the electronic device 3 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 36. The network adapter 36 may communicate with other modules of the electronic device 3 via the bus 33. It should be appreciated that although not shown in FIG. 18, other hardware and/or software modules may be used in conjunction with the electronic device 3, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage platforms, to name a few.

The present application also provides a computer-readable storage medium for storing a computer program which, when executed, implements the steps of the login authentication method in the above embodiments (as shown in fig. 1-7).

Fig. 19 shows a program product 4 provided by the present embodiment for implementing the above method, which may employ a portable compact disc read only memory (CD-ROM) and include program codes, and may be run on a terminal device, such as a personal computer. However, the program product 4 of the present invention is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. Program product 4 may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

A computer readable storage medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable storage medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing. Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

The foregoing description and drawings are only for purposes of illustrating the preferred embodiments of the present application and are not intended to limit the present application, which is, therefore, to the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present application.

Claims

1. A login authentication method, the method comprising:

2. The login authentication method of claim 1, further comprising:

verifying whether the login password is an initial password;

3. The login authentication method of claim 1, further comprising:

4. The login authentication method of claim 1, wherein the login request further comprises device information, the method further comprising:

5. The login authentication method of claim 1, further comprising:

6. The login authentication method of claim 1, further comprising:

acquiring the use record selected by the user;

matching the user-selected usage record with the pre-stored usage record;

7. The login authentication method of claim 1, further comprising:

8. A login verification method according to any one of claims 1 to 7, wherein said first storage means is a Redis server and said second storage means is a MySQL database.

9. A login authentication apparatus, the apparatus comprising:

10. A login verification system comprising the login verification apparatus of claim 9, the system further comprising a first storage apparatus and a second storage apparatus, wherein the first storage apparatus is a Redis server and the second storage apparatus is a MySQL database.