Logistics platform login security configuration verification method, apparatus and device, and storage medium

By querying the whitelist and account database split and combine passwords in the logistics platform for verification, and generating an abnormal login report to upload it to the blockchain, the problems of poor flexibility and security risks in the traditional login verification method are solved, and differentiated calibration is achieved Checksum efficient login.

CN119094229APending Publication Date: 2024-12-06上海乾臻信息科技有限公司
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411327178.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-09-23
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

Under the rapid growth of business demand, the traditional login verification method is poor, making it difficult to cope with the login efficiency needs of high-authorized institutions. At the same time, unconfigured login restrictions on low-authorized institutions will introduce data security risks, resulting in data leakage and unauthorized. Risk of access.

Method used

By querying the preset whitelist database and account database, splitting and combining passwords to obtain the login password and verification code, performing differentiated verification, generating abnormal login reports and uploading them to the blockchain, and configuring different login verification strategies to improve security Sex and efficiency.

Benefits of technology

Differentiated login verification for different institutions and personnel is achieved, system security and login efficiency are improved, unauthorized access and data leakage are prevented, and user experience is optimized.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119094229A_ABST
    Figure CN119094229A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of information processing, in particular to a logistics platform login security configuration verification method, device and equipment and a storage medium. Whether white list information having a mapping relation with an identity label exists in a preset white list database or not is inquired; splitting the combined password to obtain a login password and a verification code, verifying the consistency of the account name and the login password according to the account database to obtain a first verification result, and verifying the consistency of the verification code and the mobile phone number according to the verification code sending record to obtain a second verification result; and if one of the first verification result and the second verification result is not passed, abnormal login information is generated, and different login verification strategies are configured for different institutions or personnel, so that differential verification is realized, the login efficiency is improved, the system security is improved, unauthorized access and data leakage are prevented, and the user experience is optimized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of information processing technology, and in particular to a logistics platform login security configuration verification method, device, equipment and storage medium. Background Art

[0002] At present, the importance of logistics platforms as a key link between merchants and consumers is becoming increasingly prominent. However, the rapid growth of this field is also accompanied by unprecedented security challenges. With the surge in transaction volume and the continuous expansion of data traffic, logistics platforms must not only handle massive amounts of order information and inventory data, but also ensure the security of this information during transmission and storage to prevent security incidents such as data leakage, illegal access or tampering. Traditionally, the same verification method is configured for logins of different institutions. This method is not only inflexible, but also reduces login efficiency for institutions or personnel with higher authority, making it difficult to cope with rapidly growing business needs. For institutions or personnel with lower authority, not configuring login restriction verification will introduce data security risks. Summary of the invention

[0003] In order to overcome the shortcomings of the prior art, the purpose of the present invention is to provide a logistics platform login security configuration verification method, device, equipment and storage medium that configures different login verification strategies for different institutions or personnel to achieve differentiated verification, improve login efficiency while improving system security, prevent unauthorized access and data leakage, and optimize the user experience.

[0004] A first aspect of the present invention provides a logistics platform login security configuration verification method, including: receiving a login request instruction sent by a client, parsing the login request instruction to obtain parsing information, the parsing information including an identity identifier, a mobile phone number, an account name and a combination password; querying a preset whitelist database to determine whether there is whitelist information having a mapping relationship with the identity identifier, and when the whitelist information does not exist, splitting the combination password to obtain a login password and a verification code; verifying the consistency of the account name and the login password according to an account database to obtain a first verification result, and verifying the consistency of the verification code and the mobile phone number according to a verification code sending record to obtain a second verification result; if one of the first verification result and the second verification result is a failure, generating abnormal login information, and sending the abnormal login information to the client; generating an abnormal login report according to the abnormal login information, and uploading the abnormal login report to a blockchain.

[0005] Optionally, in a first implementation method of the first aspect of the present invention, the receiving login request instruction sent by the client, parsing the login request instruction to obtain parsing information, the parsing information including an identity identifier, a mobile phone number, an account name and a combination password, includes: creating an access listener, and using the access listener to monitor the client's access to the login page; when the client is monitored to access the login page, generating a verification code and returning it to the client for the client to configure a combination password; saving the verification code in a verification code sending record; receiving the login request instruction sent by the client that is encrypted with a public key, and decrypting the login request instruction using a private key to obtain decrypted information; parsing the decrypted information to obtain parsing information, the parsing information including an identity identifier, a mobile phone number, an account name and the combination password.

[0006] Optionally, in a second implementation method of the first aspect of the present invention, the query whether there is whitelist information having a mapping relationship with the identity identifier in the preset whitelist database, and when the whitelist information does not exist, splitting the combined password to obtain a login password and a verification code, including: identifying the ID identifier of each login outlet, and grading the login outlets to obtain outlet grading information; configuring first login restriction cancellation information according to the ID identifier and the outlet grading information; constructing a whitelist database according to the first login restriction cancellation information; querying whether there is the ID identifier having a mapping relationship with the identity identifier in the preset whitelist database; when the ID identifier does not exist, splitting the combined password to obtain a login password and a verification code.

[0007] Optionally, in a third implementation method of the first aspect of the present invention, the consistency of the account name and the login password is verified according to the account database to obtain a first verification result, and the consistency of the verification code and the mobile phone number is verified according to the verification code sending record to obtain a second verification result, including: calling a preset account database; verifying the consistency of the account name and the login password according to the account database to obtain a first verification result; obtaining the verification code sending record; verifying the consistency of the verification code and the mobile phone number according to the verification code sending record to obtain a second verification result.

[0008] Optionally, in a fourth implementation method of the first aspect of the present invention, if one of the first verification result and the second verification result is failed, abnormal login information is generated and the abnormal login information is sent to the client, including: if the first verification result and the second verification result are both passed, the client is allowed to log in; if one of the first verification result and the second verification result is failed, abnormal login information is generated; the abnormal login information is sent to the client, so that the client generates and displays an abnormal login page based on the abnormal login information.

[0009] Optionally, in a fifth implementation manner of the first aspect of the present invention, generating an abnormal login report based on the abnormal login information and uploading the abnormal login report to the blockchain includes: extracting a report template and identifying a fill area in the report template; filling the abnormal login information into the fill area of ​​the report template to generate an abnormal login report, and recording a report generation time; merging the report generation time and the abnormal login report to obtain merged information; and uploading the merged information to the blockchain.

[0010] Optionally, in a sixth implementation method of the first aspect of the present invention, after generating an abnormal login report based on the abnormal login information and uploading the abnormal login report to the blockchain, it also includes: obtaining a new whitelist list; configuring second login restriction cancellation information based on the new whitelist list; and updating the whitelist database based on the second login restriction cancellation information.

[0011] The second aspect of the present invention provides a logistics platform login security configuration verification device, including: a receiving and parsing module, used to receive a login request instruction sent by a client, parse the login request instruction, and obtain parsing information, wherein the parsing information includes an identity identifier, a mobile phone number, an account name, and a combined password; a query and splitting module, used to query whether there is whitelist information with a mapping relationship with the identity identifier in a preset whitelist database, and when the whitelist information does not exist, split the combined password to obtain a login password and a verification code; a verification module, used to verify the consistency of the account name and the login password according to the account database to obtain a first verification result, and verify the consistency of the verification code and the mobile phone number according to the verification code sending record to obtain a second verification result; a generation and sending module, used to generate abnormal login information if one of the first verification result and the second verification result is not passed, and send the abnormal login information to the client; a generation and upload module, used to generate an abnormal login report according to the abnormal login information, and upload the abnormal login report to the blockchain.

[0012] Optionally, in a first implementation method of the second aspect of the present invention, the receiving and parsing module includes: creating a monitoring unit, used to create an access listener, and using the access listener to monitor the client's access to the login page; generating a return unit, used to generate a verification code and return it to the client when monitoring the client's access to the login page, so that the client can configure a combination password; a saving unit, used to save the verification code in a verification code sending record; a receiving and decryption unit, used to receive a login request instruction sent by the client that is encrypted with a public key, and use a private key to decrypt the login request instruction to obtain decrypted information; and a parsing unit, used to parse the decrypted information to obtain parsed information, wherein the parsed information includes an identity identifier, a mobile phone number, an account name, and the combination password.

[0013] Optionally, in a second implementation method of the second aspect of the present invention, the query splitting module includes: an identification and grading unit, used to identify the ID identification of each login outlet, and grade the login outlets to obtain outlet grading information; a configuration unit, used to configure the first login restriction cancellation information according to the ID identification and the outlet grading information; a construction unit, used to construct a whitelist database according to the first login restriction cancellation information; a query unit, used to query whether there is an ID identification having a mapping relationship with the identity identification in the preset whitelist database; a splitting unit, used to split the combined password to obtain a login password and a verification code when the ID identification does not exist.

[0014] Optionally, in a third implementation method of the second aspect of the present invention, the verification module includes: a calling unit, used to call a preset account database; a first verification unit, used to verify the consistency of the account name and the login password according to the account database, and obtain a first verification result; an acquisition unit, used to obtain a verification code sending record; a second verification unit, used to verify the consistency of the verification code and the mobile phone number according to the verification code sending record, and obtain a second verification result.

[0015] Optionally, in a fourth implementation method of the second aspect of the present invention, the generation and sending module includes: an allowing unit, used to allow the client to log in if both the first verification result and the second verification result are passed; a generating unit, used to generate abnormal login information if one of the first verification result and the second verification result is failed; and a sending unit, used to send the abnormal login information to the client, so that the client generates and displays an abnormal login page based on the abnormal login information.

[0016] Optionally, in a fifth implementation of the second aspect of the present invention, the generation and upload module includes: an extraction and identification unit, used to extract the report template and identify the fill area in the report template; a filling and recording unit, used to fill the abnormal login information into the fill area of ​​the report template to generate an abnormal login report, and record the report generation time; a merging unit, used to merge the report generation time and the abnormal login report to obtain merged information; and an uploading unit, used to upload the merged information to the blockchain.

[0017] Optionally, in the sixth implementation method of the second aspect of the present invention, it also includes: an acquisition module for acquiring a new list of whitelists; a configuration module for configuring second login restriction cancellation information according to the new list of whitelists; and an update module for updating the whitelist database based on the second login restriction cancellation information.

[0018] The third aspect of the present invention provides a logistics platform login security configuration verification device, which includes: a memory and at least one processor, wherein instructions are stored in the memory; at least one of the processors calls the instructions in the memory to enable the logistics platform login security configuration verification device to perform each step of the logistics platform login security configuration verification method described in any one of the above items.

[0019] A fourth aspect of the present invention provides a computer-readable storage medium having instructions stored thereon, and when the instructions are executed by a processor, the various steps of any of the above-mentioned methods for verifying the security configuration of a logistics platform login are implemented.

[0020] In the technical solution of the present invention, by querying whether there is whitelist information with a mapping relationship with the identity identifier in a preset whitelist database, when the whitelist information does not exist, the combined password is split to obtain the login password and the verification code, and the consistency of the account name and the login password is verified according to the account database to obtain a first verification result, and the consistency of the verification code and the mobile phone number is verified according to the verification code sending record to obtain a second verification result. If one of the first verification result and the second verification result fails, abnormal login information is generated, and different login verification strategies are configured for different institutions or personnel to achieve differentiated verification, thereby improving login efficiency while improving system security, preventing unauthorized access and data leakage, and optimizing user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 A first flow chart of a logistics platform login security configuration verification method provided by an embodiment of the present invention;

[0022] Figure 2A second flow chart of the logistics platform login security configuration verification method provided by an embodiment of the present invention;

[0023] Figure 3 A third flow chart of the logistics platform login security configuration verification method provided by an embodiment of the present invention;

[0024] Figure 4 A fourth flow chart of the logistics platform login security configuration verification method provided by an embodiment of the present invention;

[0025] Figure 5 A schematic diagram of a structure of a logistics platform login security configuration verification device provided by an embodiment of the present invention;

[0026] Figure 6 Another structural schematic diagram of the logistics platform login security configuration verification device provided by an embodiment of the present invention;

[0027] Figure 7 A schematic diagram of the structure of a logistics platform login security configuration verification device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0028] The present invention provides a logistics platform login security configuration verification method, device, equipment and storage medium, which configure different login verification strategies for different institutions or personnel to achieve differentiated verification, improve login efficiency while improving system security, prevent unauthorized access and data leakage, and optimize user experience.

[0029] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" or "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0030] For ease of understanding, the specific process of the embodiment of the present invention is described below. Figure 1 , an embodiment of the logistics platform login security configuration verification method in an embodiment of the present invention includes:

[0031] 101. Receive a login request instruction sent by a client, parse the login request instruction, and obtain parsed information, where the parsed information includes an identity identifier, a mobile phone number, an account name, and a combination password;

[0032] In this embodiment, a listener is set up on the server side to wait for the request sent by the client, decrypt the client's request with a private key, parse the decrypted data, and extract the identity identifier, mobile phone number, account name and combined password. The identity identifier is an ID that uniquely identifies the client or user. The mobile phone number is the user's mobile phone number, which is used for secondary verification and security notification. The account name is the user's account name, which is used to match the information in the account database. The combined password includes a login password and a verification code.

[0033] 102. Check whether there is whitelist information with a mapping relationship with the identity identifier in a preset whitelist database. When the whitelist information does not exist, split the combined password to obtain a login password and a verification code;

[0034] In this embodiment, the identity identifier is used as a query condition, and a query request is issued to the whitelist database. The query result is used to determine whether the identity identifier exists in the whitelist. If it exists, the corresponding authorization operation is performed. If it does not exist, the next step is continued, and the combination password is split based on the structure of the combination password to extract the login password and the verification code. The login password is the main password entered by the user and is used to verify the user's identity. The verification code is a temporary, secure code used to further verify the user's identity or prevent automated attacks.

[0035] 103. Verify the consistency of the account name and the login password according to the account database to obtain a first verification result, and verify the consistency of the verification code and the mobile phone number according to the verification code sending record to obtain a second verification result;

[0036] In this embodiment, an account database is queried to obtain a record matching the account name. The account database includes the account name, password, and other user information. The account name is used as a query condition to issue a query request to the database to retrieve the corresponding record. The login password provided by the user is compared with the password stored in the account database. The password provided by the user is hashed in the same way and compared with the password hash stored in the database. If the two are consistent, it means that the password is correct, otherwise the password is incorrect. If the account name exists and the password matches, the first verification result is "successful". If the account name does not exist or the password does not match, the first verification result is "failed". The verification code sending record database records the verification code sent each time and its associated mobile phone number, sending time and other information. The mobile phone number is used as a query condition to retrieve the verification code sending record to obtain the corresponding verification code and its validity information. The verification code provided by the user is compared with the verification code retrieved from the verification code sending record to check whether the verification code provided by the user is consistent with the verification code in the record, and verify whether the verification code is within the validity period. If the verification code matches and is within the validity period, the second verification result is "successful". If the verification code does not match or has expired, the second verification result is "failed".

[0037] 104. If one of the first verification result and the second verification result is failed, abnormal login information is generated and sent to the client;

[0038] In this embodiment, it is checked whether the first verification result and the second verification result are both "successful". If any one of them is "failed", it is necessary to generate abnormal login information, which includes the failed verification step, error type, timestamp, user account name, etc. The abnormal login information is a structured data object or message, which contains a specific error description and related information. The generated abnormal information is sent to the client application or user interface to provide instant feedback, and a friendly error message is displayed on the login page or application to inform the user of the problem and guide the user to take appropriate action.

[0039] 105. Generate an abnormal login report based on the abnormal login information, and upload the abnormal login report to the blockchain;

[0040] In this embodiment, an abnormal login report is generated based on the abnormal login information, the abnormal login report includes detailed information of the abnormal event, such as timestamp, account name, failed verification steps and error type, a blockchain platform suitable for storing and verifying data is selected, the data of the abnormal login report is converted into a format suitable for blockchain storage, a smart contract is written to automate the storage and retrieval process of the report, and the hash value or summary of the report is uploaded to the blockchain network.

[0041] In an embodiment of the present invention, by querying whether there is whitelist information with a mapping relationship with the identity identifier in a preset whitelist database, when the whitelist information does not exist, the combined password is split to obtain a login password and a verification code, and the consistency of the account name and the login password is verified according to the account database to obtain a first verification result, and the consistency of the verification code and the mobile phone number is verified according to the verification code sending record to obtain a second verification result. If one of the first verification result and the second verification result fails, abnormal login information is generated, and different login verification strategies are configured for different institutions or personnel to implement differentiated verification, thereby improving login efficiency while improving system security, preventing unauthorized access and data leakage, and optimizing user experience.

[0042] See also Figure 2 The second embodiment of the logistics platform login security configuration verification method in the embodiment of the present invention includes:

[0043] 201. Create an access listener and use the access listener to monitor the client access to the login page;

[0044] In this embodiment, the port, protocol (such as HTTP / HTTPS) and other necessary parameters of the access listener are configured to ensure that the access listener can correctly receive and process client requests, initialize the listener, set up appropriate logging and error handling mechanisms to facilitate debugging and maintenance, and the access listener captures and processes all requests that arrive at the login page, processes the captured requests, and extracts necessary data, such as request time, client IP, request parameters, etc.

[0045] 202. When monitoring the client accessing the login page, generate a verification code and return it to the client so that the client can configure a combination password;

[0046] In this embodiment, a verification code type is selected, such as a graphic verification code, a text message verification code, or an email verification code. When a client is monitored accessing the login page, a strong random number generator is used to create a verification code to ensure its security and uniqueness. The validity period of the verification code is set to ensure that it is used within a reasonable time and to prevent abuse. The verification code is embedded in the HTTP response to ensure that the client can receive it correctly. The verification code is encrypted during transmission to prevent it from being intercepted or tampered with. The client needs to receive and display the verification code, and provide an interface for the user to enter the verification code.

[0047] 203. Save the verification code to the verification code sending record;

[0048] In this embodiment, the data structure of the verification code record is determined, including the verification code ID field, the verification code value field, the sending time field, the user information field, the request source field, the validity period field and the usage status field, and a suitable data storage solution is selected, such as a database (SQL or NoSQL), a cache system, etc. After the verification code is generated, the verification code information is inserted into the selected data storage, and a cache mechanism is used to reduce the database burden. Sensitive data, such as the verification code value, is encrypted during the storage process to prevent data leakage. Expired or used verification code records are cleaned up regularly to keep the database clean and performant, and operation logs of verification code generation and storage are recorded for subsequent auditing and troubleshooting.

[0049] 204. Receive the login request instruction sent by the client after being encrypted with the public key, and use the private key to decrypt the login request instruction to obtain decrypted information;

[0050] In this embodiment, the server sets up an interface to receive the encrypted login request sent by the client. Before processing the request, the request is first subjected to basic verification, such as the legitimacy and integrity of the request, to ensure that the request comes from the expected client and that the data has not been tampered with, to ensure that the received data format meets expectations, such as the format of the encrypted data contained in the request body, to extract the encrypted login request instruction data from the request, to ensure that the private key is stored securely, that only authorized system components can access the private key, and to use the private key to decrypt the extracted encrypted data.

[0051] 205. Parse the decrypted information to obtain parsed information, where the parsed information includes the identity identifier, mobile phone number, account name, and combination password;

[0052] In this embodiment, the decrypted data is in a structured format. The specific information of the login request is extracted from the decrypted data, the specific information is loaded into the parsing tool, the data is parsed using the functions or methods provided by the tool to obtain parsed information, and key information (identity identification, mobile phone number, account name and combined password) is extracted from the parsed information.

[0053] 206. Identify the ID of each login outlet, and classify the login outlets to obtain outlet classification information;

[0054] In this embodiment, the ID identification of each login outlet is identified, and the standards for grading the outlets are determined. For example, the outlets may be graded based on their scale, function, geographical location and other attributes, and specific grading rules may be formulated. For example, the prefix or suffix of the ID identification may indicate different levels, or other attributes of the outlet (such as visit frequency, importance, etc.) may be used to determine the level. According to the formulated rules, the ID of each login outlet is graded, and the level information of each outlet is recorded and associated with the ID.

[0055] 207. Configure first login restriction cancellation information according to the ID identification and the network point classification information;

[0056] In this embodiment, the ID identification of each login outlet and its corresponding classification information are obtained from the previous steps, and it is determined which levels of outlets can cancel the restrictions. For example, it is stipulated that only outlets with higher levels can cancel the restrictions. It is determined whether the ID identification contains information related to the first login restriction, such as a specific prefix or suffix. According to the classification information and ID identification of the outlet, the cancellation information of the first login restriction is configured, and the conditions for canceling the restriction are formulated according to the classification rules. For example, level 1 outlets can cancel the restrictions, while level 2 and level 3 outlets cannot cancel them. The system configuration is updated for the outlets that meet the conditions, and the first login restriction is canceled.

[0057] 208. Building a whitelist database according to the first login restriction cancellation information;

[0058] In this embodiment, ensure that you have the ID identification and classification information of all outlets that need to cancel the first login restriction, clean and format the outlet data, ensure the consistency of the ID identification and classification information, select a suitable database system, such as a relational database (MySQL, PostgreSQL) or a non-relational database (MongoDB), create a whitelist table to store the information of the outlets that need to cancel the first login restriction, use the database import tool to import the data into the whitelist table, regularly review the whitelist content, and update the cancellation status of the outlets.

[0059] 209. Check whether there is an ID identifier having a mapping relationship with the identity identifier in the preset whitelist database;

[0060] In this embodiment, the identity to be queried (such as user ID, branch ID, etc.) is clearly defined, the mapping rules between the identity and the ID are defined, the relevant tables in the whitelist database are determined, the query is performed based on the identity, and the database connection library in the database management tool or programming language is used to execute the SQL query, and check whether there is an ID corresponding to the identity in the query result. If the result is empty, it means that the ID does not exist in the whitelist.

[0061] 210. When the ID does not exist, the combined password is split to obtain the login password and verification code;

[0062] In this embodiment, it is checked whether there is an ID identifier corresponding to the identity identifier in the query result. If the result is empty, it means that the ID identifier does not exist in the whitelist. The format or rules of the combined password are determined, for example, whether the "login password" and "verification code" are combined strings, or whether there are specific separators. If the combined password contains a separator, the string is split using the separator. If the combined password does not have a clear separator but has a fixed length, it can be split according to the fixed length. For example, the first 8 characters are the login password and the last 4 characters are the verification code. Ensure that the split login password and verification code meet the expected format requirements, for example, whether the login password meets the complexity requirements and whether the verification code is a valid combination of numbers or letters.

[0063] In the embodiment of the present invention, by using verification codes and encryption and decryption mechanisms, the security protection of the system is improved to prevent unauthorized access and data leakage. The application of verification codes effectively blocks automated attacks and brute force cracking attempts. By parsing login requests, branch classification and whitelist verification, it is ensured that only legitimate users can access the system. Branch classification and login restriction configuration allow the system to flexibly adjust access rights according to different risk levels. Public key encryption and private key decryption ensure the security and confidentiality of data transmission. By splitting and combining passwords to handle abnormal situations, the validity of the login request is further verified.

[0064] See also Figure 3 The third embodiment of the logistics platform login security configuration verification method in the embodiment of the present invention includes:

[0065] 301. Calling a preset account database;

[0066] In this embodiment, the connection information of the account database is ensured to be known, and a connection is established with the database according to the connection information.

[0067] 302. Verify the consistency of the account name and the login password according to the account database to obtain a first verification result;

[0068] In this embodiment, the account name input by the user is used to query the account database, the corresponding account record is retrieved, the stored password information is obtained from the account record retrieved from the database, and the login password is compared with the password in the database. If the account name and password match, it means that the consistency of the account name and login password has passed the verification. If the account name exists but the password does not match, it means that the consistency of the account name and login password has not passed the verification.

[0069] 303. Obtain verification code sending record;

[0070] In this embodiment, a database table storing verification code sending records is identified, key fields in the table are understood, query conditions are determined to retrieve relevant verification code records based on user account names or other identification information, and the verification code sending records are retrieved from the database using an SQL query method.

[0071] 304. Verify the consistency between the verification code and the mobile phone number according to the verification code sending record to obtain a second verification result;

[0072] In this embodiment, the verification code record related to the current request is obtained from the verification code sending record to ensure that it includes information such as the mobile phone number, verification code value, sending time, and expiration time. It is checked whether the mobile phone number in the verification code sending record is consistent with the mobile phone number provided by the user. The verification code provided by the user is compared with the verification code in the record. If the verification code and the mobile phone number are consistent, the verification is successful. If the verification code or the mobile phone number are inconsistent, or the verification code has expired, the verification fails.

[0073] 305. If both the first verification result and the second verification result are passed, the client is allowed to log in;

[0074] In this embodiment, it is checked whether the first verification result and the second verification result are both passed. If both are passed, it means that the consistency of the account name and the login password has passed the verification, and the consistency of the verification code and the mobile phone number has been successfully verified, and the verification code itself is also valid. The client is allowed to log in, a user session or token is created to maintain the login status, the user's login status is updated to "logged in", and relevant information is recorded, and a message of successful login is fed back to the client.

[0075] 306. If one of the first verification result and the second verification result fails, abnormal login information is generated;

[0076] In this embodiment, it is checked whether one of the first verification result and the second verification result is failed. If any one of the results fails, it means that there is an abnormality in the login request, and abnormal login information is created, such as an invalid verification code, an expired verification code, a mismatch in mobile phone number, etc.

[0077] 307. Send the abnormal login information to the client, so that the client generates and displays an abnormal login page based on the abnormal login information;

[0078] In this embodiment, the abnormal login information is constructed into a data format suitable for client processing, and the abnormal information is sent to the client through the communication protocol between the server and the client (such as HTTP). The client receives the abnormal login information from the server, parses the data in the abnormal information to extract the error type and description, and designs and displays the abnormal login page based on the received abnormal information, with clear error messages and reasons to help users understand the reason for the login failure.

[0079] In the embodiment of the present invention, the verification of the account name and password is combined with the verification of the verification code, so the security of the login is enhanced and the risk of unauthorized access is reduced. By generating and sending abnormal login information, the client is notified of potential security issues in a timely manner, and the user experience and system responsiveness are improved. The independence of each verification step ensures the accuracy of the system, reduces the possibility of erroneous login, and effectively prevents various attack methods. The display of the abnormal login page provides users with clear error feedback, helping users better understand and solve login problems.

[0080] See also Figure 4 The fourth embodiment of the logistics platform login security configuration verification method in the embodiment of the present invention includes:

[0081] 401. Extracting a report template and identifying a fill area in the report template;

[0082] In this embodiment, a report template is obtained from a storage system, the template file is loaded into a processing system, and the template file is parsed according to the format of the template file to extract text, tables, images and other contents in the template, understand the overall structure and layout of the template, find predefined placeholders or fill areas in the template, analyze the context of each placeholder, identify its field type and purpose, mark all identified fill areas in the template for subsequent processing, and record detailed information for each fill area, including location, field type and expected data format, for subsequent data filling and report generation.

[0083] 402. Fill the abnormal login information into the filling area of ​​the report template to generate an abnormal login report, and record the report generation time;

[0084] In this embodiment, the data to be filled in, such as error type, description, timestamp, etc., is extracted from the previously generated abnormal login information. According to the fill-in area marked in the report template, the extracted data is mapped to the corresponding placeholder, and the extracted data is filled into the fill-in area marked in the template to generate an abnormal login report. The current timestamp of the system is obtained to record the time when the report was generated.

[0085] 403. Merge the report generation time and the abnormal login report to obtain merged information;

[0086] In this embodiment, a suitable location is reserved for the generation time in the template, such as the cover page, title page or footer, and the report generation time is inserted into the cover page, title page or footer of the abnormal login report to obtain merged information.

[0087] 404. Upload the merged information to the blockchain;

[0088] In this embodiment, a suitable blockchain platform (such as Ethereum, Hyperledger Fabric, Polygon, etc.) is selected, a public blockchain such as Ethereum is used, a smart contract is written or selected for storing data, the written smart contract is deployed to the blockchain network, the merged information is encoded into a format suitable for blockchain storage, the API or tool provided by the blockchain platform is used to call the smart contract, the encoded data is submitted to the blockchain, the blockchain network is waited for to confirm the transaction, and it is ensured that the merged information has been successfully written to the blockchain, and the unique identifier (transaction ID) of the blockchain transaction is recorded for subsequent tracking and verification.

[0089] 405. Get the new whitelist list;

[0090] In this embodiment, new entries that need to be added to the whitelist are determined, the format of the new entries is ensured to be consistent with that of the existing whitelist, and a new whitelist list is generated according to the new entries.

[0091] 406. Configure the second login restriction cancellation information according to the newly added list in the whitelist;

[0092] In this embodiment, the latest entry is extracted from the newly added whitelist list, including information such as user ID and IP address, and the whitelist rule is set or updated in the system to cancel the second login restriction. For example, the corresponding record is updated in the user table or permission table, and the restriction status of the whitelist user is set to "cancel". If the system uses a configuration file to manage login restrictions, the configuration file is updated to include the whitelist entry.

[0093] 407. Update the whitelist database based on the second login restriction cancellation information;

[0094] In this embodiment, an SQL statement is constructed based on the data that needs to be updated, and the constructed SQL statement is executed in a database management tool or application to apply the updated configuration to the system, query the updated entry in the database, confirm that the restriction status has been correctly changed, verify the functionality in the system, and ensure that the canceled restrictions are no longer applied to these users.

[0095] In the embodiment of the present invention, by extracting and filling in report templates, and generating and recording abnormal login reports, the standardization and automation of the exception handling process are ensured, and uploading the merged information to the blockchain ensures the integrity and non-tamperability of the report, thereby improving the security and reliability of the data. The acquisition and application of new whitelist lists allow the system to flexibly adjust login restrictions according to the latest security requirements, thereby improving the adaptability and protection capabilities of the system, and by updating the whitelist database, the flexibility of the configuration is improved.

[0096] The above describes the method for verifying the security configuration of the logistics platform login in the embodiment of the present invention. The following describes the device for verifying the security configuration of the logistics platform login in the embodiment of the present invention. Figure 5 In one embodiment of the present invention, a device for verifying the security configuration of a logistics platform login includes:

[0097] The receiving and parsing module 501 is used to receive the login request instruction sent by the client, parse the login request instruction, and obtain parsing information, which includes the identity identifier, mobile phone number, account name and password combination;

[0098] The query splitting module 502 is used to query whether there is whitelist information with a mapping relationship with the identity identifier in a preset whitelist database. When the whitelist information does not exist, the combined password is split to obtain a login password and a verification code;

[0099] Verification module 503, used to verify the consistency of the account name and the login password according to the account database to obtain a first verification result, and verify the consistency of the verification code and the mobile phone number according to the verification code sending record to obtain a second verification result;

[0100] A generating and sending module 504 is used to generate abnormal login information if one of the first verification result and the second verification result fails, and send the abnormal login information to the client;

[0101] The generation upload module 505 is used to generate an abnormal login report according to the abnormal login information and upload the abnormal login report to the blockchain.

[0102] In this embodiment, by querying whether there is whitelist information with a mapping relationship with the identity identifier in the preset whitelist database, when the whitelist information does not exist, the combined password is split to obtain the login password and the verification code, and the consistency of the account name and the login password is verified according to the account database to obtain a first verification result, and the consistency of the verification code and the mobile phone number is verified according to the verification code sending record to obtain a second verification result. If one of the first verification result and the second verification result fails, abnormal login information is generated, and different login verification strategies are configured for different institutions or personnel to achieve differentiated verification, thereby improving login efficiency while improving system security, preventing unauthorized access and data leakage, and optimizing user experience.

[0103] See also Figure 6 Another embodiment of the logistics platform login security configuration verification device in the embodiment of the present invention includes:

[0104] The receiving and parsing module 501 is used to receive the login request instruction sent by the client, parse the login request instruction, and obtain parsing information, which includes the identity identifier, mobile phone number, account name and password combination;

[0105] The query splitting module 502 is used to query whether there is whitelist information with a mapping relationship with the identity identifier in a preset whitelist database. When the whitelist information does not exist, the combined password is split to obtain a login password and a verification code;

[0106] Verification module 503, used to verify the consistency of the account name and the login password according to the account database to obtain a first verification result, and verify the consistency of the verification code and the mobile phone number according to the verification code sending record to obtain a second verification result;

[0107] A generating and sending module 504 is used to generate abnormal login information if one of the first verification result and the second verification result fails, and send the abnormal login information to the client;

[0108] A generation upload module 505 is used to generate an abnormal login report according to the abnormal login information, and upload the abnormal login report to the blockchain;

[0109] In this embodiment, the receiving and parsing module 501 includes: creating a monitoring unit 5011, which is used to create an access listener and use the access listener to monitor the client's access to the login page; generating a return unit 5012, which is used to generate a verification code and return it to the client when monitoring the client's access to the login page, so that the client can configure a combination password; a saving unit 5013, which is used to save the verification code in the verification code sending record; a receiving and decrypting unit 5014, which is used to receive the login request instruction sent by the client after being encrypted with the public key, and use the private key to decrypt the login request instruction to obtain decrypted information; a parsing unit 5015, which is used to parse the decrypted information to obtain parsed information, and the parsed information includes an identity identifier, a mobile phone number, an account name, and a combination password.

[0110] In this embodiment, the query splitting module 502 includes: an identification and grading unit 5021, which is used to identify the ID identification of each login outlet, and grade the login outlets to obtain outlet grading information; a configuration unit 5022, which is used to configure the first login restriction cancellation information according to the ID identification and the outlet grading information; a construction unit 5023, which is used to construct a whitelist database according to the first login restriction cancellation information; a query unit 5024, which is used to query whether there is an ID identification with a mapping relationship with the identity identification in the preset whitelist database; a splitting unit 5025, which is used to split the combined password to obtain the login password and the verification code when the ID identification does not exist.

[0111] In this embodiment, the verification module 503 includes: a calling unit 5031, used to call a preset account database; a first verification unit 5032, used to verify the consistency of the account name and the login password according to the account database, and obtain a first verification result; an acquisition unit 5033, used to obtain a verification code sending record; a second verification unit 5034, used to verify the consistency of the verification code and the mobile phone number according to the verification code sending record, and obtain a second verification result.

[0112] In this embodiment, the generation and sending module 504 includes: an allowing unit 5041, which is used to allow the client to log in if both the first verification result and the second verification result are passed; a generating unit 5042, which is used to generate abnormal login information if one of the first verification result and the second verification result is failed; a sending unit 5043, which is used to send the abnormal login information to the client, so that the client generates and displays an abnormal login page based on the abnormal login information.

[0113] In this embodiment, the generation upload module 505 includes: an extraction and identification unit 5051, which is used to extract the report template and identify the fill area in the report template; a filling and recording unit 5052, which is used to fill the abnormal login information into the fill area of ​​the report template to generate an abnormal login report, and record the report generation time; a merging unit 5053, which is used to merge the report generation time and the abnormal login report to obtain merged information; an uploading unit 5054, which is used to upload the merged information to the blockchain.

[0114] In this embodiment, it also includes: an acquisition module 506, which is used to obtain a new list of the white list; a configuration module 507, which is used to configure the second login restriction cancellation information according to the new list of the white list; and an update module 508, which is used to update the white list database based on the second login restriction cancellation information.

[0115] above Figure 5 and Figure 6 The logistics platform login security configuration verification device in the embodiment of the present invention is described in detail from the perspective of modular functional entities. The logistics platform login security configuration verification device in the embodiment of the present invention is described in detail from the perspective of hardware processing.

[0116] Figure 7 6 is a structural diagram of a logistics platform login security configuration verification device provided by an embodiment of the present invention. The logistics platform login security configuration verification device 600 may have relatively large differences due to different configurations or performances, and may include one or more processors (central processing units, CPU) 610 (for example, one or more processors) and a memory 620, and one or more storage media 630 (for example, one or more mass storage devices) storing application programs 633 or data 632. Among them, the memory 620 and the storage medium 630 can be short-term storage or permanent storage. The program stored in the storage medium 630 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations in the logistics platform login security configuration verification device 600. Furthermore, the processor 610 can be configured to communicate with the storage medium 630, and execute a series of instruction operations in the storage medium 630 on the logistics platform login security configuration verification device 600 to implement the steps of the logistics platform login security configuration verification method provided by the above-mentioned method embodiments.

[0117] The logistics platform login security configuration verification device 600 may also include one or more power supplies 640, one or more wired or wireless network interfaces 650, one or more input and output interfaces 660, and / or one or more operating systems 631, such as Windows Serve, Mac OS X, Unix, Linux, FreeBSD, etc. Those skilled in the art will appreciate that Figure 7 The logistics platform login security configuration verification device structure shown does not constitute a limitation on the logistics platform login security configuration verification device, and may include more or fewer components than shown in the figure, or a combination of certain components, or a different arrangement of components.

[0118] The present invention also provides a computer-readable storage medium, which may be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium. Instructions are stored in the computer-readable storage medium. When the instructions are executed on a computer, the computer executes the steps of a logistics platform login security configuration verification method.

[0119] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described system, device, or unit can refer to the corresponding process in the aforementioned method embodiment and will not be repeated here.

[0120] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program codes.

[0121] Finally, it should be noted that the above description is only a preferred example of the present invention and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art can still modify the technical solutions described in the aforementioned embodiments or replace some of the technical features therein by equivalents. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A logistics platform login security configuration verification method, characterized in that: include: Receiving a login request instruction sent by a client, parsing the login request instruction to obtain parsing information, the parsing information including an identity identifier, a mobile phone number, an account name, and a combination password; Querying a preset whitelist database to determine whether there is whitelist information having a mapping relationship with the identity identifier; when the whitelist information does not exist, splitting the combined password to obtain a login password and a verification code; Verifying the consistency of the account name and the login password according to the account database to obtain a first verification result, and verifying the consistency of the verification code and the mobile phone number according to the verification code sending record to obtain a second verification result; If one of the first verification result and the second verification result is failed, abnormal login information is generated and sent to the client; Generate an abnormal login report based on the abnormal login information, and upload the abnormal login report to the blockchain.

2. The method for verifying the security configuration of a logistics platform login according to claim 1 is characterized in that: The receiving client sends a login request instruction, and parses the login request instruction to obtain parsing information, wherein the parsing information includes an identity identifier, a mobile phone number, an account name, and a combination password, including: Create an access listener, and use the access listener to monitor the client's access to the login page; When monitoring that the client accesses the login page, generating a verification code and returning it to the client, so that the client can configure a combination password; Saving the verification code in the verification code sending record; Receive the login request instruction sent by the client after being encrypted with the public key, and decrypt the login request instruction using the private key to obtain decrypted information; The decrypted information is parsed to obtain parsed information, wherein the parsed information includes an identity identifier, a mobile phone number, an account name, and the combined password.

3. The method for verifying the security configuration of a logistics platform login according to claim 1 is characterized in that: The querying of a preset whitelist database to determine whether there is whitelist information having a mapping relationship with the identity identifier, and when the whitelist information does not exist, splitting the combined password to obtain a login password and a verification code, includes: Identify the ID of each login outlet, and classify the login outlets to obtain outlet classification information; configuring first login restriction cancellation information according to the ID identification and the network point classification information; Building a whitelist database according to the first login restriction cancellation information; Querying a preset whitelist database to determine whether there is an ID identifier that has a mapping relationship with the identity identifier; When the ID identification does not exist, the combined password is split to obtain a login password and a verification code.

4. The method for verifying the security configuration of a logistics platform login according to claim 1 is characterized in that: The verification of the consistency of the account name and the login password according to the account database to obtain a first verification result, and the verification of the consistency of the verification code and the mobile phone number according to the verification code sending record to obtain a second verification result, include: Call the preset account database; Verifying the consistency of the account name and the login password according to the account database to obtain a first verification result; Get verification code sending records; The consistency between the verification code and the mobile phone number is verified according to the verification code sending record to obtain a second verification result.

5. The method for verifying the security configuration of a logistics platform login according to claim 1 is characterized in that: If one of the first verification result and the second verification result is failed, generating abnormal login information and sending the abnormal login information to the client includes: If both the first verification result and the second verification result are passed, allowing the client to log in; If one of the first verification result and the second verification result fails, abnormal login information is generated; The abnormal login information is sent to the client, so that the client generates and displays an abnormal login page based on the abnormal login information.

6. The method for verifying the security configuration of a logistics platform login according to claim 1 is characterized in that: The generating an abnormal login report according to the abnormal login information and uploading the abnormal login report to the blockchain includes: extracting a report template and identifying a fill area in the report template; Fill the abnormal login information into the filling area of ​​the report template to generate an abnormal login report, and record the report generation time; Merging the report generation time with the abnormal login report to obtain merged information; The merged information is uploaded to the blockchain.

7. The method for verifying the security configuration of a logistics platform login according to claim 1 is characterized in that: After generating an abnormal login report according to the abnormal login information and uploading the abnormal login report to the blockchain, the method further includes: Get the new whitelist list; Configure the second login restriction cancellation information according to the newly added list of the whitelist; The whitelist database is updated based on the second login restriction cancellation information.

8. A logistics platform login security configuration verification device, characterized in that: include: A receiving and parsing module, configured to receive a login request instruction sent by a client, parse the login request instruction, and obtain parsing information, wherein the parsing information includes an identity identifier, a mobile phone number, an account name, and a combination password; A query splitting module is used to query whether there is whitelist information with a mapping relationship with the identity identifier in a preset whitelist database, and when the whitelist information does not exist, split the combined password to obtain a login password and a verification code; A verification module, configured to verify the consistency of the account name and the login password according to the account database to obtain a first verification result, and verify the consistency of the verification code and the mobile phone number according to the verification code sending record to obtain a second verification result; A generating and sending module, configured to generate abnormal login information if one of the first verification result and the second verification result is failed, and send the abnormal login information to the client; A generation and uploading module is used to generate an abnormal login report according to the abnormal login information, and upload the abnormal login report to the blockchain.

9. A logistics platform login security configuration verification device, characterized in that: The logistics platform login security configuration verification device includes: a memory and at least one processor, wherein the memory stores instructions; At least one of the processors calls the instructions in the memory so that the logistics platform login security configuration verification device executes each step of the logistics platform login security configuration verification method as described in any one of claims 1-7.

10. A computer-readable storage medium having instructions stored thereon, characterized in that: When the instruction is executed by the processor, each step of the logistics platform login security configuration verification method as described in any one of claims 1-7 is implemented.