Method and device for quickly accessing supplier system to user center

Abstract

The invention discloses a method and a device for quickly accessing a supplier system to a user center. The method comprises the following steps: deploying a Servlet filter in a Web application container of a supplier system to intercept all HTTP (Hyper Text Transport Protocol) requests; checking whether the request carries an authentication certificate from the unified user center, and if not, redirecting to the unified user center for authentication; a verification request is sent to a user center verification interface after the voucher is obtained, and a local session is created in the supplier system based on returned user information after verification succeeds; and storing the authentication credential and the session identifier in a distributed cache in an associated manner, returning the credential through Cookie, and finally releasing the request to a service logic layer. According to the method, zero-intrusive integration is realized, core codes of the supplier system do not need to be modified, and the method has the advantages of low development cost, high access speed, high universality, high safety, support of single sign-on and sign-off and the like, and is suitable for various Java Web supplier systems to quickly access the unified user center.

Description

Technical Field

[0001] This application relates to the field of system access methods, and in particular to a method, apparatus, computer-readable storage medium, and electronic device for a supplier system to quickly access a user center. Background Technology

[0002] In traditional vendor system-user center integration models, a method based on pre-defined interface specifications is typically used. In this model, the integrating party must adhere to the fixed interface protocols defined by the vendor system (such as specific data formats, call flows, and authentication mechanisms) to complete the system integration. Specifically, the integrating party needs to perform a series of standardized operations, including but not limited to: completing a lengthy account registration and permission application process on the vendor platform, performing localized configuration according to the interface documentation (such as parameter mapping and environment adaptation), and conducting customized development and debugging for the interface's input / output (I / O) constraints. This process heavily relies on the integrating party's in-depth understanding of the vendor system's underlying architecture, interface implementation details, and authentication logic—for example, parsing core code logic such as interface encryption algorithms and session management mechanisms; otherwise, it is difficult to ensure the stability and compatibility of the integration.

[0003] However, this type of integration model has significant limitations: First, high development costs. The access party needs to invest significant manpower in interface adaptation, abnormal scenario testing, and subsequent maintenance. Especially when the supplier's system is upgraded or the interface changes, its own system must be adjusted to match the new specifications, further increasing iteration costs. Second, lengthy development cycles. The entire process, from requirement alignment and environment setup to functional verification, is time-consuming, making it difficult to meet the needs of rapid business integration. Third, lack of flexibility. The types and quantities of input parameters and the output data structure of the interface are strictly fixed, making it impossible to flexibly configure them according to the access party's personalized business scenarios (such as expanding fields or dynamically adjusting authentication strategies). This results in low data interaction efficiency between systems and difficulty in adapting to changing business needs. Fourth, strong technical dependence. The access party needs to continuously rely on the supplier for technical support (such as interface update notifications and troubleshooting assistance). If the supplier's response is delayed or services are terminated, it may lead to integration interruptions, affecting business continuity.

[0004] In summary, traditional interface-based integration methods with fixed specifications are no longer sufficient to meet the current development needs of enterprise-level systems for rapid integration, flexible expansion, and low-cost operation and maintenance. There is an urgent need for a more efficient and universal vendor system access solution. Summary of the Invention

[0005] To overcome the aforementioned shortcomings of traditional integration methods, this application proposes a novel method for rapid integration of a supplier system with a user center. This invention aims to address the problems of high development costs, insufficient flexibility, and strong technological dependence inherent in traditional supplier system-user center integration, providing a rapid integration solution that is highly versatile, low-intrusive, and has low development costs. Specific objectives include: 1. Simplify development: Integration can be achieved simply by using standard Servlet interceptors without needing to understand or modify the vendor's internal authentication code.

[0006] 2. Increased flexibility: Allows developers to customize access logic as needed, without being restricted by the fixed interface specifications of the supplier's system.

[0007] 3. Reduce costs: Bypass the complex supplier registration and approval system to achieve independent and rapid connection.

[0008] To achieve the above objectives, the present invention adopts the following technical strategy: a custom general Servlet interceptor (Filter) is deployed in the web application container (such as Tomcat) layer of the supplier system to seamlessly take over all HTTP requests flowing into the supplier system; before the request reaches the business logic layer, the interceptor communicates and interacts with the external unified user center to complete identity authentication and session state synchronization, and then passes the authenticated request through to the target business component, without requiring any modification to the existing code of the supplier system.

[0009] This invention innovatively proposes a zero-intrusion proxy authentication mode based on a standard Web container mechanism: by leveraging the native interception capabilities of the Servlet specification, the authentication process originally embedded in the business system is transparently transferred to an external unified user center for processing without modifying the vendor system's source code (the vendor system is unaware of this). This mode achieves complete decoupling between the vendor system and the authentication logic, systematically solving the core shortcomings of traditional solutions in terms of development cost, flexibility, and technological dependence.

[0010] Specifically, this application provides the following technical solutions: The first aspect of this application provides a method for a supplier system to quickly access a user center, the method comprising: S1. Deploy a Servlet filter in the web application container of the supplier system and configure it to intercept all HTTP requests entering the supplier system; S2. Receive user access requests through the Servlet filter and check whether the request carries authentication credentials from the unified user center; S3. If the request does not carry the authentication credential, the request is redirected to the authentication entry point of the unified user center, and an access request carrying the authentication credential is returned after the user completes authentication. S4. Extract the authentication credentials through the Servlet filter and send a verification request to the verification interface of the unified user center; S5. Receive the verification response returned by the unified user center. If the verification is successful, create a local user session in the supplier system based on the user information in the verification response. S6. Associate the authentication credential with the session identifier of the local user session and store it in a distributed cache, and return the authentication credential to the user's browser via a cookie; S7. Allow the access request to the business logic layer of the supplier system.

[0011] Furthermore, in the method of this application, the step S1 of deploying the Servlet filter in the Web application container of the supplier system includes: creating a filter class that inherits from javax.servlet.Filter in the Web application of the supplier system, and registering the filter class as a global interceptor through a web.xml configuration file or annotation.

[0012] Furthermore, in the method of this application, the authentication credentials are transmitted in the request via URL query parameters or browser cookies.

[0013] Furthermore, in the method of this application, the step S3 of redirecting the request to the authentication entry of the unified user center includes: constructing a redirect URL containing a product code and a callback address, wherein the product code is used to identify the supplier system and the callback address is used to receive the authentication credentials returned by the unified user center.

[0014] Furthermore, in the method of this application, the step S4 of sending a verification request to the verification interface of the unified user center includes: sending the authentication credential and the product code of the supplier system to the Token verification interface of the unified user center through a backend HTTP POST request.

[0015] Furthermore, in the method of this application, the step S5 of creating a local user session within the supplier system includes: extracting the username of the unified user center from the verification response, calling the automatic login interface inside the supplier system, and creating a valid local session with the username.

[0016] Furthermore, in the method of this application, the step S6 of associating the authentication credential with the session identifier of the local user session and storing it in the distributed cache includes: establishing a mapping relationship between the authentication credential and the local token of the local user session in the distributed cache.

[0017] Furthermore, the method of this application also includes: If the verification response indicates that the authentication credential is invalid or expired, the local user session is cleared, and the step of redirecting to the unified user center authentication entry is re-executed; The pre-configured administrator account is exempt from the verification of authentication credentials and subsequent steps, and the request is allowed directly.

[0018] A second aspect of this application provides an apparatus for rapid access of a supplier system to a user center. The apparatus, when operating, implements the steps of the aforementioned method for rapid access of a supplier system to a user center. The apparatus includes: The Servlet filter deployment module is used to deploy Servlet filters in the web application container of the vendor system and configure them to intercept all HTTP requests entering the vendor system. The authentication credential checking module is used to receive user access requests through the Servlet filter and check whether the request carries authentication credentials from the unified user center. The redirection module is used to redirect the request to the authentication entry point of the unified user center when the authentication credential is not carried in the request, and to return an access request carrying the authentication credential after the user completes the authentication. The credential verification module is used to extract the authentication credentials through the Servlet filter and send a verification request to the verification interface of the unified user center. The session creation module is used to receive the verification response returned by the unified user center. If the verification is successful, a local user session is created in the supplier system based on the user information in the verification response. The state synchronization module is used to associate the authentication credentials with the session identifier of the local user session and store them in a distributed cache, and return the authentication credentials to the user's browser via a cookie; The request permission module is used to allow the access request to the business logic layer of the supplier system.

[0019] A third aspect of this application provides an electronic device, including: a memory and a processor; Memory: Used to store computer programs; Processor: Used to execute the computer program to implement the steps of the aforementioned method for rapid access of the supplier system to the user center.

[0020] A fourth aspect of this application provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, it implements the steps of the aforementioned method for rapid access to a user center by a supplier system.

[0021] In summary, compared with traditional interface methods based on fixed specifications, the solution of this invention has the following technical advantages: (1) Achieve zero-intrusion integration and significantly reduce development and maintenance costs: Only standard Servlet Filter components and a small amount of declarative configuration need to be deployed, without modifying the existing business code of the supplier system, thus completely avoiding the risks and costs brought about by source code-level transformation.

[0022] (2) The access cycle is greatly shortened and the implementation efficiency is greatly improved: the access party can independently control the integration progress, and in typical scenarios, end-to-end joint debugging and delivery can be completed within a few days.

[0023] (3) It has broad applicability and is independent of technology stack: It is built based on the Java Servlet general specification and can be seamlessly adapted to most Web application containers (such as Tomcat, Jetty, etc.), and has strong compatibility with heterogeneous Java Web systems.

[0024] (4) Strengthen security control and centralized session management: The token verification logic is closed-loop on the entire server side to eliminate the risk of front-end forgery; the session lifecycle is uniformly managed by distributed caching (such as Redis), and it naturally supports advanced security strategies such as single sign-out.

[0025] (5) Optimize user experience and ensure cross-system authentication consistency: Cross-system single sign-on (SSO) is achieved through a unified user center, allowing users to access all related supplier systems smoothly with only one authentication, thereby improving business fluency and user satisfaction.

[0026] Other features and advantages of this application will be set forth in detail in the following description, or will become apparent through the implementation of the relevant technical solutions of this application. The objectives and other advantages of this application can be achieved through the technical features and means explicitly pointed out in the description, claims, and drawings, and will be obtained through the implementation of these technical contents. Attached Figure Description

[0027] To more clearly illustrate the technical solutions of this application, the accompanying drawings involved in the description of the embodiments will be briefly introduced below. It should be noted that the drawings only show some embodiments of this application. For those skilled in the art, other related drawings can be derived from these drawings without creative effort.

[0028] Figure 1 This is a flowchart illustrating the overall implementation process of the method for quickly connecting the supplier system to the user center in this application.

[0029] Figure 2 This is a diagram illustrating the specific implementation process of the embodiments of this application.

[0030] Figure 3 This is a structural diagram of the device for the supplier system to quickly access the user center in this application.

[0031] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0032] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be noted that the described embodiments are only some embodiments of this application, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the protection scope of this application.

[0033] In this document, the term "comprising" and any variations thereof (such as "including," "including," etc.) are open-ended expressions and should be understood as "including but not limited to," meaning that the listed content is not exhaustive and may include other content not explicitly mentioned. The term "based on" should be understood as "at least partially based on," meaning that the basis or condition referred to may not be the only factor and may involve other relevant factors. The term "one embodiment" should be understood as "at least one embodiment," meaning that the described embodiment is not the only possible implementation, and other similar embodiments may exist.

[0034] In this application, the terms "a" and "a plurality of" are used to modify related elements or features, and their expression is illustrative rather than restrictive. Unless otherwise expressly stated in the context, "a" should be understood as "at least one," and "a plurality of" should be understood as "at least two." Those skilled in the art should reasonably interpret these terms based on the semantic and logical relationships of the context to ensure that they cover the possibility of "one or more."

[0035] Figure 1 The diagram shows the overall implementation flow of the method for quickly connecting the supplier system to the user center provided in this application, including the following steps: S1. Deploy a Servlet filter in the web application container of the supplier system and configure it to intercept all HTTP requests entering the supplier system; S2. Receive user access requests through the Servlet filter and check whether the request carries authentication credentials from the unified user center; S3. If the request does not carry the authentication credential, the request is redirected to the authentication entry point of the unified user center, and an access request carrying the authentication credential is returned after the user completes authentication. S4. Extract the authentication credentials through the Servlet filter and send a verification request to the verification interface of the unified user center; S5. Receive the verification response returned by the unified user center. If the verification is successful, create a local user session in the supplier system based on the user information in the verification response. S6. Associate the authentication credential with the session identifier of the local user session and store it in a distributed cache, and return the authentication credential to the user's browser via a cookie; S7. Allow the access request to the business logic layer of the supplier system.

[0036] To more clearly illustrate the technical solution of this application, the following will provide further explanation through specific scenario embodiments.

[0037] Figure 2 The following is a detailed implementation process of the solution in this embodiment, including the following steps: 1. Deploy a custom authentication interceptor (as shown in step ① in the image). (1) In the Web application of the supplier system, add a custom filter class that inherits from javax.servlet.Filter.

[0038] (2) Configure this filter as a global interceptor in the deployment descriptor (web.xml) of the web application or through annotation so that it can handle all user requests.

[0039] 2. Intercept and inspect authentication credentials (Token) (as shown in step ② in the figure) (1) When a user accesses the supplier system, the interceptor first checks whether the request carries an authentication credential from the unified user center (hereinafter referred to as cestcToken).

[0040] (2) The cestcToken can be transmitted in the following two ways: URL query parameters: for example, ?cestcToken=xxx.

[0041] Browser Cookie: A cookie named cestcToken.

[0042] (3) If the request contains neither query parameters nor cookies, it is assumed that the user has not been authenticated by the unified user center.

[0043] 3. Redirect to the unified user center login (as shown in step ③ in the image). (1) If no valid cestcToken is detected, the interceptor will construct a redirect URL to automatically guide the user to the Single Sign-On (SSO) entry in the unified user center.

[0044] (2) This URL typically contains the following key information: Product Code: Used to identify the current supplier system.

[0045] Callback URL: After a user successfully logs in, the user center will redirect to this URL with the cestcToken.

[0046] (3) After logging in at the unified user center, users will be redirected back to the supplier system and a temporary cestcToken will be attached to the URL.

[0047] 4. Verify the token's validity with the user center (as shown in step ④ in the image). (1) After the interceptor obtains the cestcToken, it will immediately send a backend HTTP request (usually a POST request) to the Token verification interface of the unified user center.

[0048] (2) The request body contains productCode and cestcToken.

[0049] (3) The user center verifies the validity, validity period and product of the token, and returns a structured JSON response. The response includes a status code (e.g., "code": "20000" indicates success) and user data (e.g., username userName).

[0050] 5. Automatic login and session establishment on the local system (as shown in step ⑤ in the figure). (1) If the token verification is successful, the interceptor will extract the username of the unified user center from the response.

[0051] (2) Next, the automatic login assistant tool inside the supplier system is invoked to create a valid session on the local machine using the username.

[0052] (3) This process completely simulates the effect of a user entering a username and password to log in on the local system, but it is completed automatically by the system background.

[0053] 6. Synchronize session state and allow requests. (1) After successful login, in order to maintain the session state and enable subsequent single sign-out, the system will perform the following operations: Storing Tokens in Redis: Associate the cestcToken with a key identifier of the local session (such as LtpaToken) and store it in a distributed cache (such as Redis) to form a mapping relationship; Update Cookie: Write cestcToken back to the user's browser cookie so that it can be automatically carried in subsequent requests.

[0054] (2) Finally, the interceptor redirects the user back to the page they originally requested (with the cestcToken parameter removed), completing the entire seamless login process, and the user enters the supplier system without realizing it.

[0055] 7. Handling exceptions and logout scenarios (1) Token expires: If the token verification fails (e.g., it has expired), the interceptor will first try to clear the user's local session in the supplier system (call doLogout), and then redirect to the user center login page again.

[0056] (2) Administrator Exemption: For the super administrator (such as admin) built into the local system, it can be configured to allow direct access without going through the SSO process, which is convenient for system maintenance.

[0057] Figure 3 The diagram shows a device for rapid access of a supplier system to a user center according to this application. The device includes: The Servlet filter deployment module is used to deploy Servlet filters in the web application container of the vendor system and configure them to intercept all HTTP requests entering the vendor system. The authentication credential checking module is used to receive user access requests through the Servlet filter and check whether the request carries authentication credentials from the unified user center. The redirection module is used to redirect the request to the authentication entry point of the unified user center when the authentication credential is not carried in the request, and to return an access request carrying the authentication credential after the user completes the authentication. The credential verification module is used to extract the authentication credentials through the Servlet filter and send a verification request to the verification interface of the unified user center. The session creation module is used to receive the verification response returned by the unified user center. If the verification is successful, a local user session is created in the supplier system based on the user information in the verification response. The state synchronization module is used to associate the authentication credentials with the session identifier of the local user session and store them in a distributed cache, and return the authentication credentials to the user's browser via a cookie; The request permission module is used to allow the access request to the business logic layer of the supplier system.

[0058] The above-mentioned device implements the steps of the method for quickly accessing the user center by the supplier system disclosed in this application when it is in operation.

[0059] The flowcharts and block diagrams in the accompanying drawings illustrate possible implementations of apparatus, methods, and computer program products according to various embodiments of this application, including architecture, functionality, and operation. In these figures, each block may represent a module, program segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should be noted that each block in the block diagrams and / or flowcharts, and combinations thereof, can be implemented using either a dedicated hardware-based system or a combination of dedicated hardware and computer instructions to achieve the specified function or operation.

[0060] like Figure 4 As shown in the illustration, an embodiment of this application also discloses an electronic device, including: a processor 310, a communication interface 320, a memory 330 for storing a processor-executable computer program, and a communication bus 340. The processor 310, communication interface 320, and memory 330 communicate with each other via the communication bus 340. The processor 310 executes the executable computer program to implement the steps of the aforementioned method for rapid access to the user center from a supplier system.

[0061] It is understood that, in addition to memory and a processor, this electronic device may also include input devices (such as a keyboard), output devices (such as a display), and other communication modules. These input devices, output devices, and other communication modules all communicate with the processor through I / O interfaces (i.e., input / output interfaces).

[0062] The operations described in this application can be implemented by writing computer program code using one or more programming languages ​​or a combination thereof. The programming languages ​​include, but are not limited to, the following types: Object-oriented programming languages, such as Java, Smalltalk, C++, etc. Conventional procedural programming languages, such as "C" or similar programming languages.

[0063] The execution methods of program code include, but are not limited to: It runs entirely on the user's computer; Part of it executes on the user's computer, and part of it executes on a remote computer; Execute as a standalone software package; It is executed entirely on a remote computer or server.

[0064] In scenarios involving remote computers, the remote computer can connect to the user's computer via any type of network, including but not limited to local area networks (LANs) or wide area networks (WANs). Furthermore, the remote computer can also connect to external computers via an internet service provider, for example, by utilizing the internet.

[0065] Furthermore, this application also discloses a computer-readable storage medium, wherein when the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is able to perform the various steps of the method for rapid access to a user center by a supplier system disclosed in this application.

[0066] In the context of this application, a computer-readable storage medium refers to a tangible medium capable of storing computer program code and related data. Specific examples include, but are not limited to, the following: (1) Portable computer disk: such as floppy disks and other removable magnetic storage media.

[0067] (2) Hard disk: including mechanical hard disks and solid-state hard disks and other fixed storage devices.

[0068] (3) Random Access Memory (RAM): A volatile storage medium used for temporary storage of data and program code.

[0069] (4) Read-only memory (ROM): a non-volatile storage medium used to store fixed programs and data.

[0070] (5) Erasable programmable read-only memory (EPROM) or flash memory: non-volatile storage media that supports multiple erasures and reprogrammings.

[0071] (6) Fiber optic storage devices: storage media based on fiber optic technology.

[0072] (7) Portable compact disc read-only memory (CD-ROM): a read-only medium that stores data in the form of an optical disc.

[0073] (8) Optical storage devices: such as DVDs, Blu-ray discs and other storage media based on optical principles.

[0074] (9) Magnetic storage devices: such as magnetic tapes, disks and other storage media based on magnetic principles.

[0075] (10) Any suitable combination of the above: for example, combining multiple storage media to meet different storage needs.

[0076] These computer-readable storage media can be used to store the program code and related data described in this application to support program execution and persistent data storage.

[0077] Specifically, according to embodiments of this application, the processes described in the flowcharts can be implemented as computer software programs. For example, embodiments of this application relate to a computer program product comprising a computer program carried on a non-transitory computer-readable medium. The computer program includes program code for executing the method for rapid access to a user center from a supplier system disclosed in this application. When the computer program is executed by a processing device, it can achieve the functions defined in the embodiments of this application.

[0078] While the foregoing discussion contains several specific implementation details, these details should not be construed as limiting the scope of this application. The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this application is not limited to technical solutions formed by specific combinations of the above-described technical features. Furthermore, this application should also cover other technical solutions formed by any combination of the above-described technical features or their equivalents without departing from the foregoing disclosed concept.

[0079] Those skilled in the art should also understand that modifications can be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features, without departing from the spirit and scope of the technical solutions of the embodiments of this application. These modifications or substitutions will not cause the essence of the corresponding technical solutions to deviate from the core spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for rapid access of a supplier system to a user center, characterized in that, The method includes: S1. Deploy a Servlet filter in the web application container of the supplier system and configure it to intercept all HTTP requests entering the supplier system; S2. Receive user access requests through the Servlet filter and check whether the request carries authentication credentials from the unified user center; S3. If the request does not carry the authentication credential, the request is redirected to the authentication entry point of the unified user center, and an access request carrying the authentication credential is returned after the user completes authentication. S4. Extract the authentication credentials through the Servlet filter and send a verification request to the verification interface of the unified user center; S5. Receive the verification response returned by the unified user center. If the verification is successful, create a local user session in the supplier system based on the user information in the verification response. S6. Associate the authentication credential with the session identifier of the local user session and store it in a distributed cache, and return the authentication credential to the user's browser via a cookie; S7. Allow the access request to the business logic layer of the supplier system.

2. The method according to claim 1, characterized in that, The step S1 of deploying a Servlet filter in the web application container of the supplier system includes: creating a filter class that inherits from javax.servlet.Filter in the web application of the supplier system, and registering the filter class as a global interceptor through a web.xml configuration file or annotation.

3. The method according to claim 1, characterized in that, The authentication credentials are transmitted in the request via URL query parameters or browser cookies.

4. The method according to claim 1, characterized in that, The step S3, which redirects the request to the authentication entry point of the unified user center, includes: constructing a redirect URL containing a product code and a callback address, wherein the product code is used to identify the supplier system and the callback address is used to receive authentication credentials returned by the unified user center.

5. The method according to claim 1, characterized in that, The step S4 of sending a verification request to the verification interface of the unified user center includes: sending the authentication credential and the product code of the supplier system to the Token verification interface of the unified user center via a backend HTTP POST request.

6. The method according to claim 1, characterized in that, The step S5, which involves creating a local user session within the supplier system, includes: extracting the username from the unified user center from the verification response, calling the automatic login interface within the supplier system, and creating a valid local session using the username.

7. The method according to claim 1, characterized in that, The step S6, which associates the authentication credentials with the session identifier of the local user session and stores them in the distributed cache, includes: establishing a mapping relationship between the authentication credentials and the local token of the local user session in the distributed cache.

8. The method according to claim 1, characterized in that, The method further includes: If the verification response indicates that the authentication credential is invalid or expired, the local user session is cleared, and the step of redirecting to the unified user center authentication entry is re-executed; The pre-configured administrator account is exempt from the verification of authentication credentials and subsequent steps, and the request is allowed directly.

9. A device for rapid access of a supplier system to a user center, characterized in that, The device, when operating, implements the step of the method for rapid access to the user center by a supplier system as described in any one of claims 1-8, wherein the device comprises: The Servlet filter deployment module is used to deploy Servlet filters in the web application container of the vendor system and configure them to intercept all HTTP requests entering the vendor system. The authentication credential checking module is used to receive user access requests through the Servlet filter and check whether the request carries authentication credentials from the unified user center. The redirection module is used to redirect the request to the authentication entry point of the unified user center when the authentication credential is not carried in the request, and to return an access request carrying the authentication credential after the user completes the authentication. The credential verification module is used to extract the authentication credentials through the Servlet filter and send a verification request to the verification interface of the unified user center. The session creation module is used to receive the verification response returned by the unified user center. If the verification is successful, a local user session is created in the supplier system based on the user information in the verification response. The state synchronization module is used to associate the authentication credentials with the session identifier of the local user session and store them in a distributed cache, and return the authentication credentials to the user's browser via a cookie; The request permission module is used to allow the access request to the business logic layer of the supplier system.

10. An electronic device, characterized in that, include: Memory and processor; Memory: Used to store computer programs; Processor: for executing the computer program to implement the steps of the method for rapid access to the user center by the supplier system as described in any one of claims 1-8.

Images