A login control method, system, storage medium, and electronic device.

Abstract

This invention provides a login control method, system, storage medium, and electronic device. The method includes: parsing a user login request to obtain and generate URL parameters based on user device information; adding the URL parameters to a target URL to obtain a login URL; sending the login URL to a client and using the login URL to send authentication information to a second server for verification; receiving callback parameters returned by the second server, parsing the callback parameters to obtain a verification result, and if the verification result is successful, obtaining user registration information; if the URL parameters are obtained through parsing, obtaining user device information based on the URL parameters; generating a security authentication result based on the user device information and user registration information, and using the security authentication result to control user login. This invention improves account security by controlling user login based on a security authentication result obtained from user device information and user registration information.

Description

Technical Field

[0001] This invention relates to the field of Internet technology, and in particular to a login control method, system, storage medium, and electronic device. Background Technology

[0002] During user login, typically only user identity is authenticated, and login is successful upon successful authentication. However, in some business scenarios requiring security controls for login operations, such as device verification, this login method, which only verifies user identity, lacks safeguards for user account security. This fails to guarantee the security of the login system and user accounts, increasing the risk of login failures. Therefore, implementing user login controls to mitigate these risks is essential. Summary of the Invention

[0003] The purpose of this invention is to provide a login control method, system, storage medium, and electronic device that can improve account security and prevention. The specific technical solution is as follows:

[0004] This invention provides a login control method applied to a first server, the method comprising:

[0005] Receive user login requests and parse the user login requests to obtain user device information, and generate URL parameters based on the user device information;

[0006] Add the URL parameter to the target URL corresponding to the user login request to obtain the login URL;

[0007] The login URL is sent to the client, so that the client uses the login URL to send identity authentication information to a second server for verification; the second server is a different server from the first server.

[0008] The system receives callback parameters returned by the second server, parses the callback parameters to obtain a verification result, and if the verification result is successful, obtains user registration information based on the successful verification result; if the URL parameter is obtained through parsing, the system obtains user device information based on the URL parameter.

[0009] A security authentication result is generated based on the user device information and the user registration information, and the security authentication result is used for user login control.

[0010] Optionally, the user equipment information includes at least a device identifier, and after generating the URL parameters based on the user equipment information, the method further includes:

[0011] If the amount of data in the URL parameter is less than the preset amount of data, the URL parameter is sent to the client for storage.

[0012] And / or,

[0013] The URL parameters and the device identifier are sent to the cloud for corresponding storage.

[0014] Optional, also includes:

[0015] If the URL parameters are not obtained, the URL parameters stored in the client are obtained;

[0016] or,

[0017] If the URL parameter is not obtained, the URL parameter corresponding to the device identifier stored in the cloud is obtained.

[0018] Optionally, obtaining user registration information based on the verified result includes:

[0019] The verification result that passes the verification is sent to the second server to obtain the access token returned by the second server;

[0020] The access token is sent to the second server to obtain second identification information; the second identification information is user identification information stored on the second server.

[0021] Find the first identification information that corresponds to the second identification information; the first identification information is user identification information stored on the first server.

[0022] The user registration information corresponding to the first identification information is obtained by using the first identification information stored in the first server.

[0023] Optionally, the step of using the security authentication result for user login control includes:

[0024] If the security authentication result is successful, the login information carrying the first identification information is sent to the client so that the client can perform a login operation based on the login information.

[0025] Optionally, generating URL parameters based on the user equipment information includes:

[0026] The user equipment information is compressed, and the compressed user equipment information is encrypted to generate the URL parameters;

[0027] or,

[0028] The user equipment information is encrypted, and the encrypted user equipment information is compressed to generate the URL parameters.

[0029] Optionally, obtaining the user device information based on the URL parameters includes:

[0030] If the URL parameter is obtained by compressing the user equipment information and encrypting the compressed user equipment information, the URL parameter is decrypted, and the decrypted information is decompressed to obtain the user equipment information.

[0031] If the URL parameter is obtained by encrypting the user device information and compressing the encrypted user device information, the URL parameter is decompressed, and the decompressed information is decrypted to obtain the user device information.

[0032] The present invention also provides a login control system applied to a first server, the system comprising:

[0033] The URL parameter generation module is configured to receive user login requests, parse the user login requests, obtain user device information, and generate URL parameters based on the user device information;

[0034] The login URL acquisition module is configured to add the URL parameter to the target URL corresponding to the user login request to obtain the login URL;

[0035] The information verification module is configured to send the login URL to the client, so that the client uses the login URL to send identity authentication information to a second server for verification; the second server is a different server from the first server.

[0036] The parsing module is configured to receive callback parameters returned by the second server, parse the callback parameters to obtain a verification result, and if the verification result is successful, obtain user registration information based on the successful verification result; if the URL parameter is obtained through parsing, obtain user device information based on the URL parameter.

[0037] The login control module is configured to generate a security authentication result based on the user device information and the user registration information, and to use the security authentication result to control user login.

[0038] The present invention also provides a computer-readable storage medium storing a program that, when executed by a processor, implements the above-described login control method.

[0039] The present invention also provides an electronic device, comprising:

[0040] At least one processor, and at least one memory and bus connected to the processor;

[0041] The processor and the memory communicate with each other via the bus; the processor is used to call program instructions in the memory to execute the above-mentioned login control method.

[0042] This invention provides a login control method, system, storage medium, and electronic device. The login URL carries URL parameters obtained based on user device information. User device information can be obtained through the URL parameters. User login control is performed based on the security authentication result obtained based on user device information and user registration information. By obtaining user device information, the effectiveness of account security control can be improved in some business scenarios that require device verification.

[0043] Of course, any product or method implementing the present invention does not necessarily need to achieve all of the advantages described above at the same time. Attached Figure Description

[0044] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0045] Figure 1 A flowchart of a login control method provided in an embodiment of the present invention;

[0046] Figure 2 Signaling diagram of one embodiment of the login control method provided in this invention;

[0047] Figure 3 Signaling diagram of another embodiment of the login control method provided in this invention;

[0048] Figure 4 Signaling diagram of another embodiment of the login control method provided in this invention;

[0049] Figure 5 A structural diagram of a login control system provided in an embodiment of the present invention;

[0050] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0051] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0052] This invention provides a login control method applied to a first server, which has a login interface and a callback interface.

[0053] A server can be either hardware or software. When it's hardware, it can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. When it's software, it can be implemented as multiple software programs or software modules (e.g., used to provide distributed services), or as a single software program or software module. No specific limitations are made here. The login interface and callback interface can be deployed on the same primary server or on different servers; data from the login interface and the callback interface cannot be shared.

[0054] like Figure 1 As shown, the login control method provided by this invention is applied to a first server, and the method includes:

[0055] Step 101: Receive the user login request and parse it to obtain the user device information, and generate URL parameters based on the user device information.

[0056] A user login request can be a request sent by the client to log in to the target APP (Application). Parsing the user login request reveals that the user is logging in to the target APP using an account registered in another APP besides the target APP.

[0057] When a client sends a user login request, it can send the context information of the user login request to the login interface of the first server. This login interface receives and parses the user login request. This context information can include user device information, which reflects the user's device used to log in to the target app. This user device information can include one or more of the following: device identifier, device origin, device origin address, and origin platform. The device identifier can be a device identification code, such as the International Mobile Equipment Identity (IMEI); the device origin can be a mobile device or a PC; the device origin address can be an IP address; and the origin platform can be the device's operating system, such as Android or iOS. Based on the above user device information, the security of the user account can be detected, thereby implementing account security controls during user login.

[0058] As an optional implementation, the method for generating URL parameters based on user device information includes: compressing the user device information, encrypting the compressed user device information, and obtaining the URL parameters.

[0059] As another optional implementation, the method for generating URL parameters based on user equipment information includes: encrypting the user equipment information, compressing the encrypted user equipment information, and obtaining the URL parameters.

[0060] Step 102: Add the URL parameters to the target URL corresponding to the user login request to obtain the login URL.

[0061] The login interface parses user login requests, obtaining not only user device information but also the target URL pointed to by the login request. This target URL can provide the user with a login page. The method for obtaining this target URL can be as follows: identify the client type based on the user login request; if the client type is a mobile app, obtain the first target URL, which can provide the user with the mobile app login page; if the client type is a web browser, obtain the second target URL, which can provide the user with a web-based login page.

[0062] Optionally, the URL parameter can be a state parameter, which is a user-defined parameter that can be embedded in the URL as a suffix. Adding the state parameter to the target URL will not affect the validity of the target URL. That is, the login URL obtained after adding the URL parameter to the target URL can provide a login page for the user, and the login page corresponding to the login URL can be the same as the login page corresponding to the target URL.

[0063] Step 103: Send the login URL to the client so that the client can use the login URL to send its authentication information to the second server for verification. The second server is a different server from the first server.

[0064] After the login interface of the first server sends the login URL to the client, the client can be redirected to the login page via the URL, obtain the identity authentication information entered by the user on the login page, and send this identity authentication information to the second server for verification. Of course, if the login page displays an authorization button or authorization QR code, the authorization information generated after the user performs an operation based on the authorization button or authorization QR code can be sent from the login page to the second server.

[0065] The authentication information can be the user's authentication information entered in other apps besides the target app, such as username and password. The first server can be the target app's server, and the second server can be the server of other apps besides the target app. The user's registration in other apps besides the target app has user information stored on the second server. After the authentication information is sent to the second server, the user's identity can be verified.

[0066] Step 104: Receive the callback parameters returned by the second server, parse the callback parameters to obtain the verification result. If the verification result is successful, obtain the user registration information based on the successful verification result; if the URL parameter is obtained by parsing, obtain the user device information based on the URL parameter.

[0067] After the second server verifies the identity authentication information, it sends a request to the callback address of the first server. The request carries callback parameters. After the second server verifies the identity authentication information, its callback parameters may include code information. By parsing the callback parameters, the verification result can be obtained. If the verification result is successful, the callback interface of the first server can request the user registration information from the second server.

[0068] As an optional implementation, obtaining user registration information based on a successful verification result includes: sending the successful verification result to a second server to obtain an access token returned by the second server; sending the access token to the second server to obtain second identification information; the second identification information is user identification information stored on the second server; searching for first identification information that corresponds to the second identification information; the first identification information is user identification information stored on the first server; and using the first identification information to obtain user registration information stored on the first server that corresponds to the first identification information.

[0069] Optionally, the verification result can be code information. The callback interface sends the code information to the second server in exchange for an access token, which can be a token parameter. After receiving the token parameter, the callback interface can obtain the second identification information, which is the user identification information stored on the second server. The second identification information can be an openid. The callback interface uses the correspondence between the second identification information and the first identification information to look up the user identification information stored on the first server and obtain the first identification information, which can be a uid. The user registration information can be obtained through the uid.

[0070] If the user identifier information stored on the first server cannot be found using the correspondence between the second identifier information and the first identifier information, then the user is not registered in the target app. In this case, an account for the target app can be registered for the user based at least on the second identifier information openid returned by the second server. Alternatively, an account for the target app can be registered for the user based on the second identifier information openid returned by the second server, the user's avatar and nickname stored on the second server.

[0071] Because server interface interactions are based on the HTTP protocol, which is a stateless protocol based on a request-response model, parameters cannot be shared between requests. Therefore, data from the login interface and the callback interface cannot be shared. This invention sends user device information to a second server through the login interface of the first server, and then uses the second server to call back to the callback interface of the first server. In this way, the callback interface contains the user device information.

[0072] The callback parameters returned by the second server may or may not include URL parameters. If the URL parameters are parsed from the callback parameters, user device information can be obtained based on the URL parameters.

[0073] As an optional implementation, obtaining user device information based on URL parameters includes:

[0074] If the URL parameters are obtained by compressing and encrypting the user device information, then the URL parameters are decrypted, and the decrypted information is decompressed to obtain the user device information.

[0075] If the URL parameters are obtained by encrypting and compressing the encrypted user device information, then the URL parameters are decompressed, and the decompressed information is decrypted to obtain the user device information.

[0076] Optionally, the user equipment information can be encrypted using a symmetric encryption method. After encryption, the information can be decrypted using the same method. Alternatively, the user equipment information can be compressed using protobuf serialization, thus compressing its length. Decompression can then be performed using protobuf deserialization. Through these operations, the user equipment information can be obtained.

[0077] To prevent the callback interface from not receiving user device information when the second server fails to return the URL parameter, after obtaining the URL parameter based on the user device information in step 101, the login interface can send the URL parameter to the client and / or the cloud for storage, so that the URL parameter can be obtained from the client and / or the cloud when the second server fails to return the URL parameter.

[0078] As an optional implementation, after the login interface obtains the URL parameters based on the user device information, if the amount of URL parameters is less than the preset amount of data, the URL parameters are sent to the client for storage.

[0079] In this implementation, the callback interface can obtain the URL parameters stored on the client even if it does not receive the URL parameters returned by the second server.

[0080] Optionally, the login interface sends the URL parameters to the client as cookies. Cookies have a length limit, and this preset data size can be the maximum allowed data size for a cookie. If the URL parameter data size is less than the preset data size, the login interface sends the URL parameters to the client for storage. If the URL parameter data size is greater than the preset data size, the callback interface will fail to retrieve the URL parameters stored on the client.

[0081] As another optional implementation, after the login interface obtains the URL parameters based on the user's device information, it sends the URL parameters and device identifier to the cloud for corresponding storage.

[0082] In this implementation, if the callback interface fails to obtain the URL parameters returned by the second server or fails to obtain the URL parameters from the client, the callback interface can obtain the URL parameters corresponding to the device identifier stored in the cloud.

[0083] Step 105: Generate a security authentication result based on the user device information and user registration information, and use the security authentication result to control user login.

[0084] Optionally, the first server can generate a security authentication result based on user device information and user registration information. User registration information may include one or more of the following: email address, mobile phone number, username, and password. Alternatively, the email address, mobile phone number, and password can be anonymized before being sent to the security control system along with the user device information. The security control system can then assess the security of this user login operation based on the user device information and user registration information to obtain a security authentication result, which reflects whether the user login is secure.

[0085] As an optional implementation, user login control is performed using the security authentication result, including: if the security authentication result is successful, the callback interface sends login information carrying the first identification information to the client, so that the client can perform a login operation based on the login information.

[0086] Figure 2 This is a signaling diagram of one embodiment of the login control method according to this application, such as... Figure 2 As shown, in step 201, the user client sends a user login request to the first server. The login interface of the first server receives the user login request.

[0087] In step 202, the login interface of the first server parses the user login request to obtain user device information, obtains the URL parameter based on the user device information, and adds the URL parameter to the target URL pointed to by the user login request to obtain the login URL. Optionally, this URL parameter is a state parameter, and the state parameter is used as the suffix of the target URL to obtain the login URL.

[0088] In step 203, the login interface of the first server sends the login URL to the user client.

[0089] In step 204, the user client can send authentication information to the second server via the login URL.

[0090] In step 205, the second server verifies the identity authentication information and returns the verification result to the callback interface of the first server, and at the same time returns the URL parameter value to the callback interface of the first server.

[0091] In step 206, the callback interface of the first server can obtain user registration information based on the verification result that has passed the verification, and can also obtain user device information based on the URL parameters.

[0092] Optionally, the process of obtaining user registration information based on the successful verification result can be as follows: the callback interface of the first server sends the successful verification result to the second server, and the second server returns an access token to the callback interface; the callback interface sends the access token to the second server, and the second server sends the second identification information to the first server, wherein the second identification information is the user identification information stored on the second server; the callback interface looks up the first identification information, wherein the first identification information is the user identification information stored on the first server corresponding to the second identification information; the callback interface obtains the user registration information corresponding to the first identification information.

[0093] In step 207, the callback interface of the first server sends user registration information and user device information to the security control system.

[0094] In step 208, the security control system generates a security authentication result based on user registration information and user device information.

[0095] In step 209, the security control system sends the security authentication result to the callback interface of the first server.

[0096] In step 210, the callback interface of the first server controls user login based on the security authentication result.

[0097] Figure 3 This is a signaling diagram of another embodiment of the login control method according to this application, such as... Figure 3 As shown, Figure 3 The steps and Figure 2 The difference in the steps is:

[0098] In step 303, the login interface of the first server sends the URL parameters to the user client. Optionally, if the amount of data in the URL parameters is less than a preset amount, the first server can send the URL parameters as a cookie to the user client.

[0099] In step 304, the user client stores the URL parameters.

[0100] In step 307, the second server returns the verification result to the first server. If the second server cannot return the URL parameters to the first server, proceed to step 308.

[0101] In step 308, the first server obtains the URL parameters from the user client and then executes step 309.

[0102] Figure 4 This is a signaling diagram of another embodiment of the login control method according to this application, such as... Figure 4 As shown, Figure 4 The steps and Figure 2The difference in the steps is:

[0103] In step 403, the first server sends the URL parameters to the cloud. Optionally, the login interface of the first server sends the URL parameters and the device identifier in the user device information to the cloud for corresponding storage.

[0104] In step 404, the URL parameters are stored in the cloud.

[0105] In step 407, the second server returns the verification result to the first server. If the second server cannot return the URL parameters to the first server, proceed to step 408.

[0106] In step 408, the first server retrieves the URL parameters from the cloud. Optionally, the callback interface of the first server retrieves the URL parameters corresponding to the device identifier stored in the cloud.

[0107] The present invention also provides a login control system, applied to a first server, such as... Figure 5 As shown, the system includes:

[0108] The URL parameter generation module 501 is configured to receive user login requests, parse the user login requests, obtain user device information, and generate URL parameters based on the user device information.

[0109] The URL parameter generation module 501 is specifically configured to compress user device information, encrypt the compressed user device information, and generate URL parameters; or, encrypt user device information, compress the encrypted user device information, and generate URL parameters.

[0110] The login URL acquisition module 502 is configured to add URL parameters to the target URL corresponding to the user login request to obtain the login URL.

[0111] The information verification module 503 is configured to send the login URL to the client, so that the client can use the login URL to send the identity authentication information to the second server for verification; the second server is a different server from the first server.

[0112] The parsing module 504 is configured to receive callback parameters returned by the second server, parse the callback parameters to obtain the verification result, and if the verification result is successful, obtain the user registration information based on the successful verification result; if the URL parameter is obtained by parsing, obtain the user device information based on the URL parameter.

[0113] The parsing module 504 is specifically configured to send the verification result that has passed the verification to the second server to obtain the access token returned by the second server; send the access token to the second server to obtain the second identification information; the second identification information is the user identification information stored on the second server; search for the first identification information that has a corresponding relationship with the second identification information; the first identification information is the user identification information stored on the first server; and use the first identification information to obtain the user registration information stored on the first server that corresponds to the first identification information.

[0114] The parsing module 504 is also configured to, when the URL parameter is obtained by compressing and encrypting the user device information, decrypt the URL parameter, decompress the decrypted information, and obtain the user device information; and when the URL parameter is obtained by encrypting and compressing the encrypted user device information, decompress the URL parameter, decrypt the decompressed information, and obtain the user device information.

[0115] The login control module 505 is configured to generate a security authentication result based on user device information and user registration information, and to use the security authentication result to control user login.

[0116] The login control module 505 is specifically configured to send login information carrying the first identification information to the client if the security authentication result is successful, so that the client can perform a login operation based on the login information.

[0117] The login control system also includes:

[0118] The parameter sending module is configured to send the URL parameters to the client storage when the amount of URL parameters is less than the preset amount of data; and / or send the URL parameters and device identifier to the cloud for corresponding storage.

[0119] The parameter acquisition module is configured to acquire the URL parameters stored on the client if no URL parameters are available; or, if no URL parameters are available, acquire the URL parameters corresponding to the device identifier stored in the cloud.

[0120] This invention provides a computer-readable storage medium storing a program that, when executed by a processor, implements the above-described login control method.

[0121] This invention provides an electronic device, such as... Figure 6As shown, the electronic device 60 includes at least one processor 601, at least one memory 602 connected to the processor 601, and a bus 603; wherein the processor 601 and the memory 602 communicate with each other through the bus 603; the processor 601 is used to call program instructions in the memory 602 to execute the above-mentioned login control method. The electronic device in this document may be a server, PC, PAD, mobile phone, etc.

[0122] This application also provides a computer program product that, when executed on a data processing device, is adapted to perform the steps included in the above-described login control method for initialization.

[0123] This application is described with reference to flowchart illustrations and / or block diagrams of methods, systems, and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0124] In a typical configuration, the device includes one or more processors (CPUs), memory, and a bus. The device may also include input / output interfaces, network interfaces, etc.

[0125] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, like read-only memory (ROM) or flash RAM, and memory includes at least one memory chip. Memory is an example of computer-readable media.

[0126] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0127] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0128] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

[0129] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0130] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A login control method characterized by comprising: Applied to a first server, the method comprises: Receiving a user login request and parsing the user login request to obtain user device information, and generating a website parameter based on the user device information; Adding the website parameter to a target website corresponding to the user login request to obtain a login website; Sending the login website to a client to enable the client to send identity authentication information to a second server for verification using the login website; the second server and the first server are different servers; Receiving a callback parameter returned by the second server, parsing the callback parameter to obtain a verification result, and if the verification result is a verification pass, obtaining user registration information based on the verification result of the verification pass; based on the parsed website parameter, obtaining the user device information based on the website parameter; Generating a security authentication result based on the user device information and the user registration information, and performing user login control using the security authentication result.

2. The login control method according to claim 1, characterized by, The user device information at least includes a device identifier, and after the website parameter is generated based on the user device information, the method further comprises: In the case where the data amount of the website parameter is less than a preset data amount, the website parameter is sent to the client for storage; And / or, The website parameter and the device identifier are sent to the cloud for corresponding storage.

3. The login control method according to claim 2, characterized by, Further comprising: In the case where the website parameter is not obtained, the website parameter stored by the client is acquired; Or, In the case where the website parameter is not obtained, the website parameter corresponding to the device identifier stored by the cloud is acquired.

4. The login control method according to claim 1, characterized by, The user registration information is obtained based on the verification result of the verification pass, comprising: The verification result of the verification pass is sent to the second server to obtain an access token returned by the second server; The access token is sent to the second server to obtain second identifier information; the second identifier information is user identifier information stored in the second server; The first identifier information having a corresponding relationship with the second identifier information is found; the first identifier information is user identifier information stored in the first server; The user registration information corresponding to the first identifier information stored in the first server is obtained using the first identifier information.

5. The login control method according to claim 4, characterized by, The user login control is performed using the security authentication result, comprising: If the security authentication result is a security authentication pass, login information carrying the first identifier information is sent to the client to enable the client to perform a login operation based on the login information.

6. The login control method according to claim 1, wherein The website parameter is generated based on the user device information, comprising: The user device information is compressed, and the compressed user device information is encrypted to generate the website parameter; Or, The user device information is encrypted, and the encrypted user device information is compressed to generate the website parameter.

7. The log-in control method according to any one of claims 1 to 6, characterized by, The user device information is obtained based on the website parameter, comprising: In a case where the website parameter is obtained by compressing the user equipment information and encrypting the compressed user equipment information, the website parameter is decrypted, and the decrypted information is decompressed to obtain the user equipment information. In a case where the website parameter is obtained by compressing the user equipment information and encrypting the compressed user equipment information, the website parameter is decrypted, and the decrypted information is decompressed to obtain the user equipment information.

8. A login control system characterized by comprising: The system is applied to a first server, and the system comprises: a website parameter generation module configured to receive a user login request, analyze the user login request, obtain user equipment information, and generate a website parameter based on the user equipment information; a login website obtaining module configured to add the website parameter to a target website corresponding to the user login request to obtain a login website; an information verification module configured to send the login website to a client to enable the client to send identity authentication information to a second server for verification by using the login website; the second server is different from the first server; an analysis module configured to receive a callback parameter returned by the second server, analyze the callback parameter to obtain a verification result, obtain user registration information based on the verification result if the verification result is verified, and obtain the user equipment information based on the website parameter in a case where the website parameter is analyzed; a login control module configured to generate a security authentication result based on the user equipment information and the user registration information, and perform user login control by using the security authentication result.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a program, and the program is executed by the processor to implement the login control method in any one of claims 1-7.

10. An electronic device, comprising: comprise: at least one processor and at least one memory connected to the processor; the processor, the memory and the bus complete communication between each other; the processor is configured to call program instructions in the memory to execute the login control method in any one of claims 1-7.

Images