Application system integration method and device, equipment and medium

Abstract

The invention provides an application system integration method and device, equipment and a medium, and relates to the technical field of computer application, the method is applied to a service platform, the service platform comprises a first front-end system and a first rear-end system, the first rear-end system comprises a first security framework, and the method comprises the following steps: when it is determined that a user successfully logs in the service platform, determining that the user logs in the service platform; generating a main system token; in response to a trigger operation initiated by a user on the first front-end system, performing micro-service security authentication based on the first security framework, and generating a subsystem token corresponding to the target to-be-integrated system; the main system token is sent to the target to-be-integrated system, so that the target to-be-integrated system carries out user verification according to the main system token, and a verification result is fed back; and when the verification result is determined to be successful, sending the subsystem token to a back-end system of the target to-be-integrated system, so that the back-end system performs identity verification on the subsystem token, and provides an interactive response service after the identity verification operation is completed.

Description

Technical Field

[0001] The present application relates to the field of computer application technology, and in particular to an application system integration method, an application system integration device, an electronic device, and a machine-readable storage medium. Background Art

[0002] In the process of rapid development, many large enterprises have accumulated various application systems that were launched at different times and adopted different technical architectures. In order to eliminate information islands, optimize resource allocation, improve system performance and reduce maintenance costs, and provide users with more efficient, convenient and reliable services, enterprises usually integrate these systems into a unified and coordinated platform through technical and management means.

[0003] However, during the application system integration process, various problems may occur, affecting the integration effect and failing to meet user expectations. For example, differences in technology stacks and protocol stacks between different application systems may lead to integration failures, inability to guarantee the security, integrity and availability of systems and data after integration, data synchronization and consistency issues after integration, and increased system maintenance work. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide an application system integration method, an application system integration device, equipment and medium to solve the problems of high complexity and cost and low security of application system integration in the prior art.

[0005] In order to achieve the above-mentioned object, the first aspect of the present application provides an application system integration method, which is applied to a service platform, wherein the service platform includes a first front-end system and a first back-end system with front-end and back-end separations, and a menu of a system to be integrated is displayed in the first front-end system; the first back-end system includes a first security framework; the system to be integrated includes a front-end system and a back-end system with front-end and back-end separations, and the first front-end system includes the front-end system of the system to be integrated; the method includes: When it is determined that the user has successfully logged into the service platform, a main system token is generated; wherein the main system token includes user information; In response to a trigger operation initiated by a user on a menu of the target system to be integrated in a preset display area of ​​the first front-end system, microservice security authentication is performed based on the first security framework to generate a subsystem token corresponding to the target system to be integrated; Sending the main system token to the target system to be integrated, so that the target system to be integrated performs user verification according to the main system token and feeds back the verification result; When it is determined that the verification result is successful, the subsystem token is sent to the backend system of the target system to be integrated, so that the backend system authenticates the subsystem token and provides an interactive response service after completing the authentication operation.

[0006] In an embodiment of the present application, the first backend system includes a microservice security authentication user management interface and an identity supply interface; the first security framework adopts a security framework based on the OAuth protocol, and the first security framework includes a security authentication service interface; the microservice security authentication user management interface and the security authentication service interface are both used to generate a subsystem token, and the identity supply interface is used to provide user information to the system to be integrated.

[0007] In an embodiment of the present application, microservice security authentication is performed based on the first security framework to generate a subsystem token corresponding to the target system to be integrated, including: The target system to be integrated is subjected to microservice security authentication through the microservice security authentication user management interface and the security authentication service interface to generate the subsystem token.

[0008] In an embodiment of the present application, the method further includes: Determine whether the backend system of the target system to be integrated includes a Shiro-based security framework; If so, obtaining a token issued by the security framework based on the main system token; Performing microservice security authentication based on the first security framework and generating a subsystem token corresponding to the target system to be integrated includes: Determine whether the backend system of the target system to be integrated includes a Shiro-based security framework; If so, the target system to be integrated is subjected to microservice security authentication through the microservice security authentication user management interface and the security authentication service interface to obtain an authentication result, and based on the main system token, the token issued by the security framework is obtained, and the subsystem token is generated according to the authentication result and the token issued by the security framework; If not, microservice security authentication is performed on the target system to be integrated through the microservice security authentication user management interface and the security authentication service interface to generate the subsystem token.

[0009] In the embodiment of the present application, while performing microservice security authentication based on the first security framework and generating a subsystem token corresponding to the target system to be integrated, the method further includes: Generate an access request to the target system to be integrated, and send the access request to the gateway of the service platform; Mapping the access request to the target system to be integrated through the gateway of the service platform, and performing a conversion proxy operation on the access request through the gateway of the service platform, so that the target system to be integrated can receive the access request and add the main system token to the access request; Sending the main system token to the target system to be integrated includes: An access request including the main system token is sent to the target system to be integrated to log in to the target system to be integrated.

[0010] In an embodiment of the present application, the method further includes: According to the preset color scheme, adjust the color of the front-end page in the front-end system of the integrated system.

[0011] In an embodiment of the present application, the method further includes: The validity periods of the main system token and the subsystem token are controlled by the first security framework.

[0012] A second aspect of the present application provides an application system integration device, which is configured on a service platform, wherein the service platform includes a first front-end system and a first back-end system with front-end and back-end separations, and a menu of a system to be integrated is displayed on the first front-end system; the first back-end system includes a first security framework; the system to be integrated includes a front-end system and a back-end system with front-end and back-end separations, and the first front-end system includes the front-end system of the system to be integrated; the device includes: A main system token generation module, used to generate a main system token when it is determined that the user has successfully logged into the service platform; wherein the main system token includes user information; A subsystem token generation module, configured to respond to a trigger operation initiated by a user on a menu of a target system to be integrated in a preset display area of ​​the first front-end system, perform microservice security authentication based on the first security framework, and generate a subsystem token corresponding to the target system to be integrated; A verification result acquisition module, used for sending the main system token to the target system to be integrated, so that the target system to be integrated performs user verification according to the main system token and feeds back the verification result; The system integration control module is used to send the subsystem token to the back-end system of the target system to be integrated when it is determined that the verification result is successful, so that the back-end system can authenticate the subsystem token and provide interactive response services after completing the authentication operation.

[0013] The third aspect of the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the application system integration method described in the first aspect when executing the computer program.

[0014] A fourth aspect of the present application provides a machine-readable storage medium having instructions stored thereon, which, when executed by a processor, configures the processor to execute the application system integration method described in the first aspect above.

[0015] The application system integration method, device, equipment and medium provided in this application ensure the security of the front desk of the system to be integrated through multi-layer protection mechanisms such as dual tokens, unified security authentication services and microservice security authentication user management. When new users and their organizations need to be added, they only need to be added on the service platform and synchronized to the subsystem without having to be added again in each subsystem. The service platform provides similar master data and its synchronization functions, which can save operation and maintenance time and operation and maintenance costs. Through this method, the depth of system integration can be met, the security of the integrated system can be guaranteed, the complexity of system integration can be reduced, and the personnel investment cost of system integration can be reduced.

[0016] Other features and advantages of the embodiments of the present application will be described in detail in the subsequent specific implementation section. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The accompanying drawings are used to provide a further understanding of the embodiments of the present application and constitute a part of the specification. Together with the following specific implementations, they are used to explain the embodiments of the present application, but do not constitute a limitation on the embodiments of the present application. In the accompanying drawings: Figure 1 The following is a schematic diagram showing a flow chart of an application system integration method according to an embodiment of the present application; Figure 2 A flowchart schematically illustrates an application example of an embodiment of the present application; Figure 3 The structure block diagram of the application system integration device of the embodiment of the present application is schematically shown; Figure 4 The internal structure diagram of the computer device according to the embodiment of the present application is schematically shown.

[0018] Description of Reference Numerals A01-processor; A02-network interface; A03-internal memory; A04-display screen; A05-input device; A06-non-volatile storage medium; B01-operating system; B02-computer program. DETAILED DESCRIPTION

[0019] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the specific implementation methods described herein are only used to illustrate and explain the embodiments of the present application, and are not used to limit the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0020] It should be noted that if the embodiments of the present application involve directional indications (such as up, down, left, right, front, back, etc.), such directional indications are only used to explain the relative position relationship, movement status, etc. between the components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.

[0021] In addition, if there are descriptions involving "first", "second", etc. in the embodiments of the present application, the descriptions of "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or suggesting their relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in the field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by this application.

[0022] In related technologies, computer application systems based on microservice architecture decompose large, complex monolithic applications into multiple small, independent services, each of which runs in an independent process. Services are usually deployed independently using an automated deployment mechanism, and can be expanded and updated independently. Each service communicates with each other through lightweight communication protocols (such as HTTP, REST, and gRPC).

[0023] In a computer application system based on a microservice architecture, in order to better organize and manage the system, the system is usually divided into a front-end system and a back-end system according to the system functions and user roles. The front-end and back-end systems can be developed and tested independently, which helps to clarify the responsibility boundaries of the system, improve the maintainability and scalability of the system, and make the division of labor of developers clearer. Among them, the front-end system is mainly responsible for interacting with users, providing user interfaces (UI) and processing user requests. It can be a website, mobile application, desktop application or other forms of interface. The front-end system needs to respond quickly and display data, and obtain the required information by exchanging data with the back-end system. The back-end system is responsible for processing business logic and data storage, and usually includes multiple microservices, each of which has specific business functions. The back-end system communicates with the front-end system through APIs and interacts through HTTP requests. The back-end system receives requests from the front-end system and returns responses. The front-end system focuses on providing a good user experience on the basis of ensuring data security and network security, and usually needs to adapt to different devices and screen sizes. In some front-end frameworks, when communicating with the back-end system to obtain or send data, it is often necessary to share or optimize the front-end routing, component status and resources.

[0024] The depth of application system integration is positively correlated with its complexity and cost. It is necessary to find a balance based on user needs, which should not only meet business needs and technical requirements, but also ensure the stability, security and maintainability of the integrated system, while keeping costs within an acceptable range.

[0025] The depth of application system integration is positively correlated with its complexity and cost. Therefore, it is necessary to find a balance based on user needs, which should not only meet business and technical requirements, but also ensure the stability, security and maintainability of the integrated system, while controlling costs within a reasonable range.

[0026] In view of the complexity, high cost and low security of application system integration in the related art, the present application provides an application system integration method, device, equipment and medium. The application system integration method, device, equipment and medium provided in the present application are described in detail through specific examples and implementation methods in conjunction with the accompanying drawings.

[0027] Figure 1 The flowchart of the application system integration method of the embodiment of the present application is schematically shown. Figure 1As shown, in one embodiment of the present application, an application system integration method is provided, which is applied to a service platform, wherein the service platform includes a first front-end system and a first back-end system with separated front-end and back-end, and a menu of the system to be integrated is displayed on the first front-end system; the first back-end system includes a first security framework; the system to be integrated includes a front-end system and a back-end system with separated front-end and back-end, and the first front-end system includes the front-end system of the system to be integrated.

[0028] Among them, the first back-end system includes a microservice security authentication user management interface and an identity supply interface; the first security framework adopts a security framework based on the OAuth protocol, and the first security framework includes a security authentication service interface; the microservice security authentication user management interface and the security authentication service interface are both used to generate subsystem tokens, and the identity supply interface is used to provide user information to the system to be integrated.

[0029] In an embodiment of the present application, the method may include the following steps.

[0030] Step 100: When it is determined that the user has successfully logged into the service platform, a main system token is generated.

[0031] Wherein, the main system token includes user information.

[0032] Step 200, in response to a trigger operation initiated by a user on a menu of a target system to be integrated in a preset display area of ​​the first front-end system, microservice security authentication is performed based on the first security framework, and a subsystem token corresponding to the target system to be integrated is generated.

[0033] In a specific example, step 200 performs microservice security authentication based on the first security framework to generate a subsystem token corresponding to the target system to be integrated, including the following steps.

[0034] Step 210: Perform microservice security authentication on the target system to be integrated through the microservice security authentication user management interface and the security authentication service interface to generate the subsystem token.

[0035] In another specific example, step 200 performs microservice security authentication based on the first security framework to generate a subsystem token corresponding to the target system to be integrated, including the following steps.

[0036] Step 210: determine whether the backend system of the target system to be integrated includes a Shiro-based security framework.

[0037] Step 220: If it is determined that the back-end system of the target system to be integrated includes a security framework based on Shiro, microservice security authentication is performed on the target system to be integrated through the microservice security authentication user management interface and the security authentication service interface to obtain an authentication result, and based on the main system token, the token issued by the security framework is obtained, and the subsystem token is generated according to the authentication result and the token issued by the security framework; if it is determined that the back-end system of the target system to be integrated does not include a security framework based on Shiro, microservice security authentication is performed on the target system to be integrated through the microservice security authentication user management interface and the security authentication service interface to generate the subsystem token.

[0038] In addition, in the embodiment of the present application, while executing step 200, the method further includes the following steps: Generate an access request to the target system to be integrated, and send the access request to the gateway of the service platform; The access request is mapped to the target system to be integrated through the gateway of the service platform, and the access request is converted and proxy operated through the gateway of the service platform so that the target system to be integrated can receive the access request and add the main system token to the access request.

[0039] Step 300: Send the main system token to the target system to be integrated, so that the target system to be integrated performs user verification according to the main system token and feeds back the verification result.

[0040] In the embodiment of the present application, the specific operation of step 300 of sending the main system token to the target system to be integrated is: sending an access request including the main system token to the target system to be integrated to log in to the target system to be integrated.

[0041] Step 400, when it is determined that the verification result is successful, the subsystem token is sent to the backend system of the target system to be integrated, so that the backend system authenticates the subsystem token and provides an interactive response service after completing the authentication operation.

[0042] Optionally, in the embodiment of the present application, the method may further include: adjusting the color of the front-end page in the front-end system of the system to be integrated according to a preset color scheme.

[0043] The embodiment of the present application can effectively manage and control the visual effects of the interface through the preset color scheme, ensure the consistency of the visual style presented by the front-end pages of the service platform and its integrated system, and improve the user experience.

[0044] Optionally, in the embodiment of the present application, the method may further include: controlling the validity period of the main system token and the subsystem token through the first security framework.

[0045] Specifically, the validity of the main system token and the subsystem token is managed by the first security framework in the background. Once the main system token or the subsystem token expires, it will exit the service platform or the target system to be integrated.

[0046] The embodiment of the present application further improves the security of the service platform by setting the main system token and the subsystem token.

[0047] The following is an explanation of the application system integration method provided in the embodiment of the present application through a specific application example.

[0048] A certain integrated basic service platform (i.e. the service platform, referred to as the main system) has multiple integrated systems (i.e. the systems to be integrated, referred to as subsystems). Both the main system and the integrated systems use front-end and back-end separation technology and microservice development technology. The front-end and back-end services mainly involve two security architectures, Shiro and OAuth2.0, to protect the access security of microservices. The main system integrates each subsystem only by considering the integration of the front-end system and keeping the back-end system unchanged. At the same time, it needs to integrate the two security frameworks to ensure that the systems developed at different times and separated from the front-end and back-end can achieve system security integration, and solve the problems of multiple logins, multiple uses, and management and maintenance of chimney-style systems for users.

[0049] Specifically, the main page of the front-end system of the main system adopts IFrame framework technology, and the page frame is designed into different areas based on the VUE3ElementPlus Admin component. For example, the top of the page is the system title area, the left side of the page is the menu bar, and the right side of the page is the function display area. The front-end page of the subsystem is embedded in the function display area, and the identity supply interface and the identity authentication interface are designed to ensure that the main system can use the application functions of each subsystem normally after integrating the subsystem. The effect after integration is that there is only one front-end system, and the respective back-end systems remain unchanged, and their respective operations and maintenance do not interfere with each other.

[0050] like Figure 2 As shown, the specific steps for the main system to achieve subsystem integration are as follows: 1. Design a nested display area in the main system, add the front-end menu of the subsystem to be integrated to the main system, and authorize the menu in the main system.

[0051] 2. Design the UI color scheme in the main system, and adjust the color of the subsystem pages that need to be integrated according to the scheme to ensure that the front-end pages after the main system and subsystem are integrated have a unified color scheme.

[0052] 3. Design an identity provision interface in the background of the main system to provide detailed information about users and relevant organizational information. Design an identity authentication interface in the background of the subsystem to provide identity judgment and identity synchronization functions.

[0053] 4. Design OAuth2.0 microservice security authentication service in the main system to provide unified and secure authentication and authorization services for all microservices.

[0054] 5. Design microservice security authentication user management in the main system to implement account management of microservice access rights. The account and password for microservices and third parties to access the API interface of this main system can be dynamically configured. Accounts that are not configured will not be able to access all microservices of the main system.

[0055] 6. Users log in to the main system using user name, password and other technologies.

[0056] 7. Design single sign-on and unified identity authentication functions in the main system, and generate a main system token after the user successfully logs in①.

[0057] 8. The user clicks on the subsystem menu, and the main system generates a subsystem token② through gateway mapping and conversion proxy, and through the OAuth security authentication service interface and the microservice security authentication user management interface, and then the system automatically logs in to the subsystem.

[0058] In addition, for subsystems that use the Shiro security framework, it is also necessary to obtain user information through the main system token ①, and then use the user information to obtain the token issued by Shiro to generate the subsystem token ② to achieve automatic login and secure access to the subsystem.

[0059] 9. The subsystem calls the OAuth microservice security authentication service interface to verify the user token according to the subsystem's single sign-on verification rules①. After the verification is successful, the subsystem calls the OAuth microservice security authentication service interface again to obtain the token②. If the verification fails, an error is reported to the main system and the process ends.

[0060] 10. The subsystem calls the background identity authentication interface to determine the identity of the user of token ② and verify whether the user exists. If not, the identity provision interface of the main system is called to read the user information and related organizational information and synchronize them to the subsystem.

[0061] 11. The subsystem uses token ② to access the subsystem front-end functions normally and interact with the user.

[0062] 12. The validity of the main system token ① and subsystem token ② is managed by the security authentication Oauth service in the background. Once it expires, you need to exit the main system or subsystem.

[0063] It should be noted that in this application example, the same user logs in to the main system at a single sign-on, and the subsystem tokens② generated by clicking on different subsystem menus are different, to ensure that different subsystems are securely integrated into the main system. Oauth security authentication and identity provisioning interfaces are main system backend services, while identity authentication interfaces and security management Shiro are subsystem backend services. Security management Shiro is not necessary for the subsystem.

[0064] Through the above 12 steps, the subsystem with front-end and back-end separation based on microservice architecture can be integrated into the main system.

[0065] This diagram mainly shows the front-end functions of the main system and subsystems, as well as the process of users logging in to access the front-end functions of the subsystems after system integration.

[0066] It can be seen that the application system integration method provided by the embodiment of the present application ensures the security of the front desk of the system to be integrated through multi-layer protection mechanisms such as dual tokens, unified security authentication services, and microservice security authentication user management. When new users and their organizations need to be added, they only need to be added on the service platform and synchronized to the subsystem, without having to add them again in each subsystem. The service platform provides similar master data and its synchronization functions, which can save operation and maintenance time and costs.

[0067] In addition, through this method, the front-end developers of the subsystem only need to add an authentication interface and simply replace the page UI style to achieve integration with the platform, thereby maintaining the independence and logical integrity of the subsystem background. The senior developers of the subsystem do not need to invest a lot of time and energy to redevelop or modify the code to adapt to the platform, which saves the cost of system integration, simplifies the system integration process, and reduces the complexity of system integration.

[0068] Figure 1 FIG. 1 is a flow chart of an application system integration method in one embodiment. It should be understood that although Figure 1 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 1 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0069] Figure 3The structural block diagram of the application system integration device of the embodiment of the present application is schematically shown. Figure 3 As shown, in one embodiment of the present application, an application system integration device is provided, which is configured on a service platform, and the service platform includes a first front-end system and a first back-end system with separated front-end and back-end, and the menu of the system to be integrated is displayed on the first front-end system; the first back-end system includes a first security framework; the system to be integrated includes a front-end system and a back-end system with separated front-end and back-end, and the first front-end system includes the front-end system of the system to be integrated, and the device may include the following functional modules.

[0070] The main system token generation module is used to generate a main system token when it is determined that the user has successfully logged into the service platform. The main system token includes user information.

[0071] The subsystem token generation module is used to respond to the trigger operation initiated by the user on the menu of the target system to be integrated in the preset display area of ​​the first front-end system, perform microservice security authentication based on the first security framework, and generate a subsystem token corresponding to the target system to be integrated.

[0072] The verification result acquisition module is used to send the main system token to the target system to be integrated, so that the target system to be integrated performs user verification according to the main system token and feeds back the verification result.

[0073] The system integration control module is used to send the subsystem token to the back-end system of the target system to be integrated when it is determined that the verification result is successful, so that the back-end system can authenticate the subsystem token and provide interactive response services after completing the authentication operation.

[0074] In an embodiment of the present application, the first backend system includes a microservice security authentication user management interface and an identity supply interface; the first security framework adopts a security framework based on the OAuth protocol, and the first security framework includes a security authentication service interface; the microservice security authentication user management interface and the security authentication service interface are both used to generate a subsystem token, and the identity supply interface is used to provide user information to the system to be integrated.

[0075] In an embodiment of the present application, the subsystem token generation module may include: The first subsystem token generation unit is used to perform microservice security authentication on the target system to be integrated through the microservice security authentication user management interface and the security authentication service interface to generate the subsystem token.

[0076] In an embodiment of the present application, the subsystem token generation module may include: The framework determination unit is used to determine whether the backend system of the target system to be integrated includes a Shiro-based security framework.

[0077] The second subsystem token generation unit is used to perform microservice security authentication on the target system to be integrated through the microservice security authentication user management interface and the security authentication service interface when it is determined that the backend system of the target system to be integrated includes a Shiro-based security framework, obtain the authentication result, and based on the main system token, obtain the token issued by the security framework, and generate the subsystem token according to the authentication result and the token issued by the security framework.

[0078] The third subsystem token generation unit is used to perform microservice security authentication on the target system to be integrated through the microservice security authentication user management interface and the security authentication service interface to generate the subsystem token when it is determined that the backend system of the target system to be integrated does not include a Shiro-based security framework.

[0079] In the embodiment of the present application, the device further includes: The request generation module is used to generate an access request to the target system to be integrated, and send the access request to the gateway of the service platform.

[0080] A gateway mapping and conversion proxy module is used to map the access request to the target system to be integrated through the gateway of the service platform, and perform conversion proxy operations on the access request through the gateway of the service platform, so that the target system to be integrated can receive the access request and add the main system token to the access request.

[0081] In the embodiment of the present application, the verification result acquisition module includes: The request sending unit is used to send an access request including the main system token to the target system to be integrated, so as to log in to the target system to be integrated.

[0082] In the embodiment of the present application, the device further includes: The color matching adjustment module is used to adjust the color matching of the front-end pages in the front-end system of the system to be integrated according to a preset color matching scheme.

[0083] In the embodiment of the present application, the device further includes: A token management module is used to control the validity period of the main system token and the subsystem token through the first security framework.

[0084] Since the application system integration device provided in the embodiment of the present application is a virtual device corresponding to the application system integration method of the above embodiment, it can also solve the problems of high complexity, high cost and low security of application system integration in the prior art.

[0085] An embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the application system integration method described in the above embodiment when executing the computer program.

[0086] The electronic device provided in the embodiment of the present application, since it includes a processor capable of running the application system integration method of the aforementioned embodiment, can also solve the problems of high complexity and cost and low security of application system integration in the prior art.

[0087] An embodiment of the present application provides a machine-readable storage medium, on which instructions are stored. When the instructions are executed by a processor, the processor is configured to execute the application system integration method described in the above embodiment.

[0088] The machine-readable storage medium provided in the embodiment of the present application stores instructions for enabling the machine to execute the application system integration method of the above embodiment, and therefore can also solve the problems of high complexity, high cost and low security of application system integration in the prior art.

[0089] Figure 4 The internal structure diagram of the computer device of the embodiment of the present application is schematically shown. Figure 4 As shown, in one embodiment of the present application, a computer device is provided, which may be a terminal. The computer device includes a processor A01, a network interface A02, a display screen A04, an input device A05 and a memory (not shown in the figure) connected via a system bus. Among them, the processor A01 of the computer device is used to provide computing and control capabilities. The memory of the computer device includes an internal memory A03 and a non-volatile storage medium A06. The non-volatile storage medium A06 stores an operating system B01 and a computer program B02. The internal memory A03 provides an environment for the operation of the operating system B01 and the computer program B02 in the non-volatile storage medium A06. The network interface A02 of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor A01, an application system integration method is implemented. The display screen A04 of the computer device may be a liquid crystal display screen or an electronic ink display screen, and the input device A05 of the computer device may be a touch layer covered on the display screen, or a key, trackball or touchpad provided on the housing of the computer device, or an external keyboard, touchpad or mouse, etc.

[0090] Those skilled in the art will understand that Figure 4 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0091] In one embodiment, the application system integration device provided by the present application can be implemented in the form of a computer program. The computer program can be Figure 4 The computer device is run on the computer device shown. The memory of the computer device can store various program modules constituting the application system integration device, and the computer program composed of various program modules enables the processor to execute the steps of the application system integration method of each embodiment of the present application described in this specification.

[0092] Figure 4 The computer device shown can be Figure 3 The main system token generation module in the application system integration device shown executes step 100 , the subsystem token generation module executes step 200 , the verification result acquisition module executes step 300 , and the system integration control module executes step 400 .

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

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

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

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

[0097] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0098] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0099] Computer readable media include permanent and non-permanent, removable and non-removable media, and can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

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

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

Claims

1. An application system integration method, characterized in that: Applied to a service platform, the service platform includes a first front-end system and a first back-end system separated from each other, the menu of the system to be integrated is displayed in the first front-end system; the first back-end system includes a first security framework; the system to be integrated includes a front-end system and a back-end system separated from each other, the first front-end system includes the front-end system of the system to be integrated; the method includes: When it is determined that the user has successfully logged into the service platform, a main system token is generated; wherein the main system token includes user information; In response to a trigger operation initiated by a user on a menu of the target system to be integrated in a preset display area of ​​the first front-end system, microservice security authentication is performed based on the first security framework to generate a subsystem token corresponding to the target system to be integrated; Sending the main system token to the target system to be integrated, so that the target system to be integrated performs user verification according to the main system token and feeds back the verification result; When it is determined that the verification result is successful, the subsystem token is sent to the backend system of the target system to be integrated, so that the backend system authenticates the subsystem token and provides an interactive response service after completing the authentication operation.

2. The method according to claim 1, characterized in that The first backend system includes a microservice security authentication user management interface and an identity supply interface; the first security framework adopts a security framework based on the OAuth protocol, and the first security framework includes a security authentication service interface; the microservice security authentication user management interface and the security authentication service interface are both used to generate subsystem tokens, and the identity supply interface is used to provide user information to the system to be integrated.

3. The method according to claim 2, characterized in that Performing microservice security authentication based on the first security framework and generating a subsystem token corresponding to the target system to be integrated includes: The target system to be integrated is subjected to microservice security authentication through the microservice security authentication user management interface and the security authentication service interface to generate the subsystem token.

4. The method according to claim 2, characterized in that: Performing microservice security authentication based on the first security framework and generating a subsystem token corresponding to the target system to be integrated includes: Determine whether the backend system of the target system to be integrated includes a Shiro-based security framework; If so, the target system to be integrated is subjected to microservice security authentication through the microservice security authentication user management interface and the security authentication service interface to obtain an authentication result, and based on the main system token, the token issued by the security framework is obtained, and the subsystem token is generated according to the authentication result and the token issued by the security framework; If not, microservice security authentication is performed on the target system to be integrated through the microservice security authentication user management interface and the security authentication service interface to generate the subsystem token.

5. The method according to claim 1, characterized in that While performing microservice security authentication based on the first security framework and generating a subsystem token corresponding to the target system to be integrated, the method further includes: Generate an access request to the target system to be integrated, and send the access request to the gateway of the service platform; Mapping the access request to the target system to be integrated through the gateway of the service platform, and performing a conversion proxy operation on the access request through the gateway of the service platform, so that the target system to be integrated can receive the access request and add the main system token to the access request; Sending the main system token to the target system to be integrated includes: An access request including the main system token is sent to the target system to be integrated to log in to the target system to be integrated.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: According to the preset color scheme, adjust the color of the front-end page in the front-end system of the integrated system.

7. The method according to any one of claims 1 to 5, characterized in that The method further comprises: The validity periods of the main system token and the subsystem token are controlled by the first security framework.

8. An application system integration device, characterized in that: The device is configured on a service platform, wherein the service platform includes a first front-end system and a first back-end system separated from each other, and a menu of the system to be integrated is displayed in the first front-end system; the first back-end system includes a first security framework; the system to be integrated includes a front-end system and a back-end system separated from each other, and the first front-end system includes the front-end system of the system to be integrated; the device includes: A main system token generation module, used to generate a main system token when it is determined that the user has successfully logged into the service platform; wherein the main system token includes user information; A subsystem token generation module, configured to respond to a trigger operation initiated by a user on a menu of a target system to be integrated in a preset display area of ​​the first front-end system, perform microservice security authentication based on the first security framework, and generate a subsystem token corresponding to the target system to be integrated; A verification result acquisition module, used for sending the main system token to the target system to be integrated, so that the target system to be integrated performs user verification according to the main system token and feeds back the verification result; The system integration control module is used to send the subsystem token to the back-end system of the target system to be integrated when it is determined that the verification result is successful, so that the back-end system can authenticate the subsystem token and provide interactive response services after completing the authentication operation.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the application system integration method according to any one of claims 1 to 7 is implemented.

10. A machine-readable storage medium having instructions stored thereon, characterized in that: When the instruction is executed by a processor, the processor is configured to execute the application system integration method according to any one of claims 1 to 7.

Images