Login control method and device and electronic equipment

Abstract

The invention discloses a login control method and device and electronic equipment, and the method comprises the steps: obtaining login information of a user after the user logs in a target system through a server, and storing the login information in a first database which is a database deployed corresponding to the server in a database cluster, the database cluster is configured to synchronize the information of each user in each database; receiving an operation request of a target user, and querying login information of the target user from the first database; and judging whether the inquired login information is consistent with the login information carried by the operation request or not. According to the method, the risk of data leakage caused by multi-point login can be avoided, and the security of the business systems deployed by a plurality of centers is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a login control method, device and electronic device. Background Art

[0002] With the popularization of the Internet and the development of terminal technology, the business needs of network service providers are also growing, and the amount of information that their business systems need to process is increasing. In order to adapt to the growing business needs, network service providers will enhance their business processing capabilities by deploying business systems in multiple centers.

[0003] The successful processing of business depends on a secure and reliable business processing environment. Therefore, as business needs grow, more and more attention should be paid to the security of each business system.

[0004] Currently, for business systems deployed in multiple centers, the same account can be used to log in on different browsers or even in different locations without restriction. This poses a risk of data leakage and has poor security, which urgently needs to be improved. Summary of the invention

[0005] The embodiments of the present application provide a login control method, device and electronic device to avoid the risk of data leakage caused by multi-point login and improve the security of business systems deployed in multiple centers.

[0006] In a first aspect, an embodiment of the present application provides a login control method, which is applied to a server, and the method includes:

[0007] After the user logs in to the target system through the server, the user's login information is obtained and stored in the first database, wherein the first database is a database deployed in the database cluster corresponding to the server, and the database cluster is configured to synchronize the information of each user in each database;

[0008] receiving an operation request from a target user, and querying the login information of the target user from the first database;

[0009] Determine whether the queried login information is consistent with the login information carried in the operation request;

[0010] If they are inconsistent, the target user's login to the target system is terminated.

[0011] In a second aspect, an embodiment of the present application further provides a login control method, which is applied to a client, and the method includes:

[0012] After the user logs in to the target system through the client, the user's login information is sent to the server corresponding to the client, so that the server stores the login information in a first database, wherein the first database is a database deployed in a database cluster corresponding to the server, and the database cluster is configured to synchronize the information of each user in each database;

[0013] An operation request is initiated to the server so that the server determines whether the login information of the user carried in the operation request is consistent with the login information of the user queried from the first database. If not, the user's login to the target system is terminated.

[0014] In a third aspect, an embodiment of the present application further provides a login control device, which is applied to a server, and the device includes:

[0015] An information storage module, used to obtain the login information of the user and store it in a first database after the user logs in to the target system through the server, wherein the first database is a database deployed in the database cluster corresponding to the server, and the database cluster is configured to synchronize the information of each user in each database;

[0016] An operation request receiving module, used to receive an operation request from a target user, and query the login information of the target user from the first database;

[0017] A judgment module, used to judge whether the queried login information is consistent with the login information carried in the operation request, and if not, trigger the login control module;

[0018] The login control module is used to terminate the target user's login to the target system.

[0019] In a fourth aspect, an embodiment of the present application further provides a login control device, applied to a client, the device comprising:

[0020] An information sending module, configured to send the user's login information to a server corresponding to the client after the user logs in to the target system through the client, so that the server stores the login information in a first database, wherein the first database is a database deployed in a database cluster corresponding to the server, and the database cluster is configured to synchronize the information of each user in each database;

[0021] An operation request sending module is used to initiate an operation request to the server, so that the server determines whether the login information of the user carried in the operation request is consistent with the login information of the user queried from the first database. If not, the user's login to the target system is terminated.

[0022] In the fifth aspect, an embodiment of the present application further provides an electronic device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the computer program is executed by the processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0023] In a sixth aspect, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0024] At least one of the above-mentioned technical solutions adopted in the embodiments of the present application is that after the user logs in to the target system, the server will store the login information in the database corresponding to the server, and will synchronize the login information to the remaining databases to ensure the consistency of the multi-center user login information. After that, the client will initiate an operation request carrying the login information, and the server will compare the login information in the operation request with the login information stored in the database. If the two are consistent, it means that there is no situation where the user's account is used to log in to the target system multiple times. Otherwise, it means that there is a situation where the user's account is used to log in to the target system multiple times. Correspondingly, there is a risk of data leakage caused by multiple logins. At this time, terminating the user's login to the target system can eliminate the risk, thereby improving the security of the multi-center deployed target system. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0026] Figure 1 It is a deployment diagram of a target system provided in an embodiment of the present application.

[0027] Figure 2 It is a flowchart of a login control method provided in one embodiment of the present application.

[0028] Figure 3 It is a flowchart of a login control method provided in another embodiment of the present application.

[0029] Figure 4 It is a structural diagram of a login control device provided in one embodiment of the present application.

[0030] Figure 5 It is a structural diagram of a login control device provided in another embodiment of the present application.

[0031] Figure 6It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0032] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0033] In order to avoid the risk of data leakage caused by multi-point login and improve the security of business systems deployed in multiple centers, the embodiments of the present application provide a login control method, device and electronic device, which will be described below respectively.

[0034] It should be noted that the target system mentioned in the embodiments of the present application includes but is not limited to one of a business system, a business management system and an operation system, and the target system may specifically be an application.

[0035] The following is a description of the deployment architecture of the target system.

[0036] In an embodiment of the present application, the target system is deployed in multiple (more than two) centers. This deployment can also be called distributed deployment. These multiple centers can be located in different regions to handle the business needs of the region, and a database is deployed in each center.

[0037] Figure 1 FIG. 1 shows a schematic diagram of the deployment of a target system provided by an embodiment of the present application. Figure 1 As shown, the target system can be deployed in center 1, center 2 and center 3. Center 1 is deployed with multiple servers 12 and database 13 of the target system, center 2 is deployed with multiple servers 22 and database 23 of the target system, and center 3 is deployed with multiple servers 32 and database 33 of the target system. Under this deployment, the client 11 in center 1 can obtain services by accessing server 12, the client 21 in center 2 can obtain services by accessing server 22, and the client 31 in center 3 can obtain services by accessing server 32. The client may include but is not limited to: a client installed on any of smart terminal devices such as a smartphone, a personal computer (PC), a laptop, a tablet computer, an e-reader, an Internet TV, a wearable device, etc.

[0038] pass Figure 1It can be seen that in the deployment architecture of the target system provided in the embodiment of the present application, in addition to the deployment server, each center also deploys a database, which is used to store the login information of the client of this center after logging in to the target system, and for the same account, after using the account to re-login to the target system, the new login information will overwrite the previous login information.

[0039] Based on the above deployment architecture, the embodiments of the present application propose a login control method, device and electronic device, which are described in detail below.

[0040] like Figure 2 As shown, an embodiment of the present application provides a login control method, which can be applied to Figure 1 In any server of the center shown, the method may include:

[0041] Step 201: After a user logs in to a target system through the server, the user's login information is obtained and stored in a first database, wherein the first database is a database deployed in a database cluster corresponding to the server, and the database cluster is configured to synchronize information of each user in each database.

[0042] The user can log in to the target system by using an account and password. After receiving the login request, the server of the target system can authenticate the user using the preset authentication rules. After the authentication is passed, the user is allowed to log in to the target system. Accordingly, the user successfully logs in to the target system. After the user logs in to the target system through this server, the user's login information is obtained and stored in the first database, and the user login information stored in the first database is synchronized to other databases.

[0043] For example, as mentioned above, the target system may be deployed in multiple centers, wherein the first database belongs to the first center, and the first center is the center to which the user belongs among the multiple centers. Figure 1 As shown, assuming that the user covered by center 1 logs in to the target system through server 12 to which client 11 belongs, the first database is database 13, and the first center is center 1. After the user's login information is saved in database 13, it is synchronized to the databases of other centers.

[0044] There are many database synchronization technologies. Here, the database master-slave synchronization mechanism can be used to synchronize the data stored in other databases with the data stored in the first database. The database master-slave synchronization mechanism can achieve fast synchronization of data in different databases. In addition, since the database is only written when the user logs in. Therefore, the login control method provided in the embodiment of the present application can detect the risk of multiple logins of the target system by the same account in a very short time, generally within 5 seconds, so the speed of multi-login risk avoidance can be improved.

[0045] The user's login information may include, but is not limited to, at least one of the user identifier, the identifier of the target system, and preset information. The preset information is information that can uniquely identify the client. For example, the preset information may include at least one of the IP address used for this login, the session ID (session ID) of this login, and the identification information of the client. The user identifier may be a user name, such as an account number; when the target system is an application, the identifier of the target system may be an application identifier, such as an application name or an application ID; the client identifier may be a client MAC address or an International Mobile Equipment Identity (IMEI), etc.

[0046] Step 202: Receive an operation request from a target user, and query the login information of the target user from the first database.

[0047] The above operation request may be any operation of the target user on the target system. As an example, the operation request may be a polling request. Specifically, after the user successfully logs in to the target system through the client, the client may send a polling request to the server at a set time interval. The polling request may carry the login information of the user logging in to the target system through the client.

[0048] In one implementation, if the user's login information includes a user identifier, querying the target user's login information from the first database may include: querying the target user's login information from the first database using the user identifier in the login information carried by the operation request. It is understood that the first database may store the user's login information in correspondence with the user identifier, so after the target user's user identifier is known, the target user's login information may be queried accordingly.

[0049] In another embodiment, if the user's login information includes a user identifier and an identifier of the target system, querying the login information of the target user from the first database may include: querying the login information of the target user from the first database using the user identifier and the identifier of the target system in the login information carried by the operation request. It can be understood that when the first database stores user login information of multiple target systems, the login information of the target user can be obtained from the first database based on the user identifier of the target user and the identifier of the target system.

[0050] Optionally, a center can set up a unified gateway (designated gateway), and when querying the database in the database, the query can be performed through the unified gateway. The advantage of doing so is that for different target systems (in some business ecosystems, users can use the same account to log in to multiple systems under the ecosystem), the purpose of obtaining the data stored in the database can be achieved by introducing the jar package of the gateway, and the cost of modifying the target system is low. Accordingly, the above step 202 may include: querying the login information of the target user from the first database through the designated gateway.

[0051] Step 203, determine whether the queried login information is consistent with the login information carried in the operation request, if they are consistent, execute step 204, if they are inconsistent, return to execute step 202.

[0052] As described above, the database of each center in the embodiment of the present application is used to store the login information of the client of the center after logging into the target system, and for the same account, after using the account to log in to the target system again, the new login information will overwrite the previous login information, and each login will store the login information in the corresponding database. It can be understood that if the user covered by the first center uses his own account A to log in to the target system until the current polling request is initiated, and no user uses the account to log in to the target system again, then the login information of account A stored in the first database is still the login information when the user uses account A to log in to the target system for the first time; if the user covered by the first center uses his own account A to log in to the target system until the current polling request is initiated, and user A uses the account to log in to the target system again in other centers, then the login information of account A stored in the first database has changed and becomes the login information when the user uses account A to log in to the target system for the second time.

[0053] As an example, when the user's login information includes preset information, and the preset information includes at least one of the IP address used for this login, the session ID for this login, and the identification information of the client used for this login, wherein the determination of whether the queried login information is consistent with the login information carried by the operation request may include: determining whether the preset information in the queried login information is consistent with the preset information in the login information carried by the operation request.

[0054] Continuing with the example given in the previous step, if the queried login information is consistent with the login information carried in the operation request, it means that there is no multiple logins to the target system using account A, and polling can continue. Otherwise, it means that there are multiple logins to the target system using account A, and there is a corresponding risk of data leakage caused by multiple logins. The previous login can be forced to exit to avoid this risk.

[0055] Step 204: End the target user's login to the target system.

[0056] As an example, step 204 may specifically include: destroying the current login session, and returning a page for logging into the target system to the client to remind the user to log in again.

[0057] Optionally, after step 204, Figure 2 The method shown may also include: sending a prompt message to the target user, wherein the prompt message is used to prompt the user that the account used to log in to the target system has been logged in elsewhere, and / or remind the user whether your account has been stolen, please reset the password, etc., to protect the user's account security and avoid data leakage.

[0058] A login control method is provided in an embodiment of the present application. After a user logs in to a target system, the server stores the login information in a database corresponding to the server, and synchronizes the login information to other databases to ensure the consistency of multi-center user login information. After that, the client initiates an operation request carrying the login information, and the server compares the login information in the operation request with the login information stored in the database. If the two are consistent, it means that there is no situation where the user's account is used to log in to the target system multiple times. Otherwise, it means that there is a situation where the user's account is used to log in to the target system multiple times. Correspondingly, there is a risk of data leakage caused by multiple logins. At this time, terminating the user's login to the target system can eliminate the risk, thereby improving the security of the multi-center deployed target system.

[0059] like Figure 3 As shown, the embodiment of the present application also provides a login control method, which can be applied to Figure 1 In the client of each center shown, the method may include:

[0060] Step 301: After the user logs in to the target system through the client, the user's login information is sent to the server corresponding to the client, so that the server stores the login information in a first database, wherein the first database is a database deployed in a database cluster corresponding to the server, and the database cluster is configured to synchronize the information of each user in each database.

[0061] Step 302: initiate an operation request to the server, so that the server determines whether the login information of the user carried in the operation request is consistent with the login information of the user queried from the first database; if not, terminate the user's login to the target system.

[0062] Figure 3According to the method shown, after the user logs in to the target system through the client, the server will store the login information in the database of the center to which the server belongs, and will synchronize the login information to the databases of the remaining centers to ensure the consistency of the login information of the users in the multiple centers. After that, the client will initiate a polling request carrying the login information, and the server will compare the login information in the polling request with the login information stored in the database. If the two are consistent, it means that there is no situation where the user's account is used to log in to the target system at multiple points. Otherwise, it means that there is a situation where the user's account is used to log in to the target system at multiple points. Correspondingly, there is a risk of data leakage caused by multiple logins. At this time, terminating the user's login to the target system can eliminate the risk, thereby improving the security of the target system deployed in multiple centers.

[0063] Corresponding to the above method embodiment, the embodiment of the present application also provides a login control device, which is introduced below.

[0064] like Figure 4 As shown, a login control device 400 provided in an embodiment of the present application can be applied to Figure 1 In any of the central servers shown, the device may include: an information storage module 401 , an operation request receiving module 402 , a judgment module 403 and a login control module 404 .

[0065] The information storage module 401 is used to obtain the user's login information and store it in the first database after the user logs in to the target system through this server, wherein the first database is a database deployed in the database cluster corresponding to this server, and the database cluster is configured to synchronize the information of each user in each database.

[0066] The user can log in to the target system by using an account and password. After receiving the login request, the server of the target system can authenticate the user using the preset authentication rules. After the authentication is passed, the user is allowed to log in to the target system. Accordingly, the user successfully logs in to the target system. After the user logs in to the target system through this server, the user's login information is obtained and stored in the first database, and the user login information stored in the first database is synchronized to other databases.

[0067] The database master-slave synchronization mechanism can realize the rapid synchronization of data in different databases. In addition, since the database is only written when the user logs in, the login control method provided in the embodiment of the present application can detect the risk of multiple logins of the target system by the same account in a very short time, generally within 5 seconds, so the speed of avoiding the risk of multiple logins can be improved.

[0068] The above login information may include but is not limited to the user identifier, the identifier of the target system and preset information, wherein the preset information is information that can uniquely identify the client, for example, the preset information may include at least one of the IP address used for this login, the session ID (session ID) of this login and the identifier information of the client. The user identifier may be a user name, such as an account number; when the target system is an application, the identifier of the target system may be an application identifier, such as an application name or an application ID; the client identifier may be a client MAC address or an International Mobile Equipment Identity (IMEI), etc.

[0069] The operation request receiving module 402 is used to receive an operation request from a target user and query the login information of the target user from the first database.

[0070] The above operation request may be any operation of the target user on the target system. As an example, the operation request may be a polling request. Specifically, after the user successfully logs in to the target system through the client, the client may send a polling request to the server at a set time interval. The polling request may carry the login information of the user logging in to the target system through the client.

[0071] In one implementation, if the user's login information includes a user identifier, the operation request receiving module 402 may be used to query the target user's login information from the first database using the user identifier in the login information carried by the operation request. It is understood that the first database may store the user's login information in correspondence with the user identifier, so after the target user's user identifier is known, the target user's login information may be queried accordingly.

[0072] In another embodiment, if the user's login information includes a user identifier and an identifier of the target system, the operation request receiving module 402 may be used to query the login information of the target user from the first database using the user identifier and the identifier of the target system in the login information carried by the operation request. It is understood that, in the case where user login information of multiple target systems is stored in the first database, the login information of the target user may be queried from the first database according to the user identifier of the target user and the identifier of the target system.

[0073] Optionally, a center can set up a unified gateway (designated gateway), and when querying the database in the database, the query can be made through the unified gateway. The advantage of doing so is that for different target systems (in some business ecosystems, users can use the same account to log in to multiple systems under the ecosystem), the purpose of obtaining the data stored in the database can be achieved by introducing the jar package of the gateway, and the cost of modifying the target system is low. Accordingly, the operation request receiving module 402 can be used to: query the login information of the target user from the first database through the designated gateway.

[0074] The judgment module 403 is used to judge whether the queried login information is consistent with the login information carried in the operation request; if not, the login control module 404 is triggered; if consistent, the operation request receiving module 402 is triggered.

[0075] As an example, when the user's login information includes preset information, and the preset information includes at least one of the IP address used for this login, the session ID for this login, and the identification information of the client used for this login, the judgment module 403 can be used to determine whether the preset information in the queried login information is consistent with the preset information in the login information carried by the operation request.

[0076] The login control module 404 is used to end the user's login to the target system.

[0077] Specifically, the login control module 404 may be used to destroy the current login session and return a page for logging into the target system to the client to remind the user to log in again.

[0078] Optionally, Figure 4 The device shown may also include: a reminder module, used to send a prompt message to the client when the queried login information is inconsistent with the login information carried by the operation request, wherein the prompt message is used to remind the user that the account used to log in to the target system has been logged in elsewhere, and / or remind the user whether your account has been stolen, please reset the password, etc., to protect the user's account security and avoid data leakage.

[0079] It can be understood that if the queried login information is consistent with the login information carried by the operation request, it means that there is no situation where the user's account is used to log in to the target system multiple times, and polling can continue. Otherwise, it means that there is a situation where the user's account is used to log in to the target system multiple times. Correspondingly, there is a risk of data leakage caused by multiple logins. The previous login can be forced to exit to avoid this risk.

[0080] A login control device is provided in an embodiment of the present application. After a user logs in to a target system, the server will store the login information in a database corresponding to the server, and will synchronize the login information to other databases to ensure the consistency of multi-center user login information. After that, the client will initiate an operation request carrying the login information, and the server will compare the login information in the operation request with the login information stored in the database. If the two are consistent, it means that there is no situation where the user's account is used to log in to the target system multiple times. Otherwise, it means that there is a situation where the user's account is used to log in to the target system multiple times. Correspondingly, there is a risk of data leakage caused by multiple logins. At this time, terminating the user's login to the target system can eliminate the risk, thereby improving the security of the multi-center deployed target system.

[0081] like Figure 5 As shown, the present application also provides a login control device 500, which can be applied to Figure 1 In the client of each center shown, the device may include: an information sending module 501 and an operation request sending module 502.

[0082] The information sending module 501 is used to send the user's login information to the server corresponding to the client after the user logs in to the target system through the client, so that the server stores the login information in the first database, wherein the first database is a database deployed in the database cluster corresponding to this server, and the database cluster is configured to synchronize the information of each user in each database.

[0083] The operation request sending module 502 is used to initiate an operation request to the server, so that the server determines whether the login information of the user carried in the operation request is consistent with the login information of the user queried from the first database. If they are inconsistent, the user's login to the target system is terminated.

[0084] Figure 5 The device shown is used to implement Figure 3 The method shown can obtain Figure 3 The same technical effect as the method shown is not repeated here.

[0085] It should be noted that since the content executed by the device embodiment is similar to that of the method embodiment, the description of the device embodiment part in this document is relatively brief, and please refer to the method embodiment part for relevant details.

[0086] Figure 6 FIG. 1 is a schematic diagram of the structure of an electronic device provided by an embodiment of the present application. Figure 6At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. The memory may include a memory, such as a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage. Of course, the electronic device may also include hardware required for other services.

[0087] The processor, network interface and memory can be interconnected through an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0088] The memory is used to store the program. Specifically, the program may include a program code, and the program code includes a computer operation instruction. The memory may include a memory and a non-volatile memory, and provides instructions and data to the processor.

[0089] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a login control device at the logical level. The processor executes the program stored in the memory and is specifically used to execute the login control method provided in the embodiment of the present application.

[0090] The above application Figure 2 or Figure 3The method performed by the login control device disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware decoding processor for execution, or a combination of hardware and software modules in the decoding processor for execution. The software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0091] The present application also provides a computer-readable storage medium, which stores one or more programs, wherein the one or more programs include instructions, which, when executed by an electronic device including multiple application programs, enable the electronic device to execute Figure 2 or Figure 3 The method executed by the login control device in the illustrated embodiment is specifically used to execute the login control method provided in the embodiment of the present application.

[0092] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0093] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0094] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0095] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0096] It should be noted that the various embodiments in this application are described in a related manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0097] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0098] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A login control method, It is characterized in that Applied to a server, the method comprises: After the user logs in to the target system through the server, the user's login information is obtained and stored in the first database, wherein the first database is a database deployed in the database cluster corresponding to the server, and the database cluster is configured to synchronize the information of each user in each database; receiving an operation request from a target user, and querying the login information of the target user from the first database; Determine whether the queried login information is consistent with the login information carried in the operation request; If they are inconsistent, the target user's login to the target system is terminated.

2. The method according to claim 1, It is characterized in that The synchronization is achieved based on a database master-slave synchronization mechanism.

3. The method according to claim 1, It is characterized in that The user's login information includes a user identifier, wherein the step of querying the target user's login information from the first database includes: The login information of the target user is queried from the first database using the user identifier in the login information carried in the operation request.

4. The method according to claim 1, It is characterized in that The user's login information includes a user ID and an ID of the target system, wherein querying the login information of the target user from the first database includes: The login information of the target user is queried from the first database using the user identifier in the login information carried in the operation request and the identifier of the target system.

5. The method according to claim 1, It is characterized in that The user's login information includes preset information, and the preset information includes at least one of an IP address used for this login, a session ID for this login, and identification information of a client used for this login, wherein the determining whether the queried login information is consistent with the login information carried by the operation request includes: It is determined whether the preset information in the queried login information is consistent with the preset information in the login information carried in the operation request.

6. The method according to claim 1, It is characterized in that The querying the login information of the target user from the first database includes: The login information of the target user is queried from the first database through a designated gateway.

7. The method according to claim 1, It is characterized in that The step of ending the target user's login to the target system includes: The current login session is destroyed, and the page for logging into the target system is returned to the target user.

8. A login control method, It is characterized in that Applied to a client, the method comprises: After the user logs in to the target system through the client, the user's login information is sent to the server corresponding to the client, so that the server stores the login information in a first database, wherein the first database is a database deployed in a database cluster corresponding to the server, and the database cluster is configured to synchronize the information of each user in each database; An operation request is initiated to the server so that the server determines whether the login information of the user carried in the operation request is consistent with the login information of the user queried from the first database. If not, the user's login to the target system is terminated.

9. A login control device, It is characterized in that Applied to a server, the device comprises: An information storage module, used to obtain the login information of the user and store it in a first database after the user logs in to the target system through the server, wherein the first database is a database deployed in the database cluster corresponding to the server, and the database cluster is configured to synchronize the information of each user in each database; An operation request receiving module, used to receive an operation request from a target user, and query the login information of the target user from the first database; A judgment module, used to judge whether the queried login information is consistent with the login information carried in the operation request, and if not, trigger the login control module; The login control module is used to terminate the target user's login to the target system.

10. A login control device, It is characterized in that Applied to a client, the device comprises: An information sending module, configured to send the user's login information to a server corresponding to the client after the user logs in to the target system through the client, so that the server stores the login information in a first database, wherein the first database is a database deployed in a database cluster corresponding to the server, and the database cluster is configured to synchronize the information of each user in each database; An operation request sending module is used to initiate an operation request to the server, so that the server determines whether the login information of the user carried in the operation request is consistent with the login information of the user queried from the first database. If not, the user's login to the target system is terminated.

Images