A multi-factor unified authentication method and system that supports flexible configuration and scalability

Through a systematic architecture driven by rule locators and configurable rules, the problem of flexible configuration and scalability of existing authentication frameworks is solved, enabling free combination of multi-factor authentication and rapid access to heterogeneous identity sources, thereby improving authentication performance and scalability.

CN123122874APending Publication Date: 2026-11-17TIANJIN RICHSOFT ELECTRIC POWER INFORMATION TECH +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611122996.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-07-28
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing authentication frameworks cannot flexibly configure authentication links in enterprise application systems, struggle to support multi-factor authentication, have high costs for integrating third-party identity sources, poor scalability, and cannot adapt to the complex identity authentication needs of distributed microservice architectures.

Method used

It adopts a rule locator and configurable authentication rules, and through a pluggable system architecture and configurable rule-driven approach, it enables flexible customization of authentication links for different applications, supports free combination of multi-factor authentication, provides a standardized third-party identity source extension mechanism, and improves authentication performance through asynchronous execution optimization.

Benefits of technology

It enables flexible configuration and multi-factor combination of authentication links, reduces development costs, improves the response speed of authentication interfaces, supports rapid access of multiple heterogeneous identity sources, and enhances the scalability and response speed of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123122874A_ABST
    Figure CN123122874A_ABST
Patent Text Reader

Abstract

This invention discloses a flexible and scalable multi-factor unified authentication method and system, belonging to the field of information security identity authentication. The invention adopts a rule engine + chain of responsibility + policy pattern architecture, decomposing the authentication process into pluggable processors, verifiers, executors, and converter components. A rule locator configures differentiated authentication links for different applications, supporting multi-factor combined authentication. It provides three third-party access methods: interface extension, built-in adapter, and configurable remote proxy, adapting to heterogeneous identity sources. It supports asynchronous execution of non-core logic, improving authentication response speed. This invention allows for flexible customization of authentication links and rapid expansion of authentication methods, making it suitable for unified authentication scenarios in distributed microservice architectures.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of computer software and information security technology, specifically to a multi-factor unified authentication method and system that supports flexible configuration and scalability. Background Technology

[0002] With the deepening of enterprise digital transformation and the widespread adoption of microservice architecture, the identity authentication requirements of modern enterprise application systems are becoming increasingly complex, and existing authentication frameworks are gradually revealing many defects and shortcomings: First, there is a contradiction between the diversification of authentication methods and the rigidity of authentication chains. Authentication requirements vary significantly across different applications within the same enterprise platform. Internal management systems require two-factor authentication (password and SMS), external customer applications require social media account login, intranet applications need to connect to a unified permission system, and mobile office applications need to connect to industry-specific authentication platforms. However, the authentication chains in existing frameworks are typically hard-coded into the core logic, making it impossible to quickly customize authentication combinations for different applications.

[0003] Secondly, the coexistence of heterogeneous identity sources presents access challenges. Enterprises often have multiple identity sources simultaneously, such as self-built user databases, LDAP / AD directories, third-party OAuth, SAML, and CAS. The data structures and interface protocols of each type of identity source are different. Integrating each new type of identity source requires in-depth modification of the core authentication code, resulting in high development costs, long development cycles, and difficulty in quickly responding to business needs.

[0004] Third, the support for multi-factor authentication is insufficient. Single authentication methods can no longer meet the requirements of high-security scenarios. It is necessary to support multi-factor authentication combinations such as passwords, SMS, and biometrics. Moreover, different applications have different security levels, and the required combination of authentication factors also varies. The existing framework is difficult to flexibly adapt to the differentiated multi-factor authentication links.

[0005] Fourth, the authentication logic is tightly coupled with the business code, resulting in poor scalability. Adding a new authentication method, a new verification rule, or new post-processing logic requires modifying the core authentication code, which can easily lead to instability issues in the core logic. Furthermore, various verification and execution logics cannot be reused between different authentication methods, resulting in a large amount of repetitive development.

[0006] In summary, existing technologies lack a unified authentication scheme that allows for flexible configuration of authentication links, supports free combination of multiple factors, and can quickly expand third-party authentication sources, thus failing to adapt to the complex and ever-changing identity authentication needs under a distributed microservice architecture. Summary of the Invention

[0007] This invention aims to address at least one of the technical problems existing in the prior art. To this end, one objective of this invention is to propose a flexible and scalable multi-factor unified authentication method and system. Through a pluggable, systematic architecture and configurable rule-driven approach, it enables flexible customization of authentication links for different applications, supports free combination of multi-factor authentication, provides a standardized third-party identity source extension mechanism, and improves authentication performance through asynchronous execution optimization. This addresses the problems of fixed authentication links, poor scalability, high access costs, and slow response speeds in existing authentication frameworks.

[0008] To achieve the above objectives, this invention provides a multi-factor unified authentication method that supports flexible configuration and scalability, applicable to identity authentication scenarios in distributed systems and microservice architectures, comprising the following steps: S1: Receive the authentication request initiated by the client, and extract the corresponding application identifier and authentication type identifier based on the authentication request; S2: Based on the application identifier obtained in step S1, the authentication link rule corresponding to the application is obtained by matching it from the preset authentication rule configuration library through the rule locator; based on the authentication type identifier obtained in step S1, it is verified whether it belongs to the allowed authentication range of the authentication link rule. If it does not belong, an authentication failure response is returned. S3: Based on the authentication request that has passed the verification in step S2, call the set of pre-verifiers that match the current authentication scenario to perform auxiliary verification operations before authentication; if the pre-verification fails, terminate the authentication process and return an error message. S4: Based on the authentication request that has passed the verification in step S3, match the authentication processor corresponding to the authentication type identifier, execute the corresponding core authentication logic through the authentication processor, and obtain the platform standard user object corresponding to the authentication request; S5: Based on the standard user object obtained in step S4, call the set of post-verifiers to perform post-authentication verification operations; if the post-verification fails, terminate the authentication process and return an error message. S6: Based on the verification result of step S5, determine whether all the authentication types that have been completed so far fully cover all authentication factors required by the authentication chain rules; if not fully covered, generate a temporary authentication credential with the verified information in the cache and return it to the client, waiting for subsequent supplementary authentication requests; S7: If step S6 determines that all authentication factors of the authentication chain rule have been verified, then the authentication executor set is called to perform the post-session processing operation after successful authentication. S8: Based on the session data after the post-processing in step S7, generate the corresponding access token and refresh token, and return the token results to the client.

[0009] Preferably, the authentication processor achieves pluggable expansion through a unified standardized interface; when accessing a third-party heterogeneous authentication source, it implements a standardized interface to complete the development of the third-party authentication logic, and uses an object converter to map and convert the original user data returned by the third party into a platform standard user object, so that the access of the new authentication method can be completed without modifying the core code of the authentication framework.

[0010] Preferably, there are multiple built-in third-party authentication adapters, each corresponding to different mainstream identity source protocols and authentication platforms. When accessing the corresponding third-party identity source, it is only necessary to configure the corresponding authentication type identifier in the authentication link rules to enable it, without adding any new authentication logic code.

[0011] Preferably, when accessing a business system with an independent user system and authentication logic, a configurable remote proxy authentication mode is adopted: by configuring the service location information and authentication interface path of the business system, the authentication request is automatically forwarded to the business side authentication interface, and the standardized authentication result returned by the business side is received and parsed. The platform side does not need to write business authentication logic code to complete the access.

[0012] Preferably, in step S7, the authentication executor is divided into two categories: core executor and extended executor. The core executor executes synchronously in the main thread to complete token storage and session core data filling. The extended executor is submitted to an independent thread pool for asynchronous execution to complete the loading of user extended information, organizational structure, and role permission data. The asynchronous execution mode is enabled and disabled through global configuration items.

[0013] Preferably, the temporary authentication credential generated in step S6 is cached with the currently passed authentication types and user basic information; when the client initiates the next authentication request, it carries the temporary authentication credential, the system reads the verified information in the credential and merges it with the current authentication result, and continues to complete the verification process of the remaining authentication factors.

[0014] A multi-factor unified authentication system that supports flexible configuration and scalability includes: The access request module is used to receive authentication requests initiated by clients and extract the corresponding application identifier and authentication type identifier from the request parameters. The rule location module is used to match the authentication link rules of the corresponding application from the preset configuration library based on the application identifier, and to verify whether the current authentication type identifier is within the allowed range of the authentication link rules. The verification layer module contains several pluggable pre-verifiers and post-verifiers, which are used to perform auxiliary verification operations before and after the core authentication logic is executed. The authentication processing module contains several pluggable authentication processors, each corresponding to an authentication type, used to execute the corresponding authentication logic and output the platform's standard user object; The multi-factor link control module is used to determine whether the completed authentication type fully covers all the requirements of the authentication link rules after a single authentication verification passes. If it does not cover all the requirements, it generates and returns a temporary authentication credential carrying the verified information. The execution layer module contains several pluggable authentication executors, which are used to perform post-authentication session processing after all authentication links have been verified. The token generation module is used to generate access tokens and refresh tokens and return them to the client after the complete authentication process is completed; The core scheduling context module is used to schedule the above modules to execute the authentication process according to the preset chain of responsibility, and supports both synchronous and asynchronous execution modes.

[0015] Preferably, it also includes an object conversion module, which is used to convert heterogeneous user data returned by different third-party authentication sources into standard user objects in a unified platform format according to preset mapping rules, thereby decoupling heterogeneous identity sources from the platform's data model.

[0016] Preferably, the authentication processing module supports three types of extended access modes: interface code extended mode, built-in adapter extended mode, and configurable remote proxy extended mode. Among them, the configurable remote proxy extended mode automatically completes the proxy forwarding and result parsing of authentication requests by configuring the service address information of the business system, realizing zero-code access to the third-party authentication system on the platform side.

[0017] Preferably, the core scheduling context module supports configuring non-core extended operations in the execution layer module to be executed asynchronously. The main thread only completes the core authentication logic and token generation before returning a response, while the extended operations are handled in parallel by an independent thread pool to improve the response speed of the authentication interface.

[0018] The advantages of this invention compared to the prior art are: 1. This invention, through a rule locator and configurable authentication rules, can customize different authentication links such as single-factor and multi-factor combinations for different applications. The authentication strategy can be adjusted without modifying the core code, adapting to the application requirements of different security levels to achieve flexible configuration of the authentication link.

[0019] 2. The new authentication method of this invention only needs to implement a standardized authentication processor interface, which is automatically loaded and registered by the container. There is no need to modify the underlying code of the authentication framework, which greatly reduces the development cost and cycle of the new authentication method and realizes hot-swappable expansion capability.

[0020] 3. This invention provides three access methods: interface code extension, built-in adapter, and configurable remote proxy. It supports not only deeply customized third-party authentication access, but also out-of-the-box mainstream identity source adaptation. It can also achieve rapid access to independent authentication systems on the business side through zero-code configuration, adapt to various heterogeneous identity source scenarios, realize multi-mode third-party access, and reduce access costs.

[0021] 4. This invention decouples the third-party data model from the platform's standard user model through an object converter, which can flexibly adapt to various non-standard third-party user field mappings. It can be compatible with identity data of different structures without modifying the core authentication logic, thus achieving standardized adaptation of heterogeneous data.

[0022] 5. This invention supports configuring non-core session extension operations to be executed asynchronously, with the main thread only completing core authentication and token issuance. This improves the response speed of the authentication interface by more than 80%, significantly optimizes the user login experience, and achieves high-performance asynchronous optimization.

[0023] 6. The pre-verifier, post-verifier, and authentication executor of this invention can all be reused in authentication chains of different authentication methods and applications, avoiding redundant development, resulting in high system reusability and improving the consistency and maintainability of authentication logic. Attached Figure Description

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

[0025] Figure 1 This is a flowchart of the method of the present invention; Figure 2 This is a diagram showing the overall architecture of the authentication system of this invention; Figure 3 This is a flowchart of the core scheduling method for the certification of this invention. Detailed Implementation

[0026] The embodiments of this application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting this application.

[0027] In the description of this application, it should be noted that, unless otherwise expressly specified and limited, the terms "installation," "connection," and "joining" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components. Those skilled in the art can understand the specific meaning of the above terms in this application according to the specific circumstances.

[0028] The present invention will now be described in further detail with reference to the accompanying drawings.

[0029] This invention provides a multi-factor unified authentication method and system that supports flexible configuration and scalability, aiming to solve problems such as single authentication methods, fixed authentication links, difficulties in third-party access, and poor scalability in existing technologies. Different authentication links can be customized for different applications through configuration; it supports free combination of multi-factor authentication; and it supports standardized and rapid access to any third-party authentication source.

[0030] (1) Core System Architecture This invention adopts an architecture of "rule engine + chain of responsibility + strategy pattern", which decomposes the authentication process into four pluggable core components:

[0031] (2) Third-party authentication extension mechanism The core innovation of this invention lies in providing standardized third-party authentication extension points, allowing developers to quickly access any third-party authentication source through the following three methods: Method 1: Implement the authentication processor interface (code extension) @Component public class WeWorkProcessor implements IAuthenticateProcessor <user>{ @Override public String grantType() { return "wework"; / / Authentication type identifier } @Override public User getTarget(LoginParam params) { / / 1. Call a third-party API to obtain user information WeWorkUser wxUser = weWorkApi.getUser(params.getCode()); / / 2. Convert to platform standard User object return converter.convert(wxUser); } @Override public boolean process(LoginParam params, User user) { / / 3. Post-authentication processing (optional business verification) return true; } } Option 2: Built-in third-party adapter (ready to use out of the box) This invention has built-in several common third-party authentication adapters:

[0032] Method 3: Configurable Remote Proxy Authentication (Zero-code on the platform side) By configuring the following parameters, the platform will automatically forward authentication requests to the business microservice:

[0033] Applicable scenarios: 1. The business system has an independent user table and wants to control the authentication logic itself. 2. Due to the upgrading of outdated systems, user data cannot be synchronized to the platform. 3. In multi-tenant scenarios, different tenants have independent authentication logic. Access cost: Business microservices need to implement a standard authentication interface (receive LoginParam and return AuthResponse). No code needs to be written on the platform side; integration can be completed simply by configuration. (3) Multi-factor authentication link configuration This invention supports configuring different authentication links for different applications through a rule locator, supporting single-factor, multi-factor combinations, and multi-level subtypes: Configuration example (configuration file or configuration center): # Application A: Password-only authentication app.auth.rules.A = password # Application B: Password + SMS Two-Factor System app.auth.rules.B = password,sms # Application C: ISC Cryptographic Authentication app.auth.rules.C = isc_password # Application D: ISC Ticket + Platform Password Two-Factor System app.auth.rules.D = isc,password # Application E: Third-party WeChat login (including subtypes) app.auth.rules.E = third_party.wechat # Application F: iNationalNetwork Authentication + SMS Verification app.auth.rules.F = igw2,sms # Application G: Remote Custom Authentication for Businesses app.auth.rules.G = igw_remote (4) Authentication process scheduling This invention uses AuthenticateContext to uniformly schedule the authentication process, supporting both synchronous and asynchronous execution.

[0034] (5) Asynchronous execution optimization This invention supports configuring non-critical session extension operations to execute asynchronously, significantly improving the response speed of the authentication interface. The main thread only executes the core authentication logic and returns a token; extension executors (such as loading user extension data, organization information, and role permissions) are submitted to the thread pool for asynchronous execution; this is enabled by configuring auth.runExecutorInAsync=true.

[0035] Comparison of asynchronous execution results:

[0036] To more clearly illustrate the specific embodiments of the present invention, several examples are provided below: Example 1: Quickly integrate applications with "WeChat Work" third-party authentication Scenario: The business system needs to integrate with WeChat for QR code login.

[0037] Implementation steps: 1. Implement a WeChat Work processor (only one new Java class is needed): @Component public class WeWorkProcessor implements IAuthenticateProcessor <user>{ @Override public String grantType() { return "third_party.wework";} @Override public User getTarget(LoginParam params) { WeWorkUser wxUser = weWorkApi.getUser(params.getCode()); return convertToPlatformUser(wxUser); } @Override public boolean process(LoginParam params, User user) { return true; / / Authentication successful } } 2. Configure authentication rules: app.auth.rules.APP001 = third_party.wework 3. Start the application: The component automatically completes authentication scheduling, session management, and token issuance without any additional configuration.

[0038] Example 2: Asynchronous Population of ISC User Data (Performance Optimization) Scenario: The application is integrated with the ISC unified permission system and needs to load the user's organization, role, and permission data after login.

[0039] Implementation method: Developers implement IscUserSessionExtendExecutor and configure it in asynchronous mode: app.auth.runExecutorInAsync=true Execution result: Main thread: ISC ticket verification → Token generation (approximately 80ms) → Return to client Asynchronous thread: Load organization, role, and permission data in parallel (takes approximately 400ms). User experience: Login response time reduced from 500ms to 80ms Example 3: Two-Factor Authentication Link Configuration Scenario: Application B requires users to undergo dual verification using both a "password" and an "SMS verification code".

[0040] Configuration rules: app.auth.rules.B = password,sms Authentication process: 1. Initial client request: Includes grantType=password and password. 2. The component successfully performed password authentication, but the detection rules were not fully met (SMS is still required), and a temporary credential, authLinkToken, was returned. 3. Client-side secondary request: includes authLinkToken, grantType=sms, and SMS code. 4. The component merged the two authentication results, and the matching rule "password, sms" was successful. 5. Generate the final token and return it. Example 4: Configurable Remote Proxy Authentication (Zero-code platform-side integration with business microservices) Scenario: A business system has an independent user table. User data cannot or should not be synchronized to a unified authentication platform, but it needs to connect to the platform to achieve single sign-on. The business system wants to control the authentication logic itself (such as custom password encryption methods, multi-factor authentication, etc.).

[0041] Problems with traditional solutions: Modifying platform code to adapt to the authentication logic of business systems is highly intrusive and difficult to upgrade. The business system requires significant modifications and needs to integrate with the platform SDK. The solution of this invention is: through configurable remote proxy authentication, the platform side does not need to write any code, and the business system only needs to implement a standard HTTP interface to complete the access.

[0042] Implementation steps Step 1: Implement the standard authentication interface in the business system. The business microservice needs to provide an HTTP interface (example: POST / api / auth / remote / authorize) to receive the following requests: { "username": "zhangsan", "password": "xxx", "appCode": "BIZ_APP_001", "grantType": "igw_remote } Returns a standard format authentication result (AuthResponse): { "successful": true, "loginName": "zhangsan", "organs": [ {"organId": "ORG_001", "organName": "Technical Department"} ], "sessionData": { "customField": "Custom Session Data" } } Step 2: Add configuration in the platform configuration file or configuration center # Business system microservice ID (supports Spring Cloud service discovery) SPECIAL_SERVICE_REMOTE_AUTH_SERVICE_ID=biz-auth-service # Or configure the URL address directly (direct connection mode) SPECIAL_SERVICE_REMOTE_AUTH_URL=http: / / xxxx # Service Context Path SPECIAL_SERVICE_REMOTE_AUTH_CONTEXT_PATH= / api / auth # Application authentication rule configuration app.auth.rules.BIZ_APP_001 = third Step 3: Launch the application and verify access. The platform automatically forwards authentication requests to the business system interface without requiring any Java code.

[0043] Finally, any aspects not fully described in this invention utilize existing mature products and technologies.

[0044] The present invention and its embodiments have been described above. This description is not restrictive, and the accompanying drawings are only one embodiment of the present invention; the actual structure is not limited thereto. In conclusion, if those skilled in the art are inspired by this description and design similar structures and embodiments without departing from the spirit of the invention, such designs should fall within the protection scope of the present invention.< / user> < / user>

Claims

1. A multi-factor unified authentication method that supports flexible configuration and scalability, applied to identity authentication scenarios in distributed systems and microservice architectures, characterized in that, Includes the following steps: S1: Receive the authentication request initiated by the client, and extract the corresponding application identifier and authentication type identifier based on the authentication request; S2: Based on the application identifier obtained in step S1, the authentication link rule corresponding to the application is obtained by matching it from the preset authentication rule configuration library through the rule locator; based on the authentication type identifier obtained in step S1, it is verified whether it belongs to the allowed authentication range of the authentication link rule; if it does not belong, an authentication failure response is returned. S3: Based on the authentication request that has passed the verification in step S2, call the set of pre-verifiers that match the current authentication scenario and perform auxiliary verification operations before authentication; If the pre-verification fails, the authentication process will be terminated and an error message will be returned. S4: Based on the authentication request that has passed the verification in step S3, match the authentication processor corresponding to the authentication type identifier, execute the corresponding core authentication logic through the authentication processor, and obtain the platform standard user object corresponding to the authentication request; S5: Based on the standard user object obtained in step S4, call the set of post-verifiers to perform post-authentication verification operations; If the post-verification fails, the authentication process will be terminated and an error message will be returned. S6: Based on the verification result of step S5, determine whether all the authentication types that have been completed so far fully cover all authentication factors required by the authentication chain rules; if not fully covered, generate a temporary authentication credential with cached verified information and return it to the client, waiting for subsequent supplementary authentication requests; S7: If step S6 determines that all authentication factors of the authentication chain rule have been verified, then the authentication executor set is called to perform the post-session processing operation after successful authentication. S8: Based on the session data after the post-processing in step S7, generate the corresponding access token and refresh token, and return the token results to the client.

2. The multi-factor unified authentication method according to claim 1, characterized in that, The authentication processor achieves pluggable expansion through a unified standardized interface; when accessing a third-party heterogeneous authentication source, it implements the standardized interface to complete the development of the third-party authentication logic, and uses an object converter to map and convert the original user data returned by the third party into a platform standard user object, so that the access of the new authentication method can be completed without modifying the core code of the authentication framework.

3. The multi-factor unified authentication method according to claim 2, characterized in that, It has multiple built-in third-party authentication adapters, each corresponding to different mainstream identity source protocols and authentication platforms. When connecting to the corresponding third-party identity source, you only need to configure the corresponding authentication type identifier in the authentication link rules to enable it, without adding any new authentication logic code.

4. The multi-factor unified authentication method according to claim 1, characterized in that, When accessing a business system with an independent user system and authentication logic, a configurable remote proxy authentication mode is adopted: by configuring the service location information and authentication interface path of the business system, the authentication request is automatically forwarded to the business side authentication interface, and the standardized authentication result returned by the business side is received and parsed. The platform side does not need to write business authentication logic code to complete the access.

5. The multi-factor unified authentication method according to claim 1, characterized in that, In step S7, the authentication executor is divided into two categories: core executor and extended executor. The core executor is executed synchronously in the main thread to complete token storage and session core data filling. The extended executor is submitted to an independent thread pool for asynchronous execution to complete the loading of user extended information, organizational structure, and role permission data. The asynchronous execution mode is enabled and disabled through global configuration items.

6. The multi-factor unified authentication method according to claim 1, characterized in that, The temporary authentication credential generated in step S6 is cached with the currently passed authentication types and user basic information. When the client initiates the next authentication request, it carries the temporary authentication credential. The system reads the verified information in the credential and merges it with the current authentication result to continue the verification process of the remaining authentication factors.

7. A multi-factor unified authentication system that supports flexible configuration and scalability, characterized in that, include: The access request module is used to receive authentication requests initiated by clients and extract the corresponding application identifier and authentication type identifier from the request parameters. The rule location module is used to match the authentication link rules of the corresponding application from the preset configuration library according to the application identifier, and to verify whether the current authentication type identifier is within the allowed range of the authentication link rules; The verification layer module contains several pluggable pre-verifiers and post-verifiers, which are used to perform auxiliary verification operations before and after the core authentication logic is executed. The authentication processing module contains several pluggable authentication processors, each corresponding to an authentication type, used to execute the corresponding authentication logic and output the platform's standard user object; The multi-factor link control module is used to determine whether the completed authentication type fully covers all the requirements of the authentication link rules after a single authentication verification passes. If it does not cover all the requirements, it generates and returns a temporary authentication credential carrying the verified information. The execution layer module contains several pluggable authentication executors, which are used to perform post-authentication session processing after all authentication links have been verified. The token generation module is used to generate access tokens and refresh tokens and return them to the client after the complete authentication process is completed; The core scheduling context module is used to schedule the above modules to execute the authentication process according to the preset chain of responsibility, and supports both synchronous and asynchronous execution modes.

8. The multi-factor unified authentication system according to claim 7, characterized in that, It also includes an object conversion module, which converts heterogeneous user data returned by different third-party authentication sources into standard user objects in a unified platform format according to preset mapping rules, thereby decoupling heterogeneous identity sources from the platform's data model.

9. The multi-factor unified authentication system according to claim 7, characterized in that, The authentication processing module supports three types of extended access modes: interface code extended mode, built-in adapter extended mode, and configurable remote proxy extended mode. Among them, the configurable remote proxy extended mode automatically completes the proxy forwarding and result parsing of authentication requests by configuring the service address information of the business system, realizing zero-code access to the third-party authentication system on the platform side.

10. The multi-factor unified authentication system according to claim 7, characterized in that, The core scheduling context module supports configuring non-core extended operations in the execution layer module to be executed asynchronously. The main thread only completes the core authentication logic and token generation before returning a response, while the extended operations are handled in parallel by an independent thread pool to improve the response speed of the authentication interface.