Personnel information authentication method and system based on email address

Abstract

The present invention discloses a personnel information authentication method and system based on email addresses, which sets the company that maintains or develops a data sharing system as a first type of enterprise, and sets the company that uses the data sharing system as a second type of enterprise. During the login process, the user account and user password corresponding to the logged-in user are bound to a data transmission model by parsing the body data stream and the data in the header in the post request, and perform basic verification and secondary verification on the user account and user password in the data transmission model. After the verification is passed, it is determined whether the personnel type in the account details data model is an employee of the second type of enterprise. If so, the SmtpClient and the Smtp mail sending server are used to perform email verification according to the email address in the account details data model. If the verification is passed, the user logs in to the data sharing system, which solves the problem in the prior art that the data sharing system cannot identify whether the partner's logged-in user has resigned, which leads to easy leakage of information.

Description

Technical Field

[0001] The present invention relates to the field of user login information verification, and in particular to a personnel information authentication method and system based on an email address. Background Art

[0002] Enterprises often need to provide information to partners. To facilitate both themselves (system maintainers or developers) and their partners, they may develop a data sharing system that is accessed via an account and password. However, this can lead to a problem. For example, when a partner's employee leaves, the system cannot identify whether they have left. Therefore, the former employee can still log in to the data sharing system, which may lead to the leakage of important information. If this technical difficulty cannot be resolved, it will hinder the interconnection and interoperability between enterprises. Currently, there are two main methods to solve this technical difficulty:

[0003] The first method is to communicate with the partner to confirm whether the account needs to be closed. This method is time-consuming and may cause communication to be delayed or forgotten.

[0004] The second method is to assign administrators to partners to manage their accounts. However, since this method is not a local system, the administrators may forget about it, or personnel turnover may lead to no one managing it. Both methods are manual and highly uncertain, and they are likely to result in the leakage of important information.

[0005] Experience has shown that most companies have a resignation process, and after leaving, employees will disable their corresponding accounts and email addresses (these accounts and email addresses refer to the accounts and email addresses registered by employees in other systems within their company. Generally, companies will assign accounts (employee numbers) and email addresses to employees after they join the company. For example, access control and business system logins are generally done using employee numbers, and important work communication uses email addresses) to ensure information security. Based on this, the present invention verifies whether the registered email address of the partner employee is valid before logging into the data sharing system, solving the problem of data leakage in the existing technology because the data sharing system cannot identify whether the partner login user has left the company. Summary of the Invention

[0006] In order to prevent data leakage in a data sharing system, the present invention proposes a personnel information authentication method based on an email address, which is applied to a data sharing system used by a first type of enterprise and a second type of enterprise. The first type of enterprise is a company that maintains or develops the data sharing system, and the second type of enterprise is a company that uses the data sharing system. The method comprises the following steps:

[0007] S1: Obtain the login information input by the front-end, encrypt it, and send a post request containing the encrypted login information to the back-end; the encrypted login information includes: user account and encrypted login password;

[0008] S2: responds to the post request sent by the front-end, and binds the user account and password to the data transmission model by parsing the body data stream and header data in the post request;

[0009] S3: Perform a basic verification on the user account and user password in the data transmission model. Based on the user account that passes the basic verification, obtain its corresponding account details data model from the database. Perform a secondary verification on the user account and user password in the data transmission model using the account details data model. After the verification passes, proceed to the next step. The account details data model includes the user's registered account, password, email address, and person type. The person type is either a first-type enterprise employee or a second-type enterprise employee.

[0010] S4: Determine whether the person type in the account details data model is a second-type enterprise employee. If so, perform email verification using SmtpClient and the Smtp email sending server based on the email address in the account details data model. If the verification is successful, log in to the data sharing system.

[0011] Furthermore, in step S2, the user account and user password are bound to the data transmission model, specifically including:

[0012] Read the body data stream in the post request and convert it into a string data in UTF-8 format;

[0013] Read the value of Content-Type in the header and determine whether the value of Content-Type is application / json. If so, use the Newtosoft.Json plug-in to deserialize the string data into a predefined data transmission model. If not, determine whether the value of Content-Type is application / x-www-form-urlencoded. If so, split the string data with the first preset symbol as the delimiter to obtain the split data set, traverse the data set, and split each data item in the data set with the second preset symbol as the delimiter, and assign the split data to the data transmission model.

[0014] Furthermore, the step S4 specifically includes:

[0015] S41: Determine whether the person type in the account details data model is a second-type enterprise employee. If not, log in to the data sharing system. If so, proceed to the next step.

[0016] S42: Create an email sending object; the email sending object includes: email subject, email content and recipient email address; wherein the recipient email address is the email address in the account details data model corresponding to the logged-in user;

[0017] S43: Instantiate SmtpClient and connect to the Smtp mail sending server through the instantiated SmtpClient;

[0018] S44: Verify through the instantiated SmtpClient whether the client password preset in the SmtpClient is consistent with the server password pre-stored in the Smtp mail sending server. If so, deliver the mail sending object to the Smtp mail sending server through the instantiated SmtpClient and determine whether the delivery is successful. If so, log in to the data sharing system.

[0019] Furthermore, an untrusted server instance is built in the Smtp mail sending server;

[0020] In the step S44, the mail sending object is delivered to the untrusted server through the instantiated SmtpClient; the untrusted server is used to forward the mail sending object to the recipient mailbox in the mail sending object.

[0021] Furthermore, in step S3, the basic verification is specifically as follows:

[0022] Determine whether the user account and user password in the data transmission model are empty. If either one is empty, a prompt indicating that the user account or user password is incorrect is returned to the front end. If both are not empty, a secondary verification is started.

[0023] The present invention also proposes a personnel information authentication system based on an email address, which is applied to a data sharing system used by a first type of enterprise and a second type of enterprise. The first type of enterprise is a company that maintains or develops the data sharing system, and the second type of enterprise is a company that uses the data sharing system. The system includes:

[0024] The front-end request sending module is used to obtain the login information input by the front-end, encrypt it, and send a post request containing the encrypted login information to the back-end; the encrypted login information includes: user account and encrypted login password;

[0025] The backend parsing module is used to respond to the post request sent by the frontend and bind the user account and password to the data transmission model by parsing the body data stream and the data in the header of the post request;

[0026] A background verification module is used to perform basic verification on the user account and user password in the data transmission model, and based on the user account that passes the basic verification, obtain its corresponding account details data model from the database, and perform a secondary verification on the user account and user password in the data transmission model using the account details data model; the account details data model includes the user's registered account, password, email address, and person type; the person type is a first-type enterprise employee or a second-type enterprise employee;

[0027] The email verification module is used to perform email verification using SmtpClient and the Smtp email sending server based on the email address in the account details data model when the secondary verification is passed and the person type in the account details data model is the second type of enterprise employee. If the verification is passed, the user can log in to the data sharing system.

[0028] Furthermore, in the background analysis module, the user account and user password are bound to the data transmission model, specifically including:

[0029] Read the body data stream in the post request and convert it into a string data in UTF-8 format;

[0030] Read the value of Content-Type in the header and determine whether the value of Content-Type is application / json. If so, use the Newtosoft.Json plug-in to deserialize the string data into a predefined data transmission model. If not, determine whether the value of Content-Type is application / x-www-form-urlencoded. If so, split the string data with the first preset symbol as the delimiter to obtain the split data set, traverse the data set, and split each data item in the data set with the second preset symbol as the delimiter, and assign the split data to the data transmission model.

[0031] Furthermore, the email verification module specifically includes:

[0032] A personnel type determination unit, configured to determine whether the personnel type in the account details data model is a second-type enterprise employee;

[0033] An object creation unit, configured to create an email sending object when the person type in the account details data model is a second type enterprise employee; the email sending object includes: an email subject, email content, and a recipient email address; wherein the recipient email address is the email address in the account details data model corresponding to the logged-in user;

[0034] The instantiation unit is used to instantiate SmtpClient and connect to the Smtp mail sending server through the instantiated SmtpClient;

[0035] The mailbox verification unit is used to verify whether the client password preset in the SmtpClient is consistent with the server password pre-stored in the Smtp mail sending server through the instantiated SmtpClient, and when the verification is consistent, deliver the mail sending object to the Smtp mail sending server through the instantiated SmtpClient, determine whether the delivery is successful, and log in to the data sharing system after the delivery is successful.

[0036] Furthermore, an untrusted server instance is built in the Smtp mail sending server;

[0037] In the mailbox verification unit, the mail sending object is delivered to the untrusted server through the instantiated SmtpClient; the untrusted server is used to forward the mail sending object to the recipient mailbox in the mail sending object.

[0038] Furthermore, in the background verification module, the basic verification is specifically as follows:

[0039] Determine whether the user account and user password in the data transmission model are empty. If either one is empty, a prompt indicating that the user account or user password is incorrect is returned to the front end. If both are not empty, a secondary verification is started.

[0040] Compared with the prior art, the present invention has at least the following beneficial effects:

[0041] The present invention sets the company that maintains or develops the data sharing system as a first type of enterprise, and sets the company that uses the data sharing system as a second type of enterprise (i.e., a partner enterprise). During the login process, the user account and user password corresponding to the logged-in user are bound to a data transmission model by parsing the body data stream and the data in the header in the post request, and a basic verification is performed on the user account and user password in the data transmission model. Based on the user account that passes the basic verification, the corresponding account details data model is obtained from the database, and a secondary verification is performed based on the model. After the secondary verification passes, it is determined whether the person type in the account details data model is an employee of the second type of enterprise. If so, the email address in the account details data model is used to perform email verification using SmtpClient and the Smtp email sending server. If the verification passes, the user logs into the data sharing system. The present invention is based on the rule that the corresponding account and email address of an employee of a general enterprise will be disabled after leaving the company. When the logged-in user is an employee of the partner enterprise, the login is performed using email verification, which solves the problem in the prior art that data is easily leaked because the data sharing system cannot identify whether the partner login user has left the company. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 This is a flow chart of a personnel information authentication method based on email addresses;

[0043] Figure 2 This is a module diagram of a personnel information authentication system based on email addresses. DETAILED DESCRIPTION

[0044] The following are specific embodiments of the present invention and the accompanying drawings to further describe the technical solutions of the present invention, but the present invention is not limited to these embodiments.

[0045] Example 1

[0046] In order to improve the security of data in the data sharing system and solve the problem in the existing technology that the data sharing system cannot identify whether the partner’s logged-in user has resigned, which leads to the easy leakage of data, such as Figure 1 As shown, the present invention proposes a personnel information authentication method based on an email address, which is applied to a data sharing system used by a first type of enterprise and a second type of enterprise. The first type of enterprise is a company that maintains or develops the data sharing system, and the second type of enterprise is a company that uses the data sharing system.

[0047] It should be noted that after an employee of a company that maintains or develops a data sharing system completes the resignation process, the corresponding account in the data sharing system will be cancelled, so email verification is not required. However, the accounts used by the second type of enterprise (partner enterprise) are all provided by the company that maintains or develops the data sharing system, that is, the first type of enterprise. Therefore, after an employee resigns, the cancellation is often delayed or forgotten due to untimely communication, resulting in the resigned user still being able to log in to the system. To solve this problem, the present invention proposes the following authentication steps:

[0048] S1: Get the login information input by the front-end, encrypt it using MD5 (specifically encrypt the login password), and use the axios plug-in to send a post request containing the encrypted login information to the back-end; the encrypted login information includes: user account and encrypted login password;

[0049] S2: responds to the post request sent by the front-end, and binds the user account and password to the data transmission model by parsing the body data stream and header data in the post request;

[0050] In step S2, the user account and password are bound to the data transmission model, specifically including:

[0051] Read the body data stream in the post request and convert it to string data in UTF-8 format; if the data stream is empty or the conversion fails, return the HTTP status code 400 error to the front end and prompt an invalid request.

[0052] Read the value of Content-Type in the header and determine whether the value of Content-Type is application / json. If so, use the Newtosoft.Json plug-in to deserialize the string data into a predefined data transmission model. If not, determine whether the value of Content-Type is application / x-www-form-urlencoded. If so, use the first preset symbol "&" as a delimiter to split the string data to obtain a split data set, traverse the data set, and use the second preset symbol "=" as a delimiter to split each data item in the data set, and assign the data obtained after segmentation to the data transmission model. If the value of Content-Type is empty, parse the string data according to application / json. If Content-Type is a value other than the above, return an http status code 400 error to the front desk and prompt an invalid request. In addition, if the string data fails to be parsed into (bound to) the data transmission model, return an http status code 500 error to the front desk and prompt a server exception.

[0053] Specifically, this embodiment is described in detail through the following example string data, but the present invention is not limited to the example string data:

[0054] The example string data is: Account=02397&Password=123456;

[0055] This embodiment first uses the first preset symbol "&" to split the example string data into a data set containing the first data item: "Account=02397" and the second data item "Password=123456", and then traverses the data set and uses the second preset symbol "=" as a delimiter to split the first data item into the attribute name "Account" and its corresponding attribute value "02397", and split the second data item into the attribute name "Password" and its corresponding attribute value "123456". Since the attribute value may contain Chinese, it is necessary to use WebUtility.UrlDecode for decoding, and finally assign the attribute value to the data transmission model according to the attribute name.

[0056] S3: Perform basic verification on the user account and user password in the data transmission model, and based on the user account that passes the basic verification, obtain its corresponding account details data model from the database (if the account details data model does not exist, directly return the front-end account or password error prompt), and perform secondary verification on the user account and user password in the data transmission model through the account details data model (specifically, compare the user password in the data transmission model with the password field in the account details data model. If the comparison is consistent, it means that the verification is passed. If it is inconsistent, it directly prompts the front-end account and password are wrong. If there are three consecutive errors, the user account will be locked for a preset period of time and cannot log in during this period), and proceed to the next step after the verification is passed; the account details data model contains the user's registered account, password, email address and personnel type; the personnel type is a first type enterprise employee or a second type enterprise employee;

[0057] In the S3 step, the basic verification is specifically as follows:

[0058] Determine whether the user account and user password in the data transmission model are empty. If either one is empty, a prompt indicating that the user account or user password is incorrect is returned to the front end. If both are not empty, a secondary verification is started.

[0059] S4: Determine whether the person type in the account details data model is a second-type enterprise employee. If so, perform email verification using SmtpClient and the Smtp email sending server based on the email address in the account details data model. If the verification is successful, log in to the data sharing system.

[0060] The S4 step specifically includes:

[0061] S41: Determine whether the person type in the account details data model is a second-type enterprise employee. If not, log in to the data sharing system. If so, obtain the email address from the account details data model. If the email address is empty, return directly to the front desk and prompt that the current logged-in user information is incomplete and ask to supplement and log in again. If it is not empty, proceed to the next step.

[0062] S42: Create an email sending object; the email sending object includes: email subject, email content and recipient email address; wherein the recipient email address is the email address in the account details data model corresponding to the logged-in user;

[0063] S43: Instantiate SmtpClient and connect to the Smtp mail sending server through the instantiated SmtpClient;

[0064] S44: Verify through the instantiated SmtpClient (specifically through the SmtpClient.Authenticate method) whether the client password preset in the SmtpClient is consistent with the server password preset in the Smtp mail sending server (this step is for the mail service provider to authenticate the identity to prevent someone from pretending to send mails directly). If not, return the http status code 500 error to the front desk and prompt the server abnormality. If so, deliver the mail sending object to the Smtp mail sending server through the instantiated SmtpClient (specifically by calling the SmtpClient.Send method to deliver), and determine whether the delivery is successful. If so, log in to the data sharing system.

[0065] The SMTP mail sending server described above has an untrusted server instance set up. It should be noted that emails sent from an untrusted server are marked as spam by default. Users can receive them but will not be notified. This is done to reduce user nuisance caused by email notifications. The key to setting up an untrusted server is to not configure the DKIM value.

[0066] In the step S44, the mail sending object is delivered to the untrusted server through the instantiated SmtpClient; the untrusted server is used to forward the mail sending object to the recipient mailbox in the mail sending object.

[0067] It should be noted here that when the recipient and the sender use the same mailbox service provider, then after the SmtpClient delivers the email sending object to the Smtp email sending server, the Smtp email sending server will make a judgment. If there is a mailbox in the Smtp email sending server that is consistent with the recipient's mailbox in the email sending object, it means that the delivery is successful. If the recipient and the sender are not from the same mailbox service provider, then the Smtp email sending server corresponding to the sender will verify with the Smtp email sending server corresponding to the recipient whether the recipient's mailbox exists. For example, using QQ mailbox to send an email to 163 mailbox. In addition, it should be noted that the Smtp email sending server includes the user's registered mailbox information (including mailbox address).

[0068] The present invention sets the company that maintains or develops the data sharing system as a first type of enterprise, and sets the company that uses the data sharing system as a second type of enterprise (i.e., a partner enterprise). During the login process, the user account and user password corresponding to the logged-in user are bound to a data transmission model by parsing the body data stream and the data in the header in the post request, and a basic verification is performed on the user account and user password in the data transmission model. Based on the user account that passes the basic verification, the corresponding account details data model is obtained from the database, and a secondary verification is performed based on the model. After the secondary verification passes, it is determined whether the person type in the account details data model is an employee of the second type of enterprise. If so, the email address in the account details data model is used to perform email verification using SmtpClient and the Smtp email sending server. If the verification passes, the user logs into the data sharing system. The present invention is based on the rule that the corresponding account and email address of an employee of a general enterprise will be disabled after leaving the company. When the logged-in user is an employee of the partner enterprise, the login is performed using email verification, which solves the problem in the prior art that data is easily leaked because the data sharing system cannot identify whether the partner login user has left the company.

[0069] Example 2

[0070] like Figure 2 As shown, the present invention also proposes a personnel information authentication system based on an email address, which is applied to a data sharing system used by a first type of enterprise and a second type of enterprise. The first type of enterprise is a company that maintains or develops the data sharing system, and the second type of enterprise is a company that uses the data sharing system. The system includes:

[0071] The front-end request sending module is used to obtain the login information input by the front-end, encrypt it, and send a post request containing the encrypted login information to the back-end; the encrypted login information includes: user account and encrypted login password;

[0072] The backend parsing module is used to respond to the post request sent by the frontend and bind the user account and password to the data transmission model by parsing the body data stream and the data in the header of the post request;

[0073] In the background analysis module, the user account and user password are bound to the data transmission model, specifically including:

[0074] Read the body data stream in the post request and convert it into a string data in UTF-8 format;

[0075] Read the value of Content-Type in the header and determine whether the value of Content-Type is application / json. If so, use the Newtosoft.Json plug-in to deserialize the string data into a predefined data transmission model. If not, determine whether the value of Content-Type is application / x-www-form-urlencoded. If so, split the string data with the first preset symbol as the delimiter to obtain the split data set, traverse the data set, and split each data item in the data set with the second preset symbol as the delimiter, and assign the split data to the data transmission model.

[0076] A background verification module is used to perform basic verification on the user account and user password in the data transmission model, and based on the user account that passes the basic verification, obtain its corresponding account details data model from the database, and perform a secondary verification on the user account and user password in the data transmission model using the account details data model; the account details data model includes the user's registered account, password, email address, and person type; the person type is a first-type enterprise employee or a second-type enterprise employee;

[0077] In the background verification module, the basic verification is specifically as follows:

[0078] Determine whether the user account and user password in the data transmission model are empty. If either one is empty, a prompt indicating that the user account or user password is incorrect is returned to the front end. If both are not empty, a secondary verification is started.

[0079] The email verification module is used to perform email verification using SmtpClient and the Smtp email sending server based on the email address in the account details data model when the secondary verification is passed and the person type in the account details data model is the second type of enterprise employee. If the verification is passed, the user can log in to the data sharing system.

[0080] The mailbox verification module specifically includes:

[0081] A personnel type determination unit, configured to determine whether the personnel type in the account details data model is a second-type enterprise employee;

[0082] An object creation unit, configured to create an email sending object when the person type in the account details data model is a second type enterprise employee; the email sending object includes: an email subject, email content, and a recipient email address; wherein the recipient email address is the email address in the account details data model corresponding to the logged-in user;

[0083] The instantiation unit is used to instantiate SmtpClient and connect to the Smtp mail sending server through the instantiated SmtpClient;

[0084] The mailbox verification unit is used to verify whether the client password preset in the SmtpClient is consistent with the server password pre-stored in the Smtp mail sending server through the instantiated SmtpClient, and when the verification is consistent, deliver the mail sending object to the Smtp mail sending server through the instantiated SmtpClient, determine whether the delivery is successful, and log in to the data sharing system after the delivery is successful.

[0085] An untrusted server instance is built in the Smtp mail sending server;

[0086] In the mailbox verification unit, the mail sending object is delivered to the untrusted server through the instantiated SmtpClient; the untrusted server is used to forward the mail sending object to the recipient mailbox in the mail sending object.

[0087] It should be noted that all directional indications in the embodiments of the present invention (such as up, down, left, right, front, back, etc.) are only used to explain the relative position relationship, movement status, etc. between the various components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.

[0088] In addition, in the present invention, descriptions such as "first," "second," and "one" are for descriptive purposes only and should not be understood to indicate or imply their relative importance or implicitly specify the number of the technical features indicated. Therefore, a feature specified as "first" or "second" may explicitly or implicitly include at least one of such features. In the description of the present invention, "plurality" means at least two, such as two, three, etc., unless otherwise specifically defined.

[0089] In the present invention, unless otherwise specified or limited, the terms "connection" and "fixation" should be understood in a broad sense. For example, "fixation" can mean fixed connection, detachable connection, or integration; mechanical connection or electrical connection; direct connection or indirect connection through an intermediate medium; internal communication between two elements or interaction between two elements, unless otherwise specified. Those skilled in the art will be able to understand the specific meanings of the above terms in the present invention based on specific circumstances.

[0090] In addition, the technical solutions between the various embodiments of the present invention can be combined with each other, but it must be based on the fact that ordinary technicians in this field can implement it. When the combination of technical solutions is mutually contradictory or cannot be implemented, it should be deemed that such a combination of technical solutions does not exist and is not within the scope of protection required by the present invention.

Claims

1. A personnel information authentication method based on email address, characterized in that: A method for a data sharing system used jointly by a first type of enterprise and a second type of enterprise, wherein the first type of enterprise is a company that maintains or develops the data sharing system and the second type of enterprise is a company that uses the data sharing system; the method comprises the steps of: S1: Obtain the login information input by the front-end, encrypt it, and send a post request containing the encrypted login information to the back-end; the encrypted login information includes: user account and encrypted login password; S2: Respond to the post request sent by the front end and bind the user account and user password to the data transmission model by parsing the body data stream and the data in the header of the post request. In the step S2, binding the user account and user password to the data transmission model specifically includes: reading the body data stream in the post request and converting it into a string data in UTF8 format; Read the value of Content-Type in the header and determine whether the value of Content-Type is application / json. If so, use the Newtosoft.Json plug-in to deserialize the string data into a predefined data transmission model. If not, determine whether the value of Content-Type is application / x-www-form-urlencoded. If so, split the string data using the first preset symbol as a delimiter to obtain a split data set, traverse the data set, and split each data item in the data set using the second preset symbol as a delimiter, and assign the split data to the data transmission model; S3: Perform a basic verification on the user account and user password in the data transmission model. Based on the user account that passes the basic verification, obtain its corresponding account details data model from the database. Perform a secondary verification on the user account and user password in the data transmission model using the account details data model. After the verification passes, proceed to the next step. The account details data model includes the user's registered account, password, email address, and person type. The person type is either a first-type enterprise employee or a second-type enterprise employee. S4: Determine whether the person type in the account details data model is a second-type enterprise employee. If so, perform email verification using SmtpClient and the Smtp email sending server based on the email address in the account details data model. If the verification is successful, log in to the data sharing system. The S4 step specifically includes: S41: Determine whether the person type in the account details data model is a second-type enterprise employee. If not, log in to the data sharing system. If so, proceed to the next step. S42: Create an email sending object; the email sending object includes: email subject, email content and recipient email address; wherein the recipient email address is the email address in the account details data model corresponding to the logged-in user; S43: Instantiate SmtpClient and connect to the Smtp mail sending server through the instantiated SmtpClient; S44: Verify through the instantiated SmtpClient whether the client password preset in the SmtpClient is consistent with the server password pre-stored in the Smtp mail sending server. If so, deliver the mail sending object to the Smtp mail sending server through the instantiated SmtpClient and determine whether the delivery is successful. If so, log in to the data sharing system.

2. A personnel information authentication method based on email address according to claim 1, characterized in that: An untrusted server instance is built in the Smtp mail sending server; In the step S44, the mail sending object is delivered to the untrusted server through the instantiated SmtpClient; the untrusted server is used to forward the mail sending object to the recipient mailbox in the mail sending object.

3. A personnel information authentication method based on email address according to claim 1, characterized in that: In the S3 step, the basic verification is specifically as follows: Determine whether the user account and user password in the data transmission model are empty. If either one is empty, a prompt indicating that the user account or user password is incorrect is returned to the front end. If both are not empty, a secondary verification is started.

4. A personnel information authentication system based on email address, characterized in that: A data sharing system for use by first-type enterprises and second-type enterprises, wherein the first-type enterprises are companies that maintain or develop the data sharing system and the second-type enterprises are companies that use the data sharing system; the system comprises: The front-end request sending module is used to obtain the login information input by the front-end, encrypt it, and send a post request containing the encrypted login information to the back-end; the encrypted login information includes: user account and encrypted login password; The backend parsing module is used to respond to the post request sent by the frontend and bind the user account and password to the data transmission model by parsing the body data stream and the data in the header of the post request; In the background analysis module, the user account and user password are bound to the data transmission model, specifically including: Read the body data stream in the post request and convert it into a string data in UTF-8 format; Read the value of Content-Type in the header and determine whether the value of Content-Type is application / json. If so, use the Newtosoft.Json plug-in to deserialize the string data into a predefined data transmission model. If not, determine whether the value of Content-Type is application / x-www-form-urlencoded. If so, split the string data using the first preset symbol as a delimiter to obtain a split data set, traverse the data set, and split each data item in the data set using the second preset symbol as a delimiter, and assign the split data to the data transmission model; A background verification module is used to perform basic verification on the user account and user password in the data transmission model, and based on the user account that passes the basic verification, obtain its corresponding account details data model from the database, and perform a secondary verification on the user account and user password in the data transmission model using the account details data model; the account details data model includes the user's registered account, password, email address, and person type; the person type is a first-type enterprise employee or a second-type enterprise employee; The email verification module is used to use SmtpClient and the Smtp email sending server to perform email verification based on the email address in the account details data model when the secondary verification passes and the person type in the account details data model is the second type of enterprise employee. If the verification passes, the user can log in to the data sharing system; The mailbox verification module specifically includes: A personnel type determination unit, configured to determine whether the personnel type in the account details data model is a second-type enterprise employee; An object creation unit, configured to create an email sending object when the person type in the account details data model is a second type enterprise employee; the email sending object includes: an email subject, email content, and a recipient email address; wherein the recipient email address is the email address in the account details data model corresponding to the logged-in user; The instantiation unit is used to instantiate SmtpClient and connect to the Smtp mail sending server through the instantiated SmtpClient; The mailbox verification unit is used to verify whether the client password preset in the SmtpClient is consistent with the server password pre-stored in the Smtp mail sending server through the instantiated SmtpClient, and when the verification is consistent, deliver the mail sending object to the Smtp mail sending server through the instantiated SmtpClient, determine whether the delivery is successful, and log in to the data sharing system after the delivery is successful.

5. The personnel information authentication system based on email address according to claim 4, characterized in that: An untrusted server instance is built in the Smtp mail sending server; In the mailbox verification unit, the mail sending object is delivered to the untrusted server through the instantiated SmtpClient; the untrusted server is used to forward the mail sending object to the recipient mailbox in the mail sending object.

6. The personnel information authentication system based on email address according to claim 4, characterized in that: In the background verification module, the basic verification is specifically as follows: Determine whether the user account and user password in the data transmission model are empty. If either one is empty, a prompt indicating that the user account or user password is incorrect is returned to the front end. If both are not empty, a secondary verification is started.

Images