CN114567475A - Multi-system login method and device, electronic equipment and storage medium - Google Patents

Abstract

The embodiment of the application discloses a multi-system login method and device, electronic equipment and a storage medium. The method may comprise the steps of: receiving a login operation of a user; sending a request authentication to a target management system, wherein the target management system is determined according to login operation and comprises a local management system and a third-party management system; judging whether the target management system passes the request authentication; under the condition that the target management system passes the request authentication, a Code returned by the target management system is obtained; sending the Code to a gateway service module to acquire a Token returned by the gateway service module; and acquiring a subsystem list according to Token. By implementing the embodiment of the application, the multi-system is logged in a plurality of modes, so that the disaster tolerance of the multi-system login can be improved.

Description

Method, device, electronic device and storage medium for multi-system login

technical field

The embodiments of the present application relate to the field of computer technologies, and in particular, to a method, apparatus, electronic device, and storage medium for multi-system login.

Background technique

With the development of computer technology, more and more business can be realized and completed through computer equipment. For different businesses, it is usually necessary to log in to their respective business systems to perform corresponding operations. The system login, authentication and authentication methods of each business system are usually performed independently by each system. In this way, multiple business systems require their own account and password to log in, which leads to cumbersome operations and low efficiency. In order to avoid this situation, in the prior art, a third-party management system is often introduced to perform unified management of multiple systems. That is to say, after the user logs in to the third-party management system using the account password, it is equivalent to logging in to all the business systems that are connected to the third-party management system, that is, the subsystem. In this way, the operation of logging in to multiple systems can be reduced, and the efficiency of logging in is improved. However, this has led to new problems. If the third-party management system fails, all business systems will not be able to log in and use normally. Therefore, improving the disaster tolerance of multi-system login is a problem that needs to be solved.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a method, apparatus, electronic device, and storage medium for multi-system login, which can improve the disaster tolerance of multi-system login.

In a first aspect, an embodiment of the present application provides a method for logging in to multiple systems, and the method includes the following steps:

Receive the user's login operation;

Sending a request for authentication to a target management system, the target management system is determined according to the login operation, and the target management system includes a local management system and a third-party management system;

Judging whether the target management system passes the request authentication;

When the target management system passes the request authentication, obtain the Code code returned by the target management system;

Send the Code to the gateway service module to obtain the Token returned by the gateway service module;

Obtain the subsystem list according to the Token.

In a first aspect, an embodiment of the present application provides an apparatus for logging in to multiple systems, and the apparatus includes:

a communication module for receiving a user's login operation; sending a request for authentication to a target management system, the target management system is determined according to the login operation, and the target management system includes a local management system and a third-party management system;

a processing module for judging whether the target management system passes the request authentication;

The communication module is further configured to obtain the code code returned by the target management system when the target management system passes the request authentication; send the code code to the gateway service module to obtain the return code from the gateway service module Token; obtain the subsystem list according to the Token.

In a third aspect, an embodiment of the present application provides an electronic device, including a processor and a memory, wherein the processor and the memory are connected to each other, wherein the memory is used to store a computer program, and the computer program includes program instructions, the The processor is configured to invoke the program instructions to perform the method of the first aspect.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program includes program instructions, and the program instructions are executed by a processor. When executed, the processor is caused to perform the method of the first aspect.

Implementing the embodiments of the present application will have the following beneficial effects:

Using the above-mentioned multi-system login method, device, computer equipment and storage medium, after receiving the user's login operation, a request for authentication is sent to the target management system according to the user's login operation, wherein the target management system is determined according to the user's login operation. Target management systems include local management systems and third-party management systems. Then, it is judged whether the target management system has passed the request authentication. In the case that the target management system passes the request authentication, obtain the Code code returned by the target management system. Then send the code to the gateway service module to obtain the Token returned by the gateway service module. Then obtain the subsystem list according to the Token. In this way, it is possible to log in to multiple systems through different target management systems in a variety of ways, thereby improving the disaster tolerance of multi-system login.

Description of drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the accompanying drawings that are required to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the present application, and for those of ordinary skill in the art, other drawings can also be obtained based on these drawings without creative effort. in:

FIG. 1 is a schematic diagram of a system architecture provided by an embodiment of the present application;

2 is a schematic flowchart of a method for logging in to multiple systems provided by an embodiment of the present application;

3 is a schematic diagram of a login interface provided by an embodiment of the present application;

4 is a schematic structural diagram of a device for multi-system login provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of the composition of an electronic device according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are 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 those of ordinary skill in the art without creative work fall within the protection scope of the present application.

The terms "first", "second", "third" and "fourth" in the description and claims of the present application and the drawings are used to distinguish different objects, rather than to describe a specific order . Furthermore, the terms "comprising" and "having", and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes unlisted steps or units, or optionally also includes For other steps or units inherent to these processes, methods, products or devices.

Reference herein to an "embodiment" means that a particular feature, result, or characteristic described in connection with the embodiment can be included in at least one embodiment of the present application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor a separate or alternative embodiment that is mutually exclusive of other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

First, the technical terms and concepts involved in the embodiments of the present application are introduced.

(1)Token

Token is a string of strings generated by the server as a token for requesting the client (electronic device). A token is a special frame that controls the station's possession of the media, distinguishing data frames from other control frames. That is to say, Token can be understood as a secret code. Before some data is transmitted, the secret code must be checked first, and different secret codes are authorized for different data operations.

(2)Code

Code is the user credential obtained by user authorization, which is used by the server to exchange the resource access credential (Token).

(3) Spring security

Spring Security is a security framework that can provide declarative security access control solutions for Spring-based enterprise application systems. It provides a set of beans that can be configured in the Spring application context, making full use of Spring IoC, DI (Inversion of Control, DI: Dependency Injection) and AOP (Aspect Oriented Programming) functions to provide application systems with Declarative security access control capabilities reduce the effort of writing a lot of repetitive code for enterprise system security controls.

(4) Symmetric encryption

Symmetric encryption refers to an encryption method using a single-key cryptosystem, and the same key can be used for both encryption and decryption of information, also known as single-key encryption. A key is an instruction that controls the encryption and decryption process. An algorithm is a set of rules that dictate how encryption and decryption are performed.

The working process is as follows: the data sender processes the plaintext (original data) and the encryption key together with a special encryption algorithm, and then turns it into a complex encrypted ciphertext and sends it out. After the receiver receives the ciphertext, if he wants to interpret the original text, he needs to use the encryption key and the inverse algorithm of the same algorithm (that is, the special encryption algorithm above) to decrypt the ciphertext to restore it to readable plaintext.

(5) Asymmetric encryption

Asymmetric encryption algorithms require two keys for encryption and decryption. These two keys are public keys, referred to as public keys, and private keys, referred to as private keys. The public key and the private key are a pair. If the data is encrypted with the public key, only the corresponding private key can be used to decrypt it; if the data is encrypted with the private key, only the corresponding public key can be used to decrypt the data. decrypt.

The working process is as follows: Party B generates a pair of keys (public key and private key), and discloses the public key to other parties. Party A who has obtained the public key uses the public key to encrypt the confidential information before sending it to Party B. Party B then decrypts the encrypted information with another private key (private key) kept by itself. Party B can only use its private key (private key) to decrypt the information encrypted by the corresponding public key.

(6)MD5

MD5 Message-Digest Algorithm, a widely used cryptographic hash function, can generate a 128-bit (16-byte) hash value to ensure complete and consistent information transmission .

In order to better understand the technical solutions of the embodiments of the present application, the system architectures that may be involved in the embodiments of the present application are introduced here. Please refer to FIG. 1 , which is a schematic diagram of a system architecture provided by an embodiment of the present application. The system architecture may include: an electronic device 101 and a server 102 . Wherein, the electronic device 101 and the server 102 can communicate through a network. Network communications may be based on any wired and wireless network, including but not limited to the Internet, wide area networks, metropolitan area networks, local area networks, virtual private networks (VPNs), wireless communication networks, and the like.

The embodiments of the present application do not limit the number of electronic devices and servers, and the server can provide services for multiple electronic devices at the same time. In this embodiment of the present application, the electronic device is mainly a device used by a user to perform multi-system login, and can be used to communicate with a server to obtain a list of subsystems to complete multi-system login. The electronic device may be a personal computer (PC), a notebook computer, or a smart phone, and may also be an all-in-one computer, a palmtop computer, a tablet computer (pad), a smart TV player terminal, a vehicle-mounted terminal, or a portable device. Electronic equipment on the PC side, such as an all-in-one computer, etc., its operating system may include but not limited to Linux system, Unix system, Windows series system (such as Windows xp, Windows7, etc.), Mac OS X system (Apple Computer's operating system) and other operating systems . The operating system of a mobile electronic device, such as a smart phone, may include, but is not limited to, an Android system, an IOS (an operating system of an Apple mobile phone), a Windows system, and other operating systems.

The server can be an independent server, or can provide cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery network (CDN) ), as well as cloud servers for basic cloud computing services such as big data and artificial intelligence platforms. The server or can be implemented by a server cluster composed of multiple servers.

With the development of computer technology, more and more business can be realized and completed through computer equipment. For different businesses, it is usually necessary to log in to their respective business systems to perform corresponding operations. The system login, authentication and authentication methods of each business system are usually performed independently by each system. In this way, multiple business systems require their own account and password to log in, which leads to cumbersome operations and low efficiency. In order to avoid this situation, in the prior art, a third-party management system is often introduced to perform unified management of multiple systems. That is to say, after the user logs in to the third-party management system with the account and password, it is equivalent to logging in to all business systems connected to the third-party management system. In this way, the operation of logging in to multiple systems can be reduced, and the efficiency of logging in is improved. However, this has led to new problems. If the third-party management system fails, all business systems will not be able to log in and use normally. Therefore, improving the disaster tolerance of multi-system login is a problem that needs to be solved.

In order to solve the above problem, an embodiment of the present application provides a multi-system login method, which can be applied to an electronic device or a server as shown in FIG. 1 . By implementing this method, the disaster tolerance of multi-system login can be improved.

The embodiments of the present application are implemented based on a common support platform (Common Service Platform, CSP). CSP is a service platform that supports upper-layer applications, including gateway service module, SDK module and user management system. Among them, the gateway service module is responsible for authorization and authentication. The SDK module refers to the SDK package that can be referenced by each subsystem (application system). Each application is authorized by the interceptor in Spring Security. At the same time, each subsystem can obtain the menu list information owned by the current user through this module. User management system, used for user login management, authority management, etc.

Please refer to FIG. 2 , which is a schematic flowchart of a multi-system login method provided by an embodiment of the present application. The following steps S201-S206 may be included. in:

Step S201: Receive a user's login operation.

Step S202: Send a request for authentication to the target management system, and the target management system determines according to the login operation.

Requesting authentication refers to requesting authentication of the user's identity, and determining whether the user has operation rights and what operation rights it has according to the user's identity.

In a possible implementation manner, the login operation includes a first login operation, the target management system is determined according to the user's first login operation, and the target management system includes a local management system and a third-party management system. The local management system is the user management system in the CSP, and the third-party management system is other user management systems except the user management system in the CSP. As shown in FIG. 3 , a schematic diagram of a login interface provided by an embodiment of the present application is shown. Button 301 indicates logging in using a third-party management system, and button 302 indicates logging in using a local management system. The user can quickly select the third-party management system to log in or the local management system by clicking the button 301 or the button 302 to perform this login. It can be understood that, in FIG. 3 , the user's first login operation is to click the button 301 or the button 302 . When the user clicks the button 301 and chooses to log in using the third-party management system, the target management system is the third-party management system; when the user clicks the button 302 and chooses to log in using the local management system, the target management system is the local management system. By allowing users to click a button on an interface to select a local management system or a third-party management system to log in, users can log in without having to remember and input the addresses of each system, simplifying user operations and improving user experience. Spend.

In a possible implementation manner, the login operation includes a second login operation, the second login operation is used to determine a login mode, and the login mode includes a first login mode and a second login mode. As shown in FIG. 3 , the first login method refers to the login method of inputting an account password as shown in 304 to log in, and the second login method refers to the login method of scan code login as shown in 303 . In the case where the user logs in using the first login method, as shown in 304, when the user enters the account number and password and clicks the login button, the user's login operation will be received, and a request for authentication will be sent to the target management system at this time. . In the case where the user logs in using the second login method, as shown in 303, when the user scans the code with another device and clicks the button for prompting the user to confirm the login, the user's login operation will be received. A request for authentication will be sent to the target management system.

Step S203: Determine whether the target management system has passed the request authentication.

In a possible implementation, when the login mode is the first login mode, judging whether the target management system passes the request authentication may include the following steps A1-A6:

Step A1. Acquire a first input account and a first input password according to the first login method.

It should be noted that the first input account and the first input password are not the account and password input by the user, but refer to the account and password after the account and password input by the user are encrypted once. This is because if the front-end is transmitted in clear text, the account and password will be at risk of leakage. Therefore, the front end encrypts the account and password during transmission. Therefore, what is obtained is the encrypted first input account number and the first input password, not the account number and password input by the user. The encryption processing method can be symmetric encryption or asymmetric encryption. The way of encrypting the account and password can be the same or different. For example, the account number input by the user may be encrypted by using a symmetric encryption process, and the password input by the user may be encrypted by asymmetric encryption process.

Step A2. Send the first input account and the first input password to the Springsecurity framework, and the Springsecurity framework is used to decrypt the first input account to obtain the original input account and encrypt the first input password to obtain the second input password.

Wherein, the original input account is the account input by the user, and the second input password is not the password input by the user, but a password after secondary encryption of the password input by the user (the first encryption occurs in the above-mentioned front-end transmission Time).

Step A3. Obtain the original account number and encrypted password in the database.

It should be noted that, in order to ensure data security, the original account number and encrypted password are stored in the database. The original account refers to the account generated when the user registers or set by the user. The encrypted password is not a password set by the user, but a password that is encrypted twice for the password set by the user.

In a possible implementation manner, the encrypted password is obtained through the MD5 algorithm. When we need to save some password information for identity confirmation, if the password information is directly stored in the database in clear code without any confidentiality measures, the system administrator can easily obtain the original password information. Leaked, the password is also easily deciphered. In order to increase security, it is necessary to encrypt the information that needs to be kept secret in the database, so that even if someone gets the whole database, if there is no decryption algorithm, the original password information cannot be obtained. The MD5 algorithm can solve this problem very well, because it can calculate the input string of any length to obtain a fixed-length output, and only when the plaintext is the same, can it wait for the same ciphertext, and this algorithm is irreversible, Even if the encrypted ciphertext is obtained, it is impossible to calculate the plaintext through the decryption algorithm. In this way, the user's password can be saved in the form of MD5 value (or similar other algorithms). When the user registers, the system calculates the password entered by the user into an MD5 value, and then goes to the MD5 value saved in the system. By comparison, if the ciphertexts are the same, it can be determined that the password is correct, otherwise the password is wrong. Through such steps, the system can determine the legitimacy of the user's login to the system without knowing the clear code of the user's password. This not only prevents the user's password from being known by users with system administrator rights, but also increases the difficulty of password cracking to a certain extent.

Step A4. Encrypt the original account to obtain an encrypted account.

An encrypted account is an account that has been encrypted once for the original account.

Step A5. Send the encrypted account number and the encrypted password to the Springsecurity framework, and the Springsecurity framework is used to decrypt the encrypted account number to obtain the original account number, and to obtain the original input account number and the original account number, the second input password and The verification result of the encrypted password.

The verification result refers to whether the original input account and the original account are successfully matched, and whether the second input password and the encrypted password are successfully matched. If the original input account and the original account are successfully matched, and the second input password is successfully matched with the encrypted password, the verification result is that the matching is successful. Otherwise, the verification result is that the matching is unsuccessful.

Step A6. Determine whether the request authentication is passed according to the verification result.

If the verification result is that the matching is successful, it is determined that the request authentication is passed. If the verification result is that the matching is unsuccessful, it is determined that the request authentication is not passed.

Exemplarily, on the one hand, the account entered by the user is A, and the password is B. The acquired account transmitted by the front end is A1 (account A1 is the result of encrypting account A once), and the password is B1 (password B1 is the result of encrypting password B once). Then pass the account A1 and password B1 into the SpringSecurity framework. The SpringSecurity framework decrypts account A1 to obtain account A again, and encrypts password B1 again to obtain B2 (password B2 is equivalent to the result of secondary encryption of password B). On the other hand, the account stored in the database corresponding to the account A input by the user is a and the password is b2. Before entering Spring Security, the account a is encrypted to obtain the account a1, and the password b2 is not processed. After passing the account a1 and password b2 into the SpringSecurity framework, the SpringSecurity framework decrypts the account a1 to obtain the account a, and then judges whether the account A matches the account a, and whether the password B2 matches the password b2. If the account A matches the account a, and the password B2 matches the password b2, the obtained verification result is that the matching is successful, so that the request is authenticated. In the case that the account A does not match the account a, or the password B2 does not match the password b2, the obtained verification result is that the matching is unsuccessful, so that the request authentication is not passed.

In a possible implementation, when the login mode is the second login mode, judging whether the target management system passes the request authentication may include the following steps B1-B7:

Step B1. Acquire the Code code according to the second login method.

The code code is generated by the third-party management system when the code is scanned successfully. The code code generated by each code scan may be different, but there is a mapping relationship between the code code and the user. Therefore, the corresponding user who scans the code can be determined in the third-party management system according to the code code.

Step B2. Send the Code to a third-party management system to obtain corresponding user information.

The gateway service module sends the code code to the third-party management system, and the third-party management system can query the user information in the third-party management system of the corresponding user according to the code code.

Step B3. Obtain the first account number and the first password in the database according to the user information query.

After acquiring the user information in the third-party management system from the third-party management system, the gateway service module queries the local management system according to the user information in the third-party management system to obtain the user information in the user's local management system. The first account number and the first password are obtained by querying the database according to the user information in the user's local management system.

It should be noted that, since the account number and password in the database cannot be obtained directly through the user information in the third-party management system, the account number and password in the database need to be obtained indirectly by using the local management system as a medium. Therefore, the user information in the third-party management system should have some or all of the corresponding user information in the local management system. That is, the local management system needs to add some or all of the user information of the user in the third-party management system, so that the corresponding user information in the local management system can be queried according to the user information in the third-party management system.

In a possible implementation, when the third-party management system cannot directly provide user information to the local management system for adding user information, that is to say, the third-party management system cannot provide user information of the third-party management system through the interface , you can obtain the user feature information provided by the user, that is, the user information that can be used to identify the unique user, use the user feature information to query the third-party management system to obtain other information of the user, and then use the user feature information to query the third-party management system. Fill in the information of the user in the local management system and save it. By acquiring user feature information and automatically filling in other user information according to the user feature information, user operations can be reduced and user experience can be improved.

In a possible implementation manner, in the case that a third party can provide user information in the third-party management system, part or all of the user information provided by the third-party management system is obtained according to a preset parameter configuration, (for example, a third-party management system The management system includes the user information of the entire organization of group A. The group A includes organization A1, organization A2, organization A3, and organization A4. Each organization contains the user information of users under its own organization, but only the organization is related to the local management system. A1, therefore, the local management system can be pre-configured with parameters to acquire only the user information included in the organization A1), and the acquired user information in the third-party management system can be added to the local management system. Among them, the user information is encrypted, which can improve information security.

Step B4. Send the first account and the first password to the Springsecurity framework.

In a possible implementation manner, the first account is encrypted before the first account is sent to the Springsecurity framework, and then the Springsecurity framework decrypts the encrypted first account after receiving it to obtain the first account again.

Step B5. Obtain the second account number and the second password in the database.

It can be understood that the second account number and the second password in the database are obtained according to user information in the local management system.

Step B6. Send the second account and the second password to the Springsecurity framework.

In a possible implementation manner, the second account is encrypted before the second account is sent to the Springsecurity framework, and then the Springsecurity framework decrypts the encrypted second account after receiving it to obtain the second account again.

The Springsecurity framework is used to obtain the verification results of the first account and the second account, and the first password and the second password. The verification result refers to whether the first account and the second account are successfully matched, and whether the first password and the second password are successfully matched. If the first account and the second account are successfully matched, and the first password and the second password are successfully matched, the verification result is that the matching is successful. Otherwise, the verification result is that the matching is unsuccessful.

Step B7. Determine whether the request authentication is passed according to the verification result.

If the verification result is that the matching is successful, it is determined that the request authentication is passed. If the verification result is that the matching is unsuccessful, it is determined that the request authentication is not passed.

It is understandable that the account and password are retrieved from the database for matching both times, so the matching is usually successful. This match is equivalent to the process of simulating login.

Step S204: in the case that the target management system passes the request authentication, obtain the Code code returned by the target management system.

That is to say, the Code code is generated by the target management system.

Step S205: Send the Code to the gateway service module to obtain the Token returned by the gateway service module.

The validity period of the Code code is shorter than that of the Token. The code code is used to obtain the Token, and the Token is used to determine the user's identity, thereby determining the operation authority that the user has.

In a possible implementation manner, the gateway service module used when logging in with the local management system or logging in with the third-party management system is the same gateway service module, that is, the gateway service module in the CSP, so that server resources can be saved. In the gateway service module, the differentiated processing of logging in using the local management system and logging in using a third-party management system is determined by the characteristic data "redirectType". That is to say, according to the selected target management system, the data carried when obtaining the Token is also different. If the local management system is used to log in, the data carried when obtaining the Token includes the Code code and the characteristic data "redirectType"; if the third-party management system is used for logging in, the data carried when obtaining the Token includes the Code code, but The feature data "redirectType" is not included. The differentiated processing of logging in using the local management system and logging in using a third-party management system in the gateway service module may be embodied in the following steps C1-C2 and D1-D2. Wherein, steps C1-step C2 are processing methods when the target management system is a local management system, and steps D1-step D2 are processing methods when the target management system is a third-party management system.

In a possible implementation manner, in the case that the target management system is the local management system, sending the Code to the gateway service module to obtain the Token returned by the gateway service module includes step C1-step C2:

Step C1: Send the code to the gateway service module, and the gateway service module is used for sending the code to the local management system.

Step C2: Receive the Token sent by the gateway service module, and the Token is sent by the local management system to the gateway service module.

It can be understood that since the local management system and the gateway service module both belong to the CSP, when the target management system is the local management system, the role of the gateway service module at this time is to forward code codes.

In a possible implementation, when the target management system is a third-party management system, sending the Code code to the gateway service module to obtain the Token returned by the gateway service module includes steps D1-step D2:

Step D1: Send the code code to the gateway service module, the gateway service module is used for sending the code code to the third-party management system, and the third-party management system is used for returning corresponding user information to the gateway service module according to the received code code.

That is to say, after receiving the code, the gateway service module uses the code to obtain the user information in the third-party management system of the user corresponding to the code from the third-party management system.

Step D2: Receive the Token sent by the gateway service module, and the Token is generated by the gateway service module according to the received user information.

Specifically, after acquiring the user information in the user's third-party management system, the gateway service module searches the local management system according to the user information in the user's third-party management system and acquires the local management system corresponding to the user user information. Then, a Token is generated according to the obtained user information in the local management system.

Step S206: Acquire a list of subsystems according to the Token.

Among them, the subsystem refers to each application system integrated with the SDK.

In a possible implementation manner, the method of obtaining the list of subsystems according to the Token is: sending a request for obtaining the list of subsystems to the gateway service module, and the gateway service module checks the validity of the Token after receiving the request. After success, the gateway service module accesses the subsystem to obtain the menu, and the SDK module on the subsystem determines the authority of the current user according to the Token, thereby returning the list of subsystems owned by the current user and the menu list of each subsystem in the subsystem list. Thus, a method for logging in to multiple systems in multiple ways is realized.

The methods involved in the embodiments of the present application are described in detail above, and the devices involved in the embodiments of the present application are introduced below.

Referring to FIG. 4 , FIG. 4 is a schematic structural diagram of an apparatus for multi-system login provided by an embodiment of the present application. As shown in FIG. 4, the apparatus 400 for multi-system login includes:

The communication module 401 is used for receiving a user's login operation; for sending a request for authentication to a target management system, the target management system determines according to the login operation;

A processing module 402, configured to judge whether the target management system passes the request authentication;

The communication module 401 is further configured to obtain the code code returned by the target management system when the target management system passes the request authentication; send the code code to the gateway service module to obtain the code returned by the gateway service module Token; obtain the subsystem list according to the Token.

In a possible implementation manner, the login operation includes a first login operation, the target management system is determined according to the first login operation, and the target management system includes a local management system and a third-party management system.

In a possible implementation manner, the login operation includes a second login operation, the second login operation is used to determine a login mode, and the login mode includes a first login mode and a second login mode.

In a possible implementation manner, the communication module 401 is specifically configured to: send the code to a gateway service module, and the gateway service module is configured to send the code to the local management system; receive the gateway The Token sent by the service module, the Token is sent by the local management system to the gateway service module.

In a possible implementation manner, the communication module 401 is specifically configured to send the code to a gateway service module, and the gateway service module is configured to send the code to the third-party management system, and the third-party The management system is used to return the corresponding user information to the gateway service module according to the received code; receive the Token sent by the gateway service module, and the Token is sent by the gateway service module according to the received user information. information generation.

In a possible implementation manner, the communication module 401 is specifically configured to obtain the first input account and the first input password according to the first login method; send the first input account and the first input password to the Springsecurity framework , the Spring security framework is used to decrypt the first input account to obtain the original input account and encrypt the first input password to obtain the second input password; obtain the original account and encrypted password in the database. The processing module 402 is specifically configured to encrypt the original account to obtain an encrypted account. The communication module 401 is further configured to send the encrypted account and the encrypted password to the Springsecurity framework, and the Springsecurity framework is used to decrypt the encrypted account to obtain the original account, and to obtain the original input account and the original account. The verification result of the account number, the second input password and the encrypted password. The processing module is further configured to determine whether to pass the request authentication according to the verification result.

In a possible implementation manner, the communication module 401 is configured to obtain the code code according to the second login method; send the code code to the third-party management system to obtain corresponding user information; according to the user information Query to obtain the first account number and the first password in the database; send the first account number and the first password to the Springsecurity framework; obtain the second account number and the second password in the database; send the second account number and the The second password is sent to the Springsecurity framework; the Springsecurity framework is used to obtain the verification results of the first account and the second account, the first password and the second password. The processing module 402 is configured to determine whether to pass the request authentication according to the verification result.

For the specific function implementation of the apparatus 400 for multi-system login, please refer to the method steps corresponding to FIG. 2 , which will not be repeated here.

Please refer to FIG. 5 , which is a schematic diagram of the composition of an electronic device according to an embodiment of the present application. It may include: a processor 110 and a memory 120; wherein, the processor 110, the memory 120 and the communication interface 130 are connected through a bus 140, the memory 120 is used for storing instructions, and the processor 110 is used for executing the instructions stored in the memory 120, to The method steps corresponding to Figure 2 above are implemented.

The processor 110 is configured to execute the instructions stored in the memory 120 to control the communication interface 130 to receive and send signals, and to complete the steps in the above method. Wherein, the memory 120 may be integrated in the processor 110 , or may be provided separately from the processor 110 .

As an implementation manner, the function of the communication interface 130 may be implemented by a transceiver circuit or a dedicated chip for transceiver. The processor 110 can be considered to be implemented by a dedicated processing chip, a processing circuit, a processor or a general-purpose chip.

As another implementation manner, a general-purpose computer may be used to implement the computer device provided in the embodiments of the present application. The program codes that will implement the functions of the processor 110 and the communication interface 130 are stored in the memory 120 , and the general-purpose processor implements the functions of the processor 110 and the communication interface 130 by executing the codes in the memory 120 .

For the concepts related to the technical solutions provided by the embodiments of the present application, the explanations and detailed descriptions and other steps involved in the computer equipment, please refer to the description of the content of the method steps performed by the apparatus in the foregoing methods or other embodiments, which are not described here. Repeat.

As another implementation manner of this embodiment, a computer-readable storage medium is provided, on which an instruction is stored, and when the instruction is executed, the method in the foregoing method embodiment is performed.

As another implementation manner of this embodiment, a computer program product including an instruction is provided, and the method in the foregoing method embodiment is executed when the instruction is executed.

Those skilled in the art can understand that, for the convenience of description, only one memory and a processor are shown in FIG. 5 . In an actual electronic device or server, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, etc., which is not limited in this embodiment of the present application.

It should be understood that in this embodiment of the present application, the processor may be a central processing unit (Central Processing Unit, CPU for short), and the processor may also be other general-purpose processors, digital signal processors (Digital Signal Processing, DSP for short), dedicated integrated Circuit (Application Specific Integrated Circuit, ASIC for short), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA for short) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like.

It should also be understood that the memory mentioned in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory may be a read-only memory (Read-Only Memory, referred to as ROM), a programmable read-only memory (Programmable ROM, referred to as PROM), an erasable programmable read-only memory (Erasable PROM, referred to as EPROM) , Electrically Erasable Programmable Read-Only Memory (Electrically EPROM, EEPROM for short) or flash memory. The volatile memory may be a random access memory (Random Access Memory, RAM for short), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic RAM (DRAM), Synchronous DRAM, referred to as SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, referred to as DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, referred to as ESDRAM), synchronous connection dynamic random access memory (Synchlink DRAM, referred to as SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, referred to as DR RAM).

It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, the memory (storage module) is integrated in the processor.

It should be noted that the memory described herein is intended to include, but not be limited to, these and any other suitable types of memory.

In addition to the data bus, the bus may also include a power bus, a control bus, a status signal bus, and the like. However, for the sake of clarity, the various buses are labeled as buses in the figure.

It should also be understood that the first, second, third, fourth and various numeral numbers mentioned herein are only for the convenience of description, and are not used to limit the scope of the present application.

It should be understood that the term "and/or" in this document is only an association relationship to describe associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, and A and B exist at the same time , there are three cases of B alone. In addition, the character "/" in this document generally indicates that the related objects are an "or" relationship.

In the implementation process, each step of the above-mentioned method can be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software. The steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. 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. To avoid repetition, detailed description is omitted here.

In various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, rather than the implementation process of the embodiments of the present application. constitute any limitation.

Those of ordinary skill in the art can realize that various illustrative logical blocks (ILBs) and steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. accomplish. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line) or wireless (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media. The usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state drives), and the like.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims (10)

1. A method for multi-system login, the method comprising:

receiving login operation of a user;

sending a request authentication to a target management system, wherein the target management system is determined according to the login operation and comprises a local management system and a third-party management system;

judging whether the target management system passes the request authentication;

under the condition that the target management system passes the request authentication, a Code returned by the target management system is obtained;

sending the Code to a gateway service module to acquire a Token returned by the gateway service module;

and acquiring a subsystem list according to the Token.

2. The method according to claim 1, wherein the login operation includes a first login operation, the target management system determines according to the first login operation, and in a case that the target management system is the local management system, the sending the Code to a gateway service module to obtain the Token returned by the gateway service module includes:

sending the Code to a gateway service module, wherein the gateway service module is used for sending the Code to the local management system;

and receiving the Token sent by the gateway service module, wherein the Token is sent to the gateway service module by the local management system.

3. The method according to claim 1, wherein the login operation includes a first login operation, the target management system determines according to the first login operation, and in a case that the target management system is the third party management system, the sending the Code to a gateway service module to obtain the Token returned by the gateway service module includes:

sending the Code to a gateway service module, wherein the gateway service module is used for sending the Code to the third party management system, and the third party management system is used for returning corresponding user information to the gateway service module according to the received Code;

and receiving the Token sent by the gateway service module, wherein the Token is generated by the gateway service module according to the received user information.

4. The method according to claim 2 or 3, wherein the login operation comprises a second login operation, the second login operation is used for determining a login mode, the login mode comprises a first login mode, and the determining whether the target management system passes the request authentication comprises:

acquiring a first input account and a first input password according to the first login mode;

sending the first input account and the first input password to a Spring security framework, wherein the Spring security framework is used for decrypting the first input account to obtain an original input account and encrypting the first input password to obtain a second input password;

acquiring an original account and an encrypted password in a database;

encrypting the original account to obtain an encrypted account;

sending the encrypted account and the encrypted password to a Spring security framework, wherein the Spring security framework is used for decrypting the encrypted account to obtain the original account and obtaining verification results of the original input account and the original account as well as the second input password and the encrypted password;

and determining whether the request authentication is passed according to the verification result.

5. The method according to claim 2 or 3, wherein the login operation comprises a second login operation, the second login operation is used for determining login modes, the login modes comprise second login modes, and the determining whether the target management system passes the request authentication comprises:

acquiring a Code according to the second login mode;

sending the Code to the third-party management system to acquire corresponding user information;

inquiring to obtain a first account and a first password in a database according to the user information;

sending the first account and the first password to a Springsecurity framework;

acquiring a second account and a second password in the database;

sending the second account and the second password to the Springsecurity framework; the Springsecurity framework is used for obtaining verification results of the first account number and the second account number and the first password and the second password;

and determining whether the request authentication is passed or not according to the verification result.

6. The method of claim 1, further comprising:

acquiring user characteristic information, wherein the user characteristic information is used for identifying a unique user;

inquiring and acquiring other information of the user corresponding to the user characteristic information in the third-party management system according to the user characteristic information;

and storing other information of the user corresponding to the user characteristic information into the local management system.

7. The method of claim 1, further comprising:

acquiring user information of a third-party management system according to preset parameter configuration;

and adding the user information to the local management system.

8. An apparatus for multi-system login, the apparatus comprising:

the communication module is used for receiving login operation of a user; sending a request authentication to a target management system, wherein the target management system is determined according to the login operation and comprises a local management system and a third-party management system;

the processing module is used for judging whether the target management system passes the request authentication or not;

the communication module is further used for acquiring a Code returned by the target management system under the condition that the target management system passes the request authentication; sending the Code to a gateway service module to acquire a Token returned by the gateway service module; and acquiring a subsystem list according to the Token.

9. An electronic device, comprising a processor and a memory, the processor and the memory being interconnected, wherein the memory is configured to store a computer program comprising program instructions, the processor being configured to invoke the program instructions to perform the method of any one of claims 1-7.

10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions that, when executed by a processor, cause the processor to carry out the method according to any one of claims 1-7.

Images