WO2019232868A1

WO2019232868A1 - User information authentication method and apparatus, and computer device and storage medium

Info

Publication number: WO2019232868A1
Application number: PCT/CN2018/094343
Authority: WO
Inventors: 李云利; 李辉; 洪宇明; 石宇; 张文君; 孙雄; 张小敏
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-06-08
Filing date: 2018-07-03
Publication date: 2019-12-12
Also published as: CN109034816A

Abstract

Disclosed are a user information authentication method and apparatus, and a computer device and a storage medium. The user information authentication method comprises: obtaining a user information authentication request, the user information authentication request comprising a target user identification and a target service type; obtaining user authentication information based on the target user identification; obtaining reference authentication fields of the user information authentication request based on the target service type, wherein there are at least two reference authentication fields; querying user authentication information based on the reference authentication fields; and if each of the reference authentication fields queries the user authentication information for matching authentication data, responding to the user information authentication request. The method improves the efficiency of user information authentication.

Description

User information verification method, device, computer equipment and storage medium

This application is based on a Chinese invention patent application filed on June 08, 2018 with application number 201810585016.1 and entitled "User Information Verification Method, Device, Computer Equipment and Storage Medium" and claims its priority.

Technical field

The present application relates to the field of computer technology, and in particular, to a user information verification method, device, computer device, and storage medium.

Background technique

At present, when a user handles a business with high security requirements in an enterprise or platform, user information verification is usually required. For some user information, further authentication is required to implement the verification process, such as an ID card. Information and bank card information. However, when authenticating the user's identity card information and bank card information, both need to entrust a third-party platform for authentication, and corresponding fees must be paid to the third-party platform. Although this verification method can ensure the authenticity of user information, the verification process takes some time and the verification efficiency is low.

Summary of the Invention

Based on this, it is necessary to provide a user information verification method, device, computer equipment, and storage medium that can improve the efficiency of user information verification in response to the above technical problems.

A user information verification method includes:

Obtain a user information verification request. The user information verification request includes the target user identity and the target service type.

Obtaining user authentication information based on the target user identity;

Obtaining the reference verification fields of the user information verification request based on the target service type, wherein the reference verification fields are at least two;

Query user authentication information based on the benchmark authentication field;

If each of the benchmark verification fields finds matching verification data in the user verification information, it responds to the user information verification request.

A user information verification device includes:

A first obtaining module, configured to obtain a user information verification request, where the user information verification request includes a target user identifier and a target service type;

A second obtaining module, configured to obtain user authentication information based on the target user identifier;

A third obtaining module, configured to obtain the reference verification fields of the user information verification request based on the target service type, where the reference verification fields are at least two;

A query module for querying user authentication information based on the benchmark authentication field;

A first response module is configured to respond to the user information verification request if each of the benchmark verification fields queries matching verification data in the user verification information.

A computer device includes a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor. When the processor executes the computer-readable instructions, the following steps are implemented:

Obtaining user authentication information based on the target user identity;

One or more non-volatile readable storage media storing computer-readable instructions, which when executed by one or more processors, cause the one or more processors to perform the following steps:

Obtaining user authentication information based on the target user identity;

Details of one or more embodiments of the present application are set forth in the accompanying drawings and description below, and other features and advantages of the present application will become apparent from the description, the drawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to explain the technical solutions of the embodiments of the present application more clearly, the drawings used in the description of the embodiments of the application will be briefly introduced below. Obviously, the drawings in the following description are just some embodiments of the application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without paying creative labor.

FIG. 1 is a schematic diagram of an application environment of a user information verification method according to an embodiment of the present application; FIG.

2 is a flowchart of a user information verification method according to an embodiment of the present application;

3 is a flowchart of verifying login in a user information verification method according to an embodiment of the present application;

4 is a flowchart of integrating user authentication information in a user information authentication method according to an embodiment of the present application;

5 is a flowchart of implementing step S22 in a user information verification method according to an embodiment of the present application;

6 is a flowchart of verifying mismatched verification data in a user information verification method according to an embodiment of the present application;

7 is a flowchart of a user information verification method according to an embodiment of the present application;

FIG. 8 is a principle block diagram of a user information verification device in an embodiment of the present application; FIG.

FIG. 9 is a schematic diagram of a computer device in an embodiment of the present application.

Detailed ways

In the following, the technical solutions in the embodiments of the present application will be clearly and completely described with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of this application.

The user information verification method provided in this application can be applied in the application environment shown in FIG. 1, in which a client (computer device) communicates with a server through a network. The client obtains the user information verification request and sends the user information verification request to the server. After the server obtains the user information verification request, it processes it based on the user information verification request and responds to the user information verification request. Among them, the computer device may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices. The server can be implemented by an independent server or a server cluster composed of multiple servers.

In an embodiment, as shown in FIG. 2, a method for verifying user information is provided. The method is applied to the server in FIG. 1 as an example, and includes the following steps:

S10: Acquire a user information verification request. The user information verification request includes a target user identity and a target service type.

The user information verification request refers to a request for verifying identity information triggered by a user's need to handle corresponding services. The target user ID is a user ID corresponding to a user who authenticates user information. The user ID is suitable for distinguishing different users. For example, the user ID may be a user's ID number or an account ID uniquely corresponding to the user. The target service type refers to the type of target service that the user needs to handle. Different types of target services require different identity information to be verified.

S20: Acquire user authentication information based on the target user identity.

Because the target user ID is unique, the target user ID can be used as a search field to retrieve user authentication information of the target user ID. Optionally, user authentication information may be obtained in the big data platform based on the target user identification.

The user authentication information is authenticated user identity information. The user may need to verify the user identity information when performing other services. After verification, the corresponding user authentication data is formed. The user ’s The sum of the authentication data is its user authentication information. In this step, obtaining the user authentication information based on the target user ID is to obtain the user authentication information corresponding to the target user ID in the business that has been processed in the past through the target user ID. Optionally, the user authentication information may include at least one of the user's name, ID card number, mobile phone number, bank card number, or fingerprint information. The verification information corresponding to the mobile phone number, bank card number, and fingerprint information may be one or more.

For example, the user verification information verified by the user when conducting a service is the first mobile phone number, the first bank card number, and the fingerprint of the left thumb, and the user verification information verified by the other service is the second mobile phone number, the first Bank card number and right thumb fingerprint information. Therefore, the user authentication information of the user obtained based on the target user identification is the first mobile phone number, the second mobile phone number, the first bank card number, the left-hand thumb fingerprint information, and the right-hand thumb fingerprint information.

S30: Obtain a reference verification field of the user information verification request based on the target service type, where the reference verification field is at least two.

The benchmark verification field is a field corresponding to the user identity information that needs to be verified in the corresponding target service in the user information verification request. Specifically, there are at least two benchmark verification fields. For example, when the user identity information is verified, at least one field (for example, a bank card, an ID card, or a mobile phone number) is verified based on the name of the user. Therefore, there are at least two benchmark verification fields. For different target business types, the content to be verified will also be different. For example, for some general services, you may only need to verify the user ’s name, ID number, and mobile phone number, while for more core services, you may need to verify the user ’s name, ID number, mobile phone number, bank card number, and fingerprint information. Therefore, based on the target business type, a benchmark verification field of the target business type is obtained.

For example, for a target business type, when processing a target business of this type, the user's name, ID number, mobile phone number, and bank card number need to be verified, and then the base verification field of the user information verification request is obtained based on the target business type Name, ID number, mobile number, and bank card number.

S40: Query user authentication information based on the benchmark authentication field.

Specifically, according to the obtained reference verification field, the user authentication information is queried for user identity information that needs to be verified for the target service type. For example, if the reference verification field is a name, an ID number, a mobile phone number, and a bank card number, based on the above reference verification field, query whether there is corresponding verification data in the user verification information.

S50: If each benchmark verification field finds matching verification data in the user verification information, it responds to the user information verification request.

Specifically, matching verification data is found in the user verification information for each benchmark verification field, which means that there is verification data corresponding to the benchmark verification field in the user verification information. That is, if each benchmark verification field can successfully query the verification data matching the target service type in the user verification information, it responds to the user information verification request. Optionally, responding to the user information verification request may be a request to pass the user information verification.

In this embodiment, after obtaining the user authentication request, the server obtains user authentication information based on the target user ID in the user authentication request, and queries the user authentication information through the reference authentication field obtained based on the target service type. If all the fields in the user authentication information match the authentication data, they will respond to the user information authentication request. Through the above steps, repeated verification of user information that has already been verified when handling other services can be avoided, and the efficiency of user information verification is improved.

In an embodiment, as shown in FIG. 3, before step S10, the user information verification method further includes the following steps:

S11: Obtain login request information. The login request information includes a target user ID and a target user password.

In the embodiment of the present application, the login request information refers to information that is processed by the client after obtaining the input information of the user on the login interface and is sent to the server. The login request information includes the target user ID and the target user password. After the target user ID and the target user password constitute the login request information, the client sends the login request information to the server, and the server obtains the login request information.

Optionally, the target user ID and the target user password may also be obtained by the client after encrypting the login information input by the user. Encryption processing can ensure the security of login request information during data transmission.

S12: Verify the target user password based on the target user ID.

Specifically, the user enters or selects account login information according to certain prompt information when registering, wherein the account login information includes the user's original user ID and registration password. After the server obtains the account login information, the server logs in to the account. The information is stored in a registration record form. The process of verifying the target user password based on the target user ID is specifically: the server finds the corresponding original user ID in the registration record table based on the target user ID, and performs the registration password and target user password corresponding to the original user ID. Comparison. If the two are the same, the verification is successful.

Optionally, the server encrypts the registration password in the account login information in a preset manner, obtains the encrypted registration password, and stores it in the registration record table. At this time, the login request information sent by the client to the server is also encrypted. It should be noted that the way to encrypt the registration password is the same as the way to encrypt the login request information. Therefore, for the target user ID of the same user, if the entered login password is the same as the registered password, the encrypted target user password and encrypted registration password are also the same.

Further, after obtaining the login request information, the server queries the encrypted registration password of the target user ID in the registration record table based on the target user ID. If the encrypted registration password is the same as the target user password in the login request information, the target user Password verification succeeded.

S13: If the password verification of the target user is successful, the service type list is sent.

If the target user password is successfully verified, the user logs in successfully. After the user successfully logs in, the existing services in the platform are obtained, and the existing business table is generated and sent to the client for the user to choose. Optionally, the existing service table includes an existing service and a corresponding service type.

S14: Obtain a target service type, and generate a user information verification request based on the target user identifier and the target service type.

Specifically, the user selects a target service in the display interface of the client. The client uses the service type corresponding to the target service as the target service type, and generates a user information verification request based on the target service type and the target user identifier. The client then sends the user information verification request to the server, and the server obtains the user information verification request.

In this embodiment, the user can perform login operations on different platforms by using the same target user ID and target user password, eliminating the need to repeatedly register an account, and reducing the number of accounts because there is only one account information for the same user ID. The table capacity of the server registration record table saves storage space. Further, the user is authenticated with the login information before the user information is verified, thereby ensuring the security of the user information verification. Furthermore, by encrypting the user's login information on the client and transmitting it to the server for login verification, the security of the user's account information can be improved, and the risk of password leakage during data transmission can be effectively avoided.

In an embodiment, as shown in FIG. 4, before step S20 and after step S10, the user information verification method further includes the following steps:

S21: Obtain a user authentication data table for each interface.

The user authentication data table is a table for storing authentication data when a user handles different services, and uses the user's original user ID to distinguish each user's user authentication data table. The original user ID is a registered account set when the user is registered, and the user uniquely distinguishes different user IDs, such as an ID card number or an account ID.

Specifically, corresponding interfaces are set in different services for data interaction. After obtaining the user information verification request, the user verification data table of each interface is obtained to facilitate subsequent integration of the verification data table.

Optionally, a data extraction module may be added to each interface to extract a user authentication information data table. Optionally, the user authentication data table can be extracted from the database of each interface through the data extraction module and sent to the server. The server obtains the user authentication data table for each interface. Specifically, the user authentication data table of the same original user ID at each interface may be extracted in units of the original user ID.

Preferably, a data trigger may also be provided, which is used to record data change information when there is data change in the database of any interface. When the user authentication data table of any interface is detected to be added, deleted, or modified, a data trigger is used to send the changed user authentication data table to the big data platform through the data extraction module. The big data platform updates and replaces the original Some user authentication data sheets.

S22: Based on the same original user ID, the user authentication data table is integrated to obtain user authentication information.

Specifically, based on the same original user ID, duplicated verification data in the user authentication data table is combined or filtered, and the original user ID is used as a unit to form user authentication information of each original user ID.

Optionally, the user authentication data tables sent by the data extraction module can be received through the big data platform, and these user authentication data tables can be collated and then sent to the server to improve data integration efficiency.

In this embodiment, the user authentication data tables in each interface are obtained, and the user authentication data tables in each interface are integrated based on the same original user ID, so that the user authentication data of the same original user ID are in the same table. . When querying the corresponding authentication data in the user information verification, it is not necessary to obtain the corresponding user authentication data table on each interface, which saves query time and improves query efficiency.

In an embodiment, as shown in FIG. 5, in step S22, based on the same original user ID, the user authentication data table is integrated to obtain user authentication information, which specifically includes the following steps:

S221: Based on the same original user ID, the corresponding user authentication data is obtained in the user authentication data table, and the user authentication data includes the original user ID, the verification content, and the verification date.

The original user ID is a user ID of a different user in the user authentication data table. The verified content is the user identity information that the original user ID passed the verification. The verification date is the date on which the verification content passed verification.

S222: If user authentication data of the same authentication content exists in the same original user ID, obtain the authentication date in the user authentication data of the same authentication content as the target authentication date.

Specifically, after obtaining the verification content of the same original user ID, query whether the same verification content exists, for example, the first mobile phone number of the same original user ID has been verified in both the first interface and the second interface, then In the user authentication data corresponding to the original user identifier, there will be two user authentication data whose authentication content is the first mobile phone number. If the same verification content exists, the verification date corresponding to the same verification content is obtained as the target verification date.

S223: Sort the target verification dates, obtain the latest target verification date and the verification content corresponding to the latest target verification date, and delete the user verification data corresponding to the non-latest target verification date.

In this embodiment, the latest target verification date refers to a target verification date that is closest to the date when the user information verification request was obtained.

Specifically, after the target verification date is obtained, the target verification dates are sorted according to the time of the target verification date. After sorting the target verification dates, only the latest target verification date and the verification content corresponding to the latest target verification date are obtained, and the user verification data corresponding to the non-latest target verification date is deleted.

For example: The user has verified the name, ID number and first mobile phone number on the first interface and the second interface, and the target verification date of the user's name, ID number and first mobile phone number on the first interface is 2017 On March 15, 2014, and the target verification date of the user ’s name, ID number, and first mobile phone number on the second interface is May 8, 2017, the user ’s name, ID number, and first ID on the second interface The verification date of the mobile phone number is the latest target verification date, and the target verification date of the user's first interface name, ID card number, and first mobile phone number is a non-latest target verification date. At this time, the user authentication data of the verification content obtained from the first interface to be the name, the ID number, and the first mobile phone number will be deleted.

S224: Summarize user authentication data corresponding to the same original user ID to obtain user authentication information.

Further, after the same authentication content of the same original user ID is integrated, it is integrated with other authentication content of the same original user ID to obtain user authentication information of the original user ID.

In order to better understand the technical solution of this embodiment, the following describes a process of integrating the user authentication data table with a specific example, as follows:

For example, the verification data in the user verification data table of Zhang San in the first interface is name, ID card number, first mobile phone number, first bank card number, right thumb fingerprint, and verification date of each verification content; The verification data in the user verification data table of the second interface is the name, ID card number, second mobile phone number and second bank card number, and the verification date of each verification content.

Among them, Zhang San ’s name and ID number are the same verification content. Therefore, it is judged that Zhang San ’s name and ID number are on the verification date of the first interface and the second interface, respectively, through the operations of steps S223 and S224. After that, Zhang San ’s user verification information was Zhang San ’s name, ID card number, first mobile phone number, second mobile phone number, first bank card number, second bank card number, right thumb thumbprint, and the verification date of each verification content. .

In this embodiment, the same verification content is merged according to the target verification date, and the user verification data table is integrated to ensure the simplicity of the user verification information and improve the efficiency of subsequent queries.

In an embodiment, as shown in FIG. 6, after step S40, the user information verification method further includes the following steps:

S41: If there is at least one reference verification field and no matching verification data is found in the user verification information, the corresponding reference verification field is used as the target verification field.

Optionally, the existence of at least one reference verification field fails to query matching verification data in the user verification information, which means that there is at least one reference verification field, and corresponding verification data cannot be queried and obtained from the user verification information. For example, if the reference verification field is name and fingerprint information, and there is no fingerprint information in the user verification information, no verification data matching the fingerprint information can be queried in the user verification information.

Preferably, in the user verification information, the reference verification field for which no matching verification data is obtained further includes verification data corresponding to the reference verification field in the user verification information, but the timeliness of the verification data does not satisfy the target service. Type requirements. When the user's verification content is verified, the time limit for verification content is set according to the type of business. Among them, the time limit refers to the date from the date of verification to the acquisition of the target business type, and the date of verification refers to the date when the verification content passes the verification. Specifically, the timeliness of the verification data does not meet the requirements of the target service type, which may mean that the timeliness corresponding to the verification data exceeds the timeliness requirement of the verification data of the target service type.

For example: the target business type's time limit for verification data is half a year. If the verification date corresponding to the verification data in the user verification information is more than six months from the date of obtaining the target business type, it is determined that the time limit of the verification data does not meet The requirement of the target business type, that is, the verification data and the benchmark verification field do not match.

Therefore, if there is a reference verification field in the user verification information that does not obtain matching verification data, the reference verification field that does not obtain matching verification data is used as the target verification field to prompt the user to perform the target verification field verification.

S42: Send a target verification field verification request based on the target verification field.

Specifically, the target verification field verification request is sent to the client to prompt the user to verify the verification content corresponding to the target verification field. Preferably, the target verification field verification request includes a target verification field.

S43: Obtain the target verification information corresponding to the target verification field verification request. If the verification of the target verification information passes, it responds to the user information verification request.

Further, the user feeds back to the client the verification content contained in the verification request for the target verification field, and the client obtains the verification content and sends it to the server as the target verification information. The server verifies the target authentication information sent by the client and verifies. If the verification succeeds, it responds to the user information verification request.

In this embodiment, if there is a reference verification field for which no matching verification data is obtained in the user verification information, the corresponding reference verification field is verified to ensure the timeliness of user information verification, and at the same time, only the user is verified. In the verification information, the benchmark verification field of the matching verification data is not obtained, which is beneficial to improving the efficiency of user information verification.

In an embodiment, as shown in FIG. 7, in step S43, the user information verification request is responded. It includes the following steps:

S431: Obtain a service security level based on the target service type.

Specifically, the business security level means that because of different target business types, the business security level of the target business type is also different. For example, you can set the service security level according to the service price of the target service type. If the service price is higher, the corresponding target service type is also higher. According to different business security levels, different levels of user authentication requests are sent.

S432: Send a corresponding user authentication request based on the service security level and the target user identity.

Further, the user identity verification request may include but is not limited to: OTP (One-time Password), face recognition or short message verification, etc. The specific verification method may be determined by the service security level, which is not limited here. User authentication requests in different ways are sent according to different business security levels. Preferably, the higher the service security level, the stricter the corresponding user authentication request mode. For example, for ordinary business security levels, only text message verification is required, and for advanced business security levels, face recognition can be used for verification. Optionally, a combination of multiple verification methods may also be used for verification. For example, the user identity verification request may be a combination of face recognition and short message verification.

S433: Obtain user identity verification information. If the user identity verification information passes verification, the user information verification request verification passes.

The identity verification information refers to the verification information performed by the user according to the user authentication request. After the client obtains the identity verification information, it sends the identity verification information to the server. After the server obtains the user identity verification information, it performs verification. If the user identity verification information is verified, the user information verification request is verified.

Preferably, after obtaining the user identity verification information, the server verifies the user identity verification information based on the target user identity. Optionally, the user identity verification information may be compared with the user identity information stored in advance by the server. If the comparison result is a match, the user identity verification information is verified and the user information verification request is verified.

In this embodiment, the user is authenticated based on the service security level of the target service type to ensure that the user performs operations and provides verification-free operations on the verification data, which improves the security of user information and reduces information leakage. risk.

It should be understood that the size of the sequence numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

In one embodiment, a user information verification device is provided, and the user information verification device corresponds to the user information verification method in the above embodiment in a one-to-one correspondence. As shown in FIG. 8, the user information verification apparatus includes a first acquisition module 81, a second acquisition module 82, a third acquisition module 83, a query module 84, and a first response module 85. The detailed description of each function module is as follows:

A first obtaining module 81, configured to obtain a user information verification request, where the user information verification request includes a target user identifier and a target service type;

A second obtaining module 82, configured to obtain user authentication information based on a target user identifier;

A third obtaining module 83, configured to obtain a reference verification field of the user information verification request based on a target service type, where the reference verification field is at least two;

A query module 84, configured to query user authentication information based on the benchmark authentication field;

A first response module 85 is configured to respond to a user information verification request if each reference verification field queries the user verification information for matching verification data.

Preferably, the user information verification device further includes:

A login obtaining module 811, configured to obtain login request information, where the login request information includes a target user ID and a target user password;

A verification module 812, configured to verify a target user password based on the target user identifier;

A sending module 813 is configured to send a list of service types if the password verification of the target user is successful;

The request generating module 814 is configured to obtain a target service type, and generate a user information verification request based on the target user identifier and the target service type.

Preferably, the user information verification device further includes:

The interface acquisition module 821 is configured to acquire a user authentication data table of each interface;

The integration module 822 is configured to integrate the user authentication data table based on the same original user identifier to obtain user authentication information.

Preferably, the integration module 822 further includes:

The verification data acquisition submodule 8221 is configured to obtain corresponding user verification data in a user verification data table based on the same original user identity, and the user verification data includes the original user identity, verification content, and verification date;

The verification date acquisition submodule 8222 is used to obtain the verification date in the user verification data of the same verification content as the target verification date if the user verification data of the same verification content exists in the same original user identification;

The verification date sorting submodule 8223 is used to sort the target verification dates, obtain the latest target verification date after the sort and the verification content corresponding to the latest target verification date, and delete the user verification data corresponding to the non-latest target verification date. ;

The verification information collating sub-module 8224 is configured to summarize user verification data corresponding to the same original user ID to obtain user verification information.

Preferably, the user information verification device further includes:

A target verification field generating module 841, configured to use the corresponding benchmark verification field as a target verification field if at least one of the benchmark verification fields does not query matching verification data in the user verification information;

A sending module 842, configured to send a target verification field verification request based on the target verification field;

The second response module 843 is configured to obtain target verification information corresponding to the target verification field verification request. If the verification of the target verification information passes, it responds to the user information verification request.

Preferably, the second response module 843 includes:

A security level acquisition submodule 8431, configured to acquire a business security level based on a target service type;

An identity verification sub-module 8432, configured to send a corresponding user identity verification request based on the service security level and the target user identity;

A check submodule 8433 is configured to obtain user identity verification information. If the user identity verification information passes verification, the user information verification request verification passes.

For the specific limitation of the user information verification device, reference may be made to the limitation on the user information verification method described above, and details are not described herein again. Each module in the above-mentioned user information verification device may be implemented in whole or in part by software, hardware, and a combination thereof. The above-mentioned modules may be embedded in the hardware in or independent of the processor in the computer device, or may be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. 9. The computer device includes a processor, a memory, a network interface, and a database connected through a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer-readable instructions, and a database. The internal memory provides an environment for the operation of the operating system and computer-readable instructions in a non-volatile storage medium. The computer equipment database is used to store user authentication information. The network interface of the computer device is used to communicate with an external terminal through a network connection. The computer-readable instructions are executed by a processor to implement a method for verifying user information.

In one embodiment, a computer device is provided, including a memory, a processor, and computer-readable instructions stored on the memory and executable on the processor. When the processor executes the computer-readable instructions, the following steps are implemented:

Obtaining user authentication information based on the target user identity;

If each benchmark verification field finds matching verification data in the user verification information, it responds to the user information verification request.

In one embodiment, one or more non-volatile readable storage media storing computer-readable instructions are provided, and when the computer-readable instructions are executed by one or more processors, the one or more Each processor performs the following steps:

Obtaining user authentication information based on the target user identity;

A person of ordinary skill in the art can understand that all or part of the processes in the methods of the foregoing embodiments can be implemented by using computer-readable instructions to instruct related hardware. The computer-readable instructions can be stored in a non-volatile computer. In the readable storage medium, the computer-readable instructions, when executed, may include the processes of the embodiments of the methods described above. Wherein, any reference to the storage, storage, database, or other media used in the embodiments provided in this application may include non-volatile and / or volatile storage. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

Those skilled in the art can clearly understand that, for the convenience and brevity of the description, only the above-mentioned division of functional units and modules is used as an example. In practical applications, the above functions can be assigned by different functional units, Module completion, that is, dividing the internal structure of the device into different functional units or modules to complete all or part of the functions described above.

The above-mentioned embodiments are only used to describe the technical solution of the present application, but are not limited thereto. Although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still implement the foregoing implementations. The technical solutions described in the examples are modified, or some of the technical features are equivalently replaced; and these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the application, and should be included in Within the scope of this application.

Claims

A user information verification method, characterized in that the user information verification method includes:

Obtaining a user information verification request, where the user information verification request includes a target user identity and a target service type;

Obtaining user authentication information based on the target user identity;

Obtaining the reference verification fields of the user information verification request based on the target service type, wherein the reference verification fields are at least two;

Querying the user authentication information based on the benchmark authentication field;

If each of the benchmark verification fields finds matching verification data in the user verification information, it responds to the user information verification request.
The user information verification method according to claim 1, wherein before the step of obtaining a user information verification request, the user information verification method further comprises:

Obtaining login request information, where the login request information includes a target user ID and a target user password;

Verifying the target user password based on the target user identifier;

If the password verification of the target user is successful, sending a service type list;

Acquiring the target service type, and generating the user information verification request based on the target user identifier and the target service type.
The user information verification method according to claim 1, wherein before the step of obtaining user verification information based on the target user ID and after the step of obtaining user information verification request, the user information verification The method also includes:

Obtain user authentication data tables for each interface;

Based on the same original user identification, the user authentication data table is integrated to obtain the user authentication information.
The user information verification method according to claim 3, wherein the integrating the user verification data table based on the same original user identification to obtain the user verification information comprises:

Obtaining corresponding user verification data in the user verification data table based on the same original user identification, the user verification data including the original user identification, verification content and verification date;

If the user verification data of the same verification content exists in the same original user identifier, obtaining the verification date in the user verification data of the same verification content as a target verification date;

Sort the target verification dates, obtain the latest target verification date and the verification content corresponding to the latest target verification date, and delete the user verification data corresponding to the non-latest target verification date;

Summarizing the user authentication data corresponding to the same original user identifier to obtain the user authentication information.
The user information verification method according to claim 1, wherein after the step of querying user verification information based on the benchmark verification field, the user information verification method further comprises:

If at least one of the benchmark verification fields does not query for matching verification data in the user verification information, the corresponding benchmark verification field is used as the target verification field;

Sending a target verification field verification request based on the target verification field;

Acquire the target verification information corresponding to the target verification field verification request, and if the target verification information verification is passed, respond to the user information verification request.
The user information verification method according to claim 5, wherein the response to the user information verification request comprises:

Obtaining a service security level based on the target service type;

Sending a corresponding user identity verification request based on the service security level and the target user identity;

Acquire user identity verification information, and if the user identity verification information is verified, request verification through the user information verification request.
A user information verification device, comprising:

A first obtaining module, configured to obtain a user information verification request, where the user information verification request includes a target user identifier and a target service type;

A second obtaining module, configured to obtain user authentication information based on the target user identifier;

A third obtaining module, configured to obtain the reference verification fields of the user information verification request based on the target service type, where the reference verification fields are at least two;

A query module, configured to query user verification information based on the benchmark verification field;

A first response module is configured to respond to the user information verification request if each of the benchmark verification fields queries matching verification data in the user verification information.
The user information verification device according to claim 7, wherein the user information verification further comprises:

A login obtaining module, configured to obtain login request information, where the login request information includes a target user ID and a target user password;

A verification module, configured to verify the target user password based on the target user identifier;

A sending module, configured to send a list of service types if the target user password verification succeeds;

The request generating module is configured to obtain a target service type, and generate a user information verification request based on the target user identifier and the target service type.
A computer device includes a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor, and is characterized in that the processor implements the computer-readable instructions as follows step:

Obtaining a user information verification request, where the user information verification request includes a target user identity and a target service type;

Obtaining user authentication information based on the target user identity;

Obtaining the reference verification fields of the user information verification request based on the target service type, wherein the reference verification fields are at least two;

Querying the user authentication information based on the benchmark authentication field;

If each of the benchmark verification fields finds matching verification data in the user verification information, it responds to the user information verification request.
The computer device according to claim 9, wherein before the step of obtaining a user information verification request, the processor further implements the following steps when executing the computer-readable instructions:

Obtaining login request information, where the login request information includes a target user ID and a target user password;

Verifying the target user password based on the target user identifier;

If the password verification of the target user is successful, sending a service type list;

Acquiring the target service type, and generating the user information verification request based on the target user identifier and the target service type.
The computer device according to claim 9, wherein before the step of obtaining user authentication information based on the target user identifier and after the step of obtaining user information authentication request, the processor executes the step The computer-readable instructions also implement the following steps:

Obtain user authentication data tables for each interface;

Based on the same original user identification, the user authentication data table is integrated to obtain the user authentication information.
The computer device according to claim 11, wherein the integrating the user authentication data table based on the same original user identification to obtain the user authentication information specifically includes the following steps:

Obtaining corresponding user verification data in the user verification data table based on the same original user identification, the user verification data including the original user identification, verification content, and verification date;

If the user verification data of the same verification content exists in the same original user identifier, obtaining the verification date in the user verification data of the same verification content as a target verification date;

Sort the target verification date, obtain the latest target verification date and the verification content corresponding to the latest target verification date, and delete the user verification data corresponding to the latest target verification date;

Summarizing the user authentication data corresponding to the same original user identifier to obtain the user authentication information.
The computer device according to claim 9, wherein after the step of querying user authentication information based on the benchmark authentication field, the processor further implements the following steps when executing the computer-readable instructions:

If at least one of the benchmark verification fields does not query for matching verification data in the user verification information, the corresponding benchmark verification field is used as the target verification field;

Sending a target verification field verification request based on the target verification field;

Acquire the target verification information corresponding to the target verification field verification request, and if the target verification information verification is passed, respond to the user information verification request.
The computer device according to claim 13, wherein the responding to the user information verification request specifically comprises the following steps:

Obtaining a service security level based on the target service type;

Sending a corresponding user identity verification request based on the service security level and the target user identity;

Acquire user identity verification information, and if the user identity verification information is verified, request verification through the user information verification request.
One or more non-volatile readable storage media storing computer-readable instructions, which when executed by one or more processors, cause the one or more processors to perform the following steps:

Obtaining a user information verification request, where the user information verification request includes a target user identity and a target service type;

Obtaining user authentication information based on the target user identity;

Obtaining the reference verification fields of the user information verification request based on the target service type, wherein the reference verification fields are at least two;

Querying the user authentication information based on the benchmark authentication field;

If each of the benchmark verification fields finds matching verification data in the user verification information, it responds to the user information verification request.
The non-volatile readable storage medium according to claim 15, wherein before the step of obtaining a user information verification request, the computer-readable instructions are executed by one or more processors to cause all The one or more processors also perform the following steps:

Obtaining login request information, where the login request information includes a target user ID and a target user password;

Verifying the target user password based on the target user identifier;

If the password verification of the target user is successful, sending a service type list;

Acquiring the target service type, and generating the user information verification request based on the target user identifier and the target service type.
The non-volatile readable storage medium according to claim 15, wherein before the step of obtaining user authentication information based on the target user identity and after the step of obtaining user information authentication request, all When the computer-readable instructions are executed by one or more processors, the one or more processors further perform the following steps:

Obtain user authentication data tables for each interface;

Based on the same original user identification, the user authentication data table is integrated to obtain the user authentication information.
The non-volatile readable storage medium according to claim 17, wherein the integrating the user authentication data table based on the same original user identification to obtain the user authentication information, specifically comprises the following steps:

Obtaining corresponding user verification data in the user verification data table based on the same original user identification, the user verification data including the original user identification, verification content, and verification date;

If the user verification data of the same verification content exists in the same original user identifier, obtaining the verification date in the user verification data of the same verification content as a target verification date;

Sort the target verification dates, obtain the latest target verification date and the verification content corresponding to the latest target verification date, and delete the user verification data corresponding to the non-latest target verification date;

Summarizing the user authentication data corresponding to the same original user identifier to obtain the user authentication information.
The non-volatile readable storage medium of claim 15, wherein after the step of querying user authentication information based on the benchmark authentication field, the computer-readable instructions are executed by one or more processors. So that the one or more processors further perform the following steps:

If at least one of the benchmark verification fields does not query for matching verification data in the user verification information, the corresponding benchmark verification field is used as the target verification field;

Sending a target verification field verification request based on the target verification field;

Acquire the target verification information corresponding to the target verification field verification request, and if the target verification information verification is passed, respond to the user information verification request.
The non-volatile readable storage medium according to claim 19, wherein the response to the user information verification request specifically comprises the following steps:

Obtaining a service security level based on the target service type;

Sending a corresponding user identity verification request based on the service security level and the target user identity;

Acquire user identity verification information, and if the user identity verification information is verified, request verification through the user information verification request.