WO2021027600A1

WO2021027600A1 - Single log-in method, apparatus and device, and computer-readable storage medium

Info

Publication number: WO2021027600A1
Application number: PCT/CN2020/106349
Authority: WO
Inventors: 罗鹏
Original assignee: 深圳前海微众银行股份有限公司
Priority date: 2019-08-09
Filing date: 2020-07-31
Publication date: 2021-02-18
Also published as: CN110430205A; CN110430205B

Abstract

Disclosed is a single log-in method. The method comprises: when it is detected that a service of an access party is started, acquiring Redis address information from a preset configuration center; when an operation request is received, determining, according to a network address of the operation request, whether the operation request is a login request; when it is determined that the operation request is a login request, acquiring user information corresponding to the login request, and logging in to an account corresponding to the user information; and when the account is successfully logged into, generating a session identifier, writing the session identifier into a Cookie, and writing the user information into a Redis server corresponding to the Redis address information.

Description

Single sign-on method, device, equipment and computer readable storage medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on August 9, 2019, the application number is 201910742748.1, and the invention title is "Single Sign-On Method, Device, Equipment, and Computer-readable Storage Medium", and its entire contents Incorporated in this application by reference.

Technical field

This application relates to the field of financial technology (Fintech) big data technology, in particular to single sign-on methods, devices, equipment, and computer-readable storage media.

Background technique

In recent years, with the rapid development of Internet technology, especially Internet financial technology (Fintech), more and more technologies (big data, distributed, blockchain, artificial intelligence, etc.) have been applied in the financial field. For example, they usually have multiple service platforms corresponding to multiple servers. When users access these service platforms, each service platform must register and log in, and when they log out, they have to log out one by one. User operations are more troublesome. Next, the enterprise forms a single sign-on system by complying with the single sign-on protocol on each business platform. Users only need to log in to one of the business platforms to access all mutually trusted business platforms.

The business platform (access party) corresponding to the existing single sign-on system needs to call Redis related methods to store and obtain user information by modifying the code. In the process of calling Redis related methods to store and obtain user information, the Redis interface will be exposed to On the access side, the Redis interface is at risk of being tampered with, and the stability and security of the single sign-on system is low.

Technical solutions

The main purpose of this application is to propose a single sign-on method, device, device, and computer-readable storage medium, aiming at the technical problem of low stability and security of the current single sign-on system.

In order to achieve the above objective, this application provides a single sign-on method, which includes the following steps:

When detecting that the access party service is started, obtain the Redis address information from the preset configuration center;

Upon receiving the operation request, determine whether the operation request is a login request according to the network address of the operation request;

Determining that the operation request is a login request, acquiring user information corresponding to the login request, and logging in to an account corresponding to the user information;

After it is determined that the account login is successful, a session identifier is generated, the session identifier is written into a Cookie, and the user information is written into the Redis server corresponding to the Redis address information.

In one embodiment, the step of "after determining that the account login is successful, generate a session identifier, write the session identifier into a Cookie, and write the user information into the Redis server corresponding to the Redis address information" ,include:

After determining that the account is successfully logged in, generate a session identifier through a preset interceptor, and write the session identifier into a Cookie;

The set method in the preset network interface is called to write the user information into the Redis server corresponding to the Redis address information.

In one embodiment, after the step of "determining whether the operation request is a login request according to the network address of the operation request after the operation request is determined to be received", the method includes:

After determining that the operation request is not a login request, obtain the session identifier corresponding to the operation request from the Cookie through the preset loading interface;

Query the Redis server corresponding to the Redis address information through the preset loading interface, and determine whether the user information corresponding to the session identifier exists in the Redis server;

It is determined that the user information corresponding to the session identifier exists in the Redis server, then accessing the access party interface to execute the operation request.

In one embodiment, the step of "after determining that the account login is successful, generate a session identifier, write the session identifier into a Cookie, and write the user information into the Redis server corresponding to the Redis address information" After that, include:

Setting the timeout period of the user information in the Redis server;

Detecting that the storage time of the user information reaches the timeout period, deleting the user information in the Redis server;

After the step of "querying the Redis server corresponding to the Redis address information through the preset loading interface, and judging whether the user information corresponding to the session identifier exists in the Redis server", the method further includes:

If it is determined that the user information corresponding to the session identifier does not exist in the Redis server, prompt information is output to prompt the user to log in again.

In one embodiment, the step of "determining that the operation request is a login request, then obtaining user information corresponding to the login request, and logging in to the account corresponding to the user information" includes:

Determining that the operation request is a login request, acquiring user information corresponding to the login request, and verifying the user information;

If it is determined that the user information verification fails, output a prompt message to prompt the user to input new user information;

If it is determined that the user information is verified, log in to the account corresponding to the user information.

In addition, in order to achieve the above-mentioned object, this application also provides a single sign-on device, which includes:

The address obtaining module is configured to detect that the access party service is started and obtain the Redis address information from the preset configuration center;

The request judgment module is configured to receive the operation request, and determine whether the operation request is a login request according to the network address of the operation request;

The account login module is configured to, after determining that the operation request is a login request, obtain user information corresponding to the login request, and log in to the account corresponding to the user information;

The information writing module is configured to generate a session identifier after determining that the account is successfully logged in, write the session identifier into a Cookie, and write the user information into the Redis server corresponding to the Redis address information.

In an embodiment, the information writing module includes:

The first writing unit is configured to generate a session identifier through a preset interceptor after determining that the account is successfully logged in, and write the session identifier into a Cookie;

The second writing unit is configured to call the set method in the preset network interface to write the user information into the Redis server corresponding to the Redis address information.

In an embodiment, the single sign-on device includes:

An identification acquisition module, configured to, after determining that the operation request is not a login request, obtain the session identifier corresponding to the operation request from the Cookie through a preset loading interface;

An information query module, configured to query the Redis server corresponding to the Redis address information through the preset loading interface, and determine whether the user information corresponding to the session identifier exists in the Redis server;

The access execution module is configured to, after determining that the user information corresponding to the session identifier exists in the Redis server, access the access party interface to execute the operation request.

In an embodiment, the single sign-on device further includes:

A time setting module configured to set the timeout period of the user information in the Redis server;

An information deletion module configured to delete the user information in the Redis server when detecting that the storage time of the user information reaches the timeout period;

The login prompt module is configured to output prompt information to prompt the user to log in again after determining that the user information corresponding to the session identifier does not exist in the Redis server.

In one embodiment, the account login module includes:

An information verification unit configured to, after determining that the operation request is a login request, obtain user information corresponding to the login request, and verify the user information;

The prompt output unit is configured to output prompt information to prompt the user to input new user information after determining that the user information verification fails;

The account login unit is configured to log in to the account corresponding to the user information after determining that the user information is verified.

In addition, in order to achieve the above object, this application also provides a single sign-on device, the single sign-on device comprising: a memory, a processor, and a single sign-on stored on the memory and capable of running on the processor The corresponding computer program, when the computer program corresponding to the single sign-on is executed by the processor, implements the steps of the single sign-on method described above.

In addition, in order to achieve the above object, the present application also provides a computer-readable storage medium having a computer program corresponding to single sign-on stored on the computer-readable storage medium, and the computer program corresponding to single sign-on is executed by a processor When implementing the steps of the single sign-on method above.

This application discloses a single sign-on method, device, equipment, and computer-readable storage medium. The single sign-on method in this application includes: detecting that the access party service is started, obtaining Redis address information from the preset configuration center; receiving The operation request is to determine whether the operation request is a login request according to the network address of the operation request; if it is determined that the operation request is a login request, the user information corresponding to the login request is obtained, and the user information corresponding to the user information is logged in Account; after determining that the account is successfully logged in, a session identifier is generated, the session identifier is written into a Cookie, and the user information is written into the Redis server corresponding to the Redis address information. In the embodiment of this application, the configuration center is preset and the Redis address information is saved to the configuration center. When the single sign-on device receives the operation request, the single sign-on device determines whether the operation request is a login request, and after determining that the operation request is a login request, The single sign-on device obtains the Redis address information from the configuration center, and the single sign-on device stores the user information in the login request in the Redis server corresponding to the Redis address information, so that the access party does not need to directly connect to the Redis interface, which improves single sign-on Stability and security.

Description of the drawings

FIG. 1 is a schematic diagram of a device structure of a hardware operating environment involved in a solution of an embodiment of the present application;

2 is a schematic flowchart of the first embodiment of the single sign-on method of this application;

3 is a schematic diagram of a specific scenario of the first embodiment of the single sign-on method of this application;

4 is a schematic flowchart of a second embodiment of the single sign-on method of this application;

FIG. 5 is a schematic diagram of functional modules of an embodiment of a single sign-on device according to the present application.

The realization, functional characteristics, and advantages of the purpose of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings.

Implementation of this application

It should be understood that the specific embodiments described here are only used to explain the application, and are not used to limit the application.

As shown in FIG. 1, FIG. 1 is a schematic diagram of the device structure of the hardware operating environment involved in the solution of the embodiment of the present application.

The single sign-on device in the embodiment of the present application may be a PC or a server device.

As shown in FIG. 1, the single sign-on device may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, and a communication bus 1002. Among them, the communication bus 1002 is used to implement connection and communication between these components. The user interface 1003 may include a display screen (Display) and an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory, or a stable memory (non-volatile memory), such as a magnetic disk memory. Optionally, the memory 1005 may also be a storage device independent of the foregoing processor 1001.

Those skilled in the art can understand that the structure of the single sign-on device shown in FIG. 1 does not constitute a limitation on the single sign-on device. The single sign-on device may include more or less components than shown in the figure, or a combination of some Components, or different component arrangements.

As shown in FIG. 1, a memory 1005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a computer program corresponding to single sign-on.

In the single sign-on device shown in FIG. 1, the network interface 1004 is mainly used to connect to a background server and perform data communication with the background server; the user interface 1003 is mainly used to connect to a client (user side) and perform data communication with the client; The processor 1001 may be used to call the computer program corresponding to the single sign-on stored in the memory 1005. When the computer program corresponding to the single sign-on running on the processor is executed, the method implemented can refer to the single sign-on of this application. Various examples of methods.

Based on the above hardware structure, an embodiment of the single sign-on method of the present application is proposed.

Referring to Fig. 2, Fig. 2 is a schematic flowchart of a first embodiment of a single sign-on method according to this application. The single sign-on method includes:

Step S10, it is detected that the access party service is started, and the Redis address information is obtained from the preset configuration center.

In this embodiment, the single sign-on method is applied to a single sign-on device, the single sign-on device is set at the front end of the single sign-on system, and the single sign-on device is used to process operation requests received on the single sign-on system; specifically, In this embodiment, the single sign-on device is in communication connection with the user client, the access party service platform, and the single sign-on system. For example, the first service platform, the second service platform, and the third service platform serve as interconnected and trusted connections. Incoming business platform, the development or operation and maintenance personnel will communicate in advance the first business platform, the second business platform and the third business platform to the single sign-on system, so that after the user logs in to the first business platform, the user can use the single sign-on system. Can access the second business platform and the third business platform at the same time, specifically:

The configuration center of the single sign-on device in this embodiment is preset, and the configuration center contains Redis address information. The single sign-on device detects the access party. When the service platform corresponding to the access party starts, the access party sends a start instruction to Single sign-on device, the single sign-on device receives the start instruction sent by the access party, the single sign-on device detects that the access party service is started, the single sign-on device obtains the Redis address information from the preset configuration center to call the Redis address information Redis related methods store or obtain user information.

In this embodiment, the Redis-related configuration is stored in the configuration center through a preset configuration center. In this embodiment, the internal implementation of single sign-on is hidden to avoid the risk of exposing the single-point system caused by Redis.

Step S20, receiving the operation request, and judging whether the operation request is a login request according to the network address of the operation request.

The single sign-on device receives the operation request. The type of the operation request is not specifically limited, that is, the operation request can be a login request, an access request, or an editing request. In addition, the triggering method of the operation request is not specifically limited, and the operation request can be It is triggered by the user. For example, the user enters on the user terminal: xxx mailbox clicks "Enter" to trigger an operation request, and the terminal sends the operation request to the single sign-on device; the operation request can also be triggered automatically, for example, in the user terminal It is preset to automatically log in to the xxx system every morning to query business data, and the terminal automatically triggers an operation request every morning, and the terminal sends the operation request to the single sign-on device.

When the single sign-on device receives the operation request, the single sign-on device obtains the network address corresponding to the operation request, and the single sign-on device judges whether the operation request is a login request according to the network address. Specifically, a set of login URLs is preset in the single sign-on device , The single sign-on device compares the network address corresponding to the operation request with each preset login address in the set of login URLs, determines whether the network address corresponding to the operation request is the preset login address in the set of preset login URLs, and determines the network If the address is the preset login address in the preset login URL set, the single sign-on device determines that the operation request is a login request; if the network address is not the preset login address in the preset login URL set, the single sign-on device determines the operation request Not a login request.

In this embodiment, the single sign-on device determines whether the operation request is a login request to determine the subsequent processing steps, namely,

Step S30: It is determined that the operation request is a login request, then user information corresponding to the login request is obtained, and the account corresponding to the user information is logged in.

To determine that the operation request is a login request, the single sign-on device obtains the user information corresponding to the login request, where the user information includes account identification (account identification refers to identification information that uniquely identifies the login account, for example, account name, user name, user ID Number) and login password and other account-related information, the single sign-on device enters the user information into the corresponding network address and executes the login instruction to log in to the account corresponding to the user information; specifically, including:

Step a1, it is determined that the operation request is a login request, then user information corresponding to the login request is obtained, and the user information is verified;

Step a2, it is determined that the user information verification fails, and then a prompt message is output to prompt the user to input new user information;

Step a3, it is determined that the user information is verified, and then the account corresponding to the user information is logged in.

With reference to Figure 3, in this embodiment, a filter (filter) is preset in the single sign-on device, where the preset filter refers to a preset filtering code, and the preset filter can be passed through SDK (Software Development Kit, a software development kit is a collection of development tools used by software engineers to build application software for specific software packages, software frameworks, hardware platforms, operating systems, etc.).

If the operation request is a login request, the preset filter in the single sign-on device does not intercept the login request. The single sign-on device obtains the user information corresponding to the login request and verifies the user information; that is, the standard login is pre-stored in the single sign-on device Information collection, the standard login information of each user registered or actively set in the standard login information collection, the single sign-on device compares the user information corresponding to the login request with the standard login information in the standard login information collection to compare the user information Perform verification, that is, if there is the same target standard information as the user information in the standard login information set, the user information verification is passed; if the standard login information set does not have the same target standard information as the user information, the user information verification fails ; If the user information verification fails, the single sign-on device outputs prompt information to prompt the user to enter new user information; if the user information is verified, the single sign-on device logs in to the account corresponding to the user information.

Step S40: After it is determined that the account login is successful, a session identifier is generated, the session identifier is written into a Cookie, and the user information is written into the Redis server corresponding to the Redis address information.

Specifically, it includes:

Step b1, after determining that the account is successfully logged in, generate a session identifier through a preset interceptor, and write the session identifier into a Cookie;

Step b2, calling the set method in the preset network interface, and writing the user information into the Redis server corresponding to the Redis address information.

That is, when the account is successfully logged in, an interceptor is preset in the single sign-on device. The preset interceptor refers to the preset code used to generate the session identifier. The preset interceptor can be used through SDK (Software Development Kit, a software development kit is a collection of development tools used by some software engineers to build application software for specific software packages, software frameworks, hardware platforms, operating systems, etc.). Single sign-on devices generate session identifiers through preset interceptors. , And write the session ID to the Cookie.

With reference to Figure 3, the single sign-on device calls the set method in the preset network interface (the preset network interface refers to the pre-rewritten Http Session interface code to implement user information storage operations). The preset network interface follows the set method Write user information to the Redis server corresponding to the Redis address information.

It is understandable that, in this embodiment, the single sign-on device writes user information into the Redis server corresponding to the Redis address information. When the user visits the preset interconnected and trusted access party, the single sign-on device calls the preset Loading interface (default loading interface refers to the pre-adapted Http Servlet Reques interface, the preset loading interface is used to obtain user information from Redis and return user information to the get The User Principle method obtains the session ID corresponding to the operation request from the Cookie; the single sign-on device queries the Redis server corresponding to the Redis address information through the preset loading interface, and obtains the user information corresponding to the session ID in the Redis server, so as to realize single sign-on, That is, the single sign-on device queries the Redis server for the user information corresponding to the session identifier, and the access party responds to the user operation request; the single sign-on device queries the Redis server that there is no user information corresponding to the session identifier, the single sign-on device The user is prompted to log in again. Among them, there are many reasons why the user information corresponding to the session identifier does not exist in the Redis server. For example, the user information in the Redis server is stored for too long and is deleted, or the user triggers the logout operation of the login account.

In the embodiment of this application, the configuration center is preset and the Redis address information is saved to the configuration center. When the single sign-on device receives the operation request, the single sign-on device determines whether the operation request is a login request, and after determining that the operation request is a login request, The single sign-on device obtains the Redis address information from the configuration center, and the single sign-on device stores the user information in the login request in the Redis server corresponding to the Redis address information, so that the access party does not need to directly connect to the Redis interface, which improves single sign-on Stability and security.

Further, referring to FIG. 4, on the basis of the first embodiment of the single sign-on method of the present application, a second embodiment of the application method is proposed.

This embodiment is a step after step S20 in the first embodiment. The difference between this embodiment and the first embodiment is:

Step S50: It is determined that the operation request is not a login request, and the session identifier corresponding to the operation request is obtained from the Cookie through a preset loading interface.

If the operation request is not a login request, the single sign-on device calls the preset loading interface (the preset loading interface refers to the pre-adapted Http Servlet Reques interface, the preset loading interface is used to obtain user information from Redis and return user information to the get The User Principle method obtains the session identifier corresponding to the operation request from the Cookie.

That is, when the user performs single sign-on, the single sign-on device will generate a session identifier and write the session identifier into the cookie. When the user performs an operation request, the single sign-on device will obtain the session identifier from the cookie to transfer the session The identifier is used as the key value to obtain the user information corresponding to the session identifier from the Redis server, specifically:

Step S60: Query the Redis server corresponding to the Redis address information through the preset loading interface, and determine whether the user information corresponding to the session identifier exists in the Redis server.

The single sign-on device queries the Redis server corresponding to the Redis address information through the preset loading interface, and the single sign-on device determines whether there is user information corresponding to the session identifier in the Redis server.

Step S70: It is determined that the user information corresponding to the session identifier exists in the Redis server, and the access party interface is accessed to execute the operation request.

If there is user information corresponding to the session identifier in the Redis server, the single sign-on device determines that the user is in the logged-in state, and the single sign-on device accesses the access party interface to perform the operation request, that is, the single sign-on device calls Http through the access party interface The set or get method of the Session request sets and obtains the session attribute value. The set and get methods will set or query the attribute value to the Redis server according to the session identifier to implement the operation request.

Step S80: It is determined that the user information corresponding to the session identifier does not exist in the Redis server, and a prompt message is output to prompt the user to log in again.

The Redis server can clear the cache information, the single sign-on device queries to determine that there is no user information corresponding to the session identifier in the Redis server, and the single sign-on device outputs prompt information to prompt the user to log in again. In this embodiment, the Redis server caches the updated information Features to avoid the situation that long-term login on the business platform takes up resources and no one uses it.

In this embodiment, when the operation request of the single sign-on device is not a login request, the single sign-on device calls the Http Servlet Get in Request User Principle method to obtain user information, in Http The user information returned by the Servlet Request does not require the user to perform repeated login operations. The single sign-on device accesses the access party interface to perform the operation request, which makes the user operation more convenient.

In this embodiment, the original Http Session interface code and Http Servlet Reqeust interface code is adapted, and the native Http Session and Http The Servlet Request is replaced with the implementation of the single sign-on system, so that the operation and maintenance personnel of the access party do not need to modify the code, which achieves zero intrusion to the system, facilitates the operation of the access party, and realizes that the user is not aware.

Further, on the basis of the foregoing embodiments of the single sign-on method of the present application, a third embodiment of the method of the present application is proposed.

This embodiment is a step after step S20 of the first embodiment. The difference between this embodiment and the above-mentioned embodiment lies in:

Set the timeout time of the user information in the Redis server, and delete the user information in the Redis server when it is detected that the storage time of the user information reaches the timeout time.

The single sign-on device sets the timeout time of the user information in the Redis server so that the Redis server automatically clears the cache information according to the set timeout time. In this embodiment, setting the timeout time of the user information in the Redis server can be implemented in different ways, specifically: Implementation method 1: The single sign-on device sets the timeout time of user information according to the user level in the user information. For example, if the user level in the user information is level 1, the timeout time of the user information is 10 minutes, and the user level in the user information If it is level two, the timeout time for user information is 20 minutes; implementation mode 2: the remaining space setting in the Redis server of the single sign-on device, when the remaining space in the Redis server is greater than 50%, the timeout time is 20 minutes, When the remaining space in the Redis server is less than or equal to 50%, the timeout period is 10 minutes.

When the single sign-on device detects that the storage time of the user information in the Redis server reaches the timeout period, the single sign-on device deletes the user information in the Redis server, and then executes step S60 in the second embodiment, and loads through the preset The interface queries the Redis server corresponding to the Redis address information, and determines whether the user information corresponding to the session identifier exists in the Redis server. The result obtained is: the user information corresponding to the session identifier does not exist in the Redis server, then the single The login device outputs prompt information to enable the user to log in again.

After the single sign-on device in this embodiment writes the user information into the Redis server corresponding to the Redis address information, the single sign-on device may also set the storage time of the user information to reduce the resource occupation of the Redis server and further improve security.

5, an embodiment of the present application further provides a single sign-on device, the single sign-on device includes:

The address obtaining module 10 is configured to detect that the access party service is started, and obtain Redis address information from the preset configuration center;

The request judgment module 20 is configured to receive an operation request, and determine whether the operation request is a login request according to the network address of the operation request;

The account login module 30 is configured to, after determining that the operation request is a login request, obtain user information corresponding to the login request, and log in to the account corresponding to the user information;

The information writing module 40 is configured to generate a session identifier after determining that the account is successfully logged in, write the session identifier into a Cookie, and write the user information into the Redis server corresponding to the Redis address information.

In an embodiment, the information writing module includes:

In an embodiment, the single sign-on device includes:

In an embodiment, the single sign-on device further includes:

In an embodiment, the account login module includes:

When each functional module in the single sign-on device of the present application is executed, the steps of the single sign-on method described above are implemented, which will not be repeated in this embodiment.

It should be noted that in this article, the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements not only includes those elements, It also includes other elements not explicitly listed, or elements inherent to the process, method, article, or system. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, article or system that includes the element.

The serial numbers of the foregoing embodiments of the present application are only for description, and do not represent the advantages and disadvantages of the embodiments.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better.的实施方式。 Based on this understanding, the technical solution of this application essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM) as described above. , Magnetic disk, optical disk), including several instructions to make a terminal device (can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the method described in each embodiment of the present application.

The above are only preferred embodiments of this application, and do not limit the scope of this application. Any equivalent structure or equivalent process transformation made using the content of the description and drawings of this application, or directly or indirectly used in other related technical fields , The same reason is included in the scope of patent protection of this application.

Claims

A single sign-on method, which includes the following steps:

It is detected that the access party service is started, and the Redis address information is obtained from the preset configuration center;

After receiving the operation request, determine whether the operation request is a login request according to the network address of the operation request;

Determining that the operation request is a login request, acquiring user information corresponding to the login request, and logging in to an account corresponding to the user information;

After it is determined that the account login is successful, a session identifier is generated, the session identifier is written into a Cookie, and the user information is written into the Redis server corresponding to the Redis address information.
The single sign-on method according to claim 1, wherein said "when the account login is successful, a session identifier is generated, the session identifier is written into a Cookie, and the user information is written into the Redis address information The steps of the corresponding Redis server include:

After determining that the account is successfully logged in, generate a session identifier through a preset interceptor, and write the session identifier into a Cookie;

The set method in the preset network interface is called to write the user information into the Redis server corresponding to the Redis address information.
The single sign-on method according to claim 1, wherein after the step of "receiving an operation request, and judging whether the operation request is a login request according to the network address of the operation request", it comprises:

Determine that the operation request is not a login request, then obtain the session identifier corresponding to the operation request from the Cookie through the preset loading interface;

Query the Redis server corresponding to the Redis address information through the preset loading interface, and determine whether the user information corresponding to the session identifier exists in the Redis server;

It is determined that the user information corresponding to the session identifier exists in the Redis server, then accessing the access party interface to execute the operation request.
The single sign-on method according to claim 3, wherein the "after determining that the account login is successful, generate a session identifier, write the session identifier into a Cookie, and write the user information into the Redis address information After the steps of "corresponding Redis server", it also includes:

Setting the timeout period of the user information in the Redis server;

Detecting that the storage time of the user information reaches the timeout period, deleting the user information in the Redis server;

After the step of "querying the Redis server corresponding to the Redis address information through the preset loading interface, and judging whether the user information corresponding to the session identifier exists in the Redis server", the method further includes:

If it is determined that the user information corresponding to the session identifier does not exist in the Redis server, prompt information is output to prompt the user to log in again.
The single sign-on method according to any one of claims 1 to 4, wherein the "determine that the operation request is a login request, then obtain the user information corresponding to the login request, and log in to the account corresponding to the user information "The steps include:

Determining that the operation request is a login request, acquiring user information corresponding to the login request, and verifying the user information;

If it is determined that the user information verification fails, output a prompt message to prompt the user to input new user information;

If it is determined that the user information is verified, log in to the account corresponding to the user information.
A single sign-on device, wherein the single sign-on device includes:

The address obtaining module is configured to detect that the access party service is started and obtain the Redis address information from the preset configuration center;

The request judgment module is configured to receive the operation request, and determine whether the operation request is a login request according to the network address of the operation request;

The account login module is configured to, after determining that the operation request is a login request, obtain user information corresponding to the login request, and log in to the account corresponding to the user information;

The information writing module is configured to generate a session identifier after determining that the account is successfully logged in, write the session identifier into a Cookie, and write the user information into the Redis server corresponding to the Redis address information.
7. The single sign-on device according to claim 6, wherein the information writing module comprises:

The first writing unit is configured to generate a session identifier through a preset interceptor after determining that the account is successfully logged in, and write the session identifier into a Cookie;

The second writing unit is configured to call the set method in the preset network interface to write the user information into the Redis server corresponding to the Redis address information.
8. The single sign-on device of claim 6, wherein the single sign-on device comprises:

An identification acquisition module, configured to, after determining that the operation request is not a login request, obtain the session identifier corresponding to the operation request from the Cookie through a preset loading interface;

An information query module, configured to query the Redis server corresponding to the Redis address information through the preset loading interface, and determine whether the user information corresponding to the session identifier exists in the Redis server;

The access execution module is configured to, after determining that the user information corresponding to the session identifier exists in the Redis server, access the access party interface to execute the operation request.
The single sign-on device according to claim 8, wherein the single sign-on device further comprises:

A time setting module configured to set the timeout period of the user information in the Redis server;

An information deletion module configured to delete the user information in the Redis server when detecting that the storage time of the user information reaches the timeout period;

The login prompt module is configured to output prompt information to prompt the user to log in again after determining that the user information corresponding to the session identifier does not exist in the Redis server.
The single sign-on device according to any one of claims 6 to 9, wherein the account login module includes:

An information verification unit configured to, after determining that the operation request is a login request, obtain user information corresponding to the login request, and verify the user information;

The prompt output unit is configured to output prompt information to prompt the user to input new user information after determining that the user information verification fails;

The account login unit is configured to log in to the account corresponding to the user information after determining that the user information is verified.
A single sign-on device, the single sign-on device comprising: a memory, a processor, and a computer program corresponding to the single sign-on stored on the memory and run on the processor, the single sign-on corresponding When the computer program of is executed by the processor, the steps of the single sign-on method according to any one of claims 1 to 5 are realized.
A computer-readable storage medium having a computer program corresponding to single sign-on stored on the computer-readable storage medium, and when the computer program corresponding to single sign-on is executed by a processor, the computer program implements any one of claims 1 to 5 Steps of the single sign-on method described in item.