Unified identity authentication integration system and method

Abstract

The invention belongs to the technical field of computers, and particularly discloses a unified identity authentication integration system and method.The system comprises a third-party system, a high-performance information communication identity authentication interface RabbitMQ and an open source collaborative engineering system OpenMBEE system; wherein the third-party system is used for a system administrator to apply for data synchronization from the OpenMBEE system; and pushing the user information and the organization information to the RabbitMQ, providing an authentication request for the user; the RabbitMQ is used for receiving the user information and the organization information, and carrying out decoupling and packaging on the user information and the organization information; and transmitting the packaged user information and the packaged organization information to an OpenMBEE system. The OpenMBEE system is used for receiving and processing the packaged user information and the packaged organization information; and receiving the authentication request, and judging whether authentication succeeds or not according to the processed user information and organization information.

Description

Technical Field

[0001] The present invention belongs to the field of computer technology, and in particular relates to a unified identity authentication integration system and method. Background Art

[0002] OpenMBEE (Open Model Based Engineering Environment) is an open source collaborative engineering system developed by NASA's JPL laboratory. The OpenMBEE system does not limit the modeling language used by engineers. Engineers can use the modeling language of their choice to complete modeling work in the OpenMBEE system. The OpenMBEE system can record the work of engineers and share and synchronize them in different modeling tools to achieve cross-tool collaborative modeling and simulation.

[0003] The OpenMBEE system builds a modeling platform that connects technical content from different technical disciplines through a collaborative document interface. The platform is mainly implemented using a model management system and developed in a RESTful way, so engineers can access the platform from tools that support RESTful network services. For example, the platform can be accessed through SySML desktop client software (such as MagicDraw), from a lightweight web client (such as View Editor), or from mathematical computing software (such as Matlab, Mathematica). The OpenMBEE system also provides functions such as version control, engineering process management, and access control. In addition, the OpenMBEE system has established an open source library that aims to integrate various modeling and analysis tools and languages. The open source library contains many open source projects and open source models. As the number of engineers using the OpenMBEE system increases, this open source library will gradually expand. In addition, the extensibility of the OpenMBEE system provides a way for many commercial tools to establish plug-ins. Commercial tools can access the OpenMBEE system by adding plug-ins, so that the model files they generate can be uniformly integrated and managed in the OpenMBEE system. These plug-ins are also included in the open source library of the OpenMBEE system, further enriching the open source library of OpenMBEE and further achieving the goal of creating a unified collaborative environment based on various commercial tool software.

[0004] The OpenMBEE system has been applied to multiple engineering fields and international projects, such as spacecraft design and large telescope design. The successful application in these fields has proved the effectiveness and superiority of the OpenMBEE system in handling large and complex product designs. Among them, the OpenMBEE system has been applied to JPL (Jet Propulsion Laboratory) projects, such as Mars2020, Europa Clipper, Europa Lander, Mars Sample Return and AsteroidRedirect Retrieval Mission. JPL uses the OpenMBEE system to create and maintain hundreds of engineering documents from models with millions of elements. In addition, TMT (Thirty Meter Telescope Observatory) also uses the OpenMBEE system to create engineering documents from executable SysML models. In the practice of complex product design, in order to integrate the OpenMBEE system into existing third-party systems and make full use of the collaborative tools and design ideas provided in the OpenMBEE system, it is necessary to solve the identity authentication integration problem between the third-party system and the OpenMBEE system. Therefore, it is urgent to propose an identity authentication integration method for the OpenMBEE system. Summary of the invention

[0005] The present invention provides a unified identity authentication integration system and method, which are used to solve the identity authentication integration problem between a third-party system and an OpenMBEE system.

[0006] In a first aspect, a unified identity authentication integration system is provided, the system comprising:

[0007] Third-party systems, high-performance information communication authentication interface RabbitMQ and open source collaborative engineering system OpenMBEE system; among them,

[0008] The third-party system is used for the system administrator to apply for data synchronization with the OpenMBEE system; and to push user information and organizational information to the RabbitMQ; and for users to make authentication requests;

[0009] The RabbitMQ is used to receive the user information and the organization information, decouple and encapsulate the user information and the organization information; and transmit the encapsulated user information and organization information to the OpenMBEE system;

[0010] The OpenMBEE system is used to receive and process the encapsulated user information and organizational information; and receive the authentication request, and determine whether the authentication is successful based on the processed user information and organizational information.

[0011] In a second aspect, a unified identity authentication integration method is provided, the method comprising:

[0012] The third-party system is used by the system administrator to apply for data synchronization with the OpenMBEE system and push user information and organizational information to the RabbitMQ;

[0013] RabbitMQ receives the user information and organization information, decouples and encapsulates the user information and organization information, and transmits the encapsulated user information and organization information to the OpenMBEE system;

[0014] The OpenMBEE system receives and processes the encapsulated user information and organizational information;

[0015] A third-party system for users to make authentication requests;

[0016] The OpenMBEE system receives the authentication request and determines whether the authentication is successful based on the processed user information and organizational information.

[0017] The embodiment of the present invention provides a unified identity authentication integration system and method. For the back-end architecture of the OpenMBEE system, the existing user data and organizational data of the third-party system are directly synchronized to the data background of the OpenMBEE system. After the user registers or logs in to the third-party system, the user's registration information, including user name, password, email address, organizational structure and other information, will be synchronized to the OpenMBEE system to achieve consistent synchronization of registration information. After registering the third-party system, the user can directly access various services and design tools provided by the OpenMBEE system, thereby reducing the tedious work of system administrators repeatedly entering personnel, organization and related information, etc., and integrating the data of the third-party system with the OpenMBEE system, keeping the personnel information of the OpenMBEE system and the third-party system synchronized, and realizing the unified login identity authentication of users of the third-party system and the OpenMBEE system.

[0018] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or be understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures particularly pointed out in the written description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0020] Figure 1 A schematic diagram of the structure of a unified identity authentication integration system provided according to an embodiment of the present invention;

[0021] Figure 2 A schematic diagram of the OpenMBEE system structure provided according to an embodiment of the present invention;

[0022] Figure 3 A schematic diagram of a program code implementation flow of a consumer unit and a data integration controller provided according to an embodiment of the present invention;

[0023] Figure 4 The present invention provides a schematic diagram of a unified identity authentication integration method implementation process. DETAILED DESCRIPTION

[0024] In order to make the purpose, technical solutions and advantages of this specification more clear, the technical solutions of this specification will be clearly and completely described below in combination with the specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.

[0025] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, device, product or equipment that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0026] The technical solutions provided by the embodiments of this specification are described in detail below in conjunction with the accompanying drawings.

[0027] In order to improve the unified identity authentication capability of the third system and the OpenMBEE system, an embodiment of the present invention provides a unified identity authentication integration system and method.

[0028] Figure 1 A schematic diagram of a unified identity authentication integrated system structure provided according to an embodiment of the present invention is shown in FIG. Figure 1 , the system comprising:

[0029] Third-party systems, high-performance information communication authentication interface RabbitMQ and open source collaborative engineering system OpenMBEE system; among them,

[0030] The third-party system is used for the system administrator to apply for data synchronization with the OpenMBEE system; and to push user information and organizational information to the RabbitMQ; and for users to make authentication requests;

[0031] The RabbitMQ is used to receive the user information and the organization information, decouple and encapsulate the user information and the organization information; and transmit the encapsulated user information and organization information to the OpenMBEE system;

[0032] The OpenMBEE system is used to receive and process the encapsulated user information and organizational information; and receive the authentication request, and determine whether the authentication is successful based on the processed user information and organizational information.

[0033] It should be noted that, for ease of understanding, see Figure 2 The original OpenMBEE system is displayed. The OpenMBEE system is based on the MVC architecture. The controller layer of the OpenMBEE system includes multiple controllers to handle different requests. It has good scalability and provides the necessary conditions for extending the controller layer of the present invention. The RabbitMQ-based authentication interface and data integration controller are used as an extended service of the OpenMBEE system controller layer.

[0034] In the OpenMBEE system, the business process of user authentication function is:

[0035] Step 1: The user enters authentication information and submits an authentication request.

[0036] Step 2: Pass the authentication request to the controller to obtain authentication information.

[0037] Step 3: Access the database and retrieve relevant user information.

[0038] Step 4: Perform authentication data comparison to verify the legitimacy of the user.

[0039] Step 5: If authentication is successful, the view layer displays the data model and provides user operation functions.

[0040] Step 6: If the authentication fails, the user is prompted with authentication failure information.

[0041] The present invention makes full use of the controllability of the view layer by the front-end service of the OpenMBEE system, expands the functions of the controller layer, and creates an identity authentication interface based on RabbitMQ to obtain a unified identity authentication integrated system architecture. The view layer corresponding to the front-end service of the MVC architecture can provide the basic conditions for data representation and information interaction for the unified authentication interface service. The services of the controller layer are expanded to add unified authentication services. The model-multi-view reusability and independence between modules in the MVC three-layer service are fully utilized, that is, changing part of the function of a module will not affect the functions and logic of other levels of content. Loosely coupled components are established, expanded through control layer services, and strong decoupling expansion is adopted without affecting the functions of other model layers.

[0042] In a specific embodiment,

[0043] Initialize configuration information, and establish connections between RabbitMQ authentication interface and OpenMBEE system and third-party system, respectively, and establish message transmission channels with both. Including configuring RabbitMQ, setting virtual machine name, host name of connection factory, port, virtual host, user name and password information. Establish switches, organization information transmission queues and user information transmission queues, and use TCP protocol to establish connections between RabbitMQ and OpenMBEE and third-party systems.

[0044] In a specific embodiment,

[0045] The RabbitMQ includes a producer unit and an input channel; wherein,

[0046] The producer unit is used to push the authentication information input by the user in the third-party system to the input channel;

[0047] The input channel is used to transmit the authentication information to the switch.

[0048] In a specific embodiment,

[0049] The RabbitMQ also includes a switch and a message queue unit; wherein,

[0050] The switch is used to classify and extract the transmitted authentication information, obtain user information and organizational information, and transmit the user information and organizational information to the information queue unit;

[0051] The information queue unit is used to store the user information in a user information transmission queue and store the organization information in an organization information queue, waiting for the consumer unit to obtain it.

[0052] In a specific embodiment,

[0053] The RabbitMQ also includes an output channel and a consumer unit; wherein,

[0054] The output channel is used to transmit the user information stored in the user information transmission queue and the organization information stored in the organization information queue to the consumer unit;

[0055] The consumer unit is used to pull out user information and organizational information from the output pipeline, and determine whether the organizational data of each new user exists in the OpenMBEE system. If the determination result is that the organizational data of each new user does not exist, the data information of the new user is cleaned and discarded; and the cleaned user information and organizational information are packaged, and the packaged user information and organizational information are transmitted to the OpenMBEE system.

[0056] In a specific embodiment,

[0057] The OpenMBEE system includes a data integration controller, a front-end server, a back-end server, a database and a view layer;

[0058] The data integration controller is used to receive the packaged user information and organizational information, and synchronize the packaged user information and organizational information into the database;

[0059] The back-end server is used to receive the authentication request from the third-party system user and control the database to perform retrieval verification;

[0060] The database is used to compare the authentication information of the received authentication request with the encapsulated user information and organizational information in the database to verify the legitimacy of the user;

[0061] The view layer is used to display the data model to the third-party system if the authentication is successful, so as to provide user operation functions; if the authentication fails, the user is prompted with authentication failure information.

[0062] In a specific implementation, in the design of the user unified identity authentication integrated function, taking into account that user information and organizational information are sensitive information, access control with system administrator privileges is adopted in the design of the security mechanism, that is, the third-party system allows users with administrator privileges to trigger the synchronization operation of user data and organizational data; in addition, in the design of synchronization authentication information, in order to ensure the reliability of the system, during the message reception process, once dynamic phenomena such as abnormal message synchronization status and abnormal message reception occur, the system needs to promptly feedback the synchronization status and error information to the system administrator.

[0063] In order to better understand the present invention, the embodiment of the present invention describes in detail the program code processing flow of the consumer unit and the data integration controller. The program of the producer unit is written by a third-party system according to its system characteristics. In this specific implementation, the program of the consumer unit and the code processing flow of the data integration controller are mainly described in detail. The present invention adopts the Spring architecture and Java programming language, which is consistent with the technology stack adopted by the OpenMBEE system. The execution flow chart is as follows Figure 3 shown.

[0064] Construct three types of Bean instances (Bean instances are Java objects managed by Spring), namely OrgVO, UserVO and MqConfigVo, which are used to instantiate the organization data, user data and configuration information data of the message queue pushed by the third-party system. The OrgVO class defines the organization object, including the organization's ID, name, hierarchy, parent organization ID and other information, as well as the corresponding get / set methods. The UserVO class defines the user object, including the user's ID, name, ID number, organization code, organization name, gender and other information, as well as the corresponding get / set methods. The MqConfigVo class defines the configuration information of the message queue, including the address, port, user name, password, switch name, organization data queue name, user data queue name and the corresponding get / set methods.

[0065] The MqConfig class and the RabbitMQUtils class are tool classes, which are called by the consumer program PullUserAndOrg class to configure RabbitMQ. The MqConfig class is mainly used to load RabbitMq configuration information from the RabbitMQ configuration file, such as address, port number, authentication information, queue and route, and encapsulate it into an MqConfigVo object for later calls, so that the RabbitMq configuration information can be changed according to different scenarios. The RabbitMQUtils class is used to initialize the RabbitMq message queue according to the host address, port number, virtual machine name, user and password information in the configuration file, and defines methods such as providing a connection object (getConnection) and closing the channel and closing the connection tool (closeConnectionAndChanel).

[0066] Define the consumer program PullUserAndOrg class, which is used to obtain user data and organization data from RabbitMQ, and define a parameterless constructor, which is used to obtain the connection of the message queue and create a connection channel when the PullUserAndOrg class object is created. Among them, the syncUserData method obtains user data from the message queue, the syncOrgData method obtains organization data from the message queue, and the closeConnAndChan method is used to close the connection channel.

[0067] When designing the unified identity authentication function, the data information includes organizational information and user identification information. In order to achieve data format compatibility, when the user issues an authentication request, the RabbitMQ message queue receives data that needs to be converted to the OpenMBEE data format (for ease of description, it is called the standard format). Define the ConvertMsg class to implement data format conversion. The converUserPo method converts user identification information into the standard format, and the converOrgPo method converts organizational information into the standard format.

[0068] The data integration controller SyncUserContr class is defined to enable the OpenMBEE system to respond to the unified authentication business of third-party system users. The SyncUserContr class defines some methods for logical processing and data information synchronization operations on standard user organization information and user identification information. The functions of these methods are described in Table 1.

[0069] Table 1 Main methods in the SyncUserContr class

[0070]

[0071]

[0072] Finally, the data synchronization process of the unified identity authentication integration method is:

[0073] (1) The MqConfig class initializes the configuration information and establishes a message transmission channel with the two systems. This includes configuring RabbitMQ and setting the virtual machine name, the host name of the connection factory, the port, the virtual host, the user name, and the password information (MqConfigVo). The virtual machine name is set to / mms, the exchange name is webAdminUserAndOrgExchange, and two queues, openCAEOrgQueue and openCAEUserQueue, are established. The RabbitMQUtils class uses the TCP protocol to establish a connection between RabbitMQ and the two systems.

[0074] (2) The PullUserAndOrg class pulls user and organization data from the message queue, and the ConvertMsg class formats the data and converts it into user (AdminUserVO class) and organization objects (AdminOrgVO class).

[0075] (3) The SyncUserContr class further encapsulates the user and organization data into the OpenMBEE standard data format, then inserts the user data and organization data into the OpenMBEE database and associates the user and organization data.

[0076] A unified identity authentication integration system provided by the present invention realizes the user identity authentication integration of the OpenMBEE system and the third-party system, forms a unified identity authentication system, reduces the tedious work of system managers repeatedly entering personnel, organization and related information, keeps the personnel information of the OpenMBEE system and the third-party system synchronized, integrates the OpenMBEE system into the existing third-party system, enables users to make full use of the OpenMBEE system for complex product collaborative design, and after the user registers the third-party system, can directly access the various services and design tools provided by the OpenMBEE system, thereby making full use of the collaboration methods and design ideas provided in OpenMBEE and improving the efficiency of complex product collaborative design.

[0077] Based on the same inventive concept, the present invention also provides a unified identity authentication integration method, see Figure 4 , the method comprising:

[0078] S400: The third-party system allows the system administrator to apply for data synchronization with the OpenMBEE system and push user information and organizational information to the RabbitMQ;

[0079] S402: RabbitMQ receives the user information and the organization information, decouples and encapsulates the user information and the organization information, and transmits the encapsulated user information and organization information to the OpenMBEE system;

[0080] S404: The OpenMBEE system receives and processes the encapsulated user information and organizational information;

[0081] S406: The third-party system allows the user to submit an authentication request;

[0082] S408: The OpenMBEE system receives the authentication request and determines whether the authentication is successful based on the processed user information and organizational information.

[0083] In a specific embodiment,

[0084] The RabbitMQ includes a producer unit and an input channel; wherein,

[0085] The producer unit is used to push the authentication information input by the user in the third-party system to the input channel;

[0086] The input channel is used to transmit the authentication information to the switch.

[0087] In a specific embodiment,

[0088] The RabbitMQ also includes a switch and a message queue unit; wherein,

[0089] The switch is used to classify and extract the transmitted authentication information, obtain user information and organizational information, and transmit the user information and organizational information to the information queue unit;

[0090] The information queue unit is used to store the user information in a user information transmission queue and store the organization information in an organization information queue, waiting for the consumer unit to obtain it.

[0091] In a specific embodiment,

[0092] The RabbitMQ also includes an output channel and a consumer unit; wherein,

[0093] The output channel is used to transmit the user information stored in the user information transmission queue and the organization information stored in the organization information queue to the consumer unit;

[0094] The consumer unit is used to pull out user information and organizational information from the output pipeline, and determine whether the organizational data of each new user exists in the OpenMBEE system. If the determination result is that the organizational data of each new user does not exist, the data information of the new user is cleaned and discarded; and the cleaned user information and organizational information are packaged, and the packaged user information and organizational information are transmitted to the OpenMBEE system.

[0095] In a specific embodiment,

[0096] The OpenMBEE system includes a data integration controller, a front-end server, a back-end server, a database and a view layer;

[0097] The data integration controller is used to receive the packaged user information and organizational information, and synchronize the packaged user information and organizational information into the database;

[0098] The back-end server is used to receive the authentication request from the third-party system user and control the database to perform retrieval verification;

[0099] The database is used to compare the authentication information of the received authentication request with the encapsulated user information and organizational information in the database to verify the legitimacy of the user;

[0100] The view layer is used to display the data model to the third-party system if the authentication is successful, so as to provide user operation functions; if the authentication fails, the user is prompted with authentication failure information.

[0101] The present invention provides a unified identity authentication integration method, which realizes cross-platform message transmission based on a message queue flow mechanism, and exchanges and transmits data with an OpenMBEE system; and proposes an extended controller mechanism, which effectively solves the problem of cross-platform unified authentication between the OpenMBEE system and a third-party system. The personnel data synchronization function uses the RabbitMQ message queue method in cross-system data interaction to realize the characteristics of asynchronous, orderly and decoupled data interaction between the two systems. The extended controller pulls the user and organization data of the third-party system from the message queue to the background and cleans, formats and encapsulates the data into a data structure suitable for itself, inserts the user data and organization data into the OpenMBEE system background database, and automatically associates the two according to the relationship between personnel and organization.

[0102] Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention.

[0103] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A unified identity authentication integrated system, characterized in that: The system comprises: Third-party systems, high-performance information communication authentication interface RabbitMQ and open source collaborative engineering system OpenMBEE system; among them, The third-party system is used for the system administrator to apply for data synchronization with the OpenMBEE system; and to push user information and organizational information to the RabbitMQ; and for users to make authentication requests; The RabbitMQ is used to receive the user information and the organization information, decouple and encapsulate the user information and the organization information; and transmit the encapsulated user information and organization information to the OpenMBEE system; The OpenMBEE system is used to receive and process the encapsulated user information and organizational information; and receive the authentication request, and determine whether the authentication is successful based on the processed user information and organizational information.

2. The system according to claim 1, characterized in that The RabbitMQ includes a producer unit and an input channel; wherein, The producer unit is used to push the authentication information input by the user in the third-party system to the input channel; The input channel is used to transmit the authentication information to the switch.

3. The system according to claim 2, characterized in that The RabbitMQ also includes a switch and a message queue unit; wherein, The switch is used to classify and extract the transmitted authentication information, obtain user information and organizational information, and transmit the user information and organizational information to the information queue unit; The information queue unit is used to store the user information in a user information transmission queue and store the organization information in an organization information queue, waiting for the consumer unit to obtain it.

4. The system according to claim 3, characterized in that The RabbitMQ also includes an output channel and a consumer unit; wherein, The output channel is used to transmit the user information stored in the user information transmission queue and the organization information stored in the organization information queue to the consumer unit; The consumer unit is used to pull out user information and organizational information from the output pipeline, and determine whether the organizational data of each new user exists in the OpenMBEE system. If the determination result is that the organizational data of each new user does not exist, the data information of the new user is cleaned and discarded; and the cleaned user information and organizational information are packaged, and the packaged user information and organizational information are transmitted to the OpenMBEE system.

5. The system according to claim 3, characterized in that The OpenMBEE system includes a data integration controller, a front-end server, a back-end server, a database and a view layer; The data integration controller is used to receive the packaged user information and organizational information, and synchronize the packaged user information and organizational information into the database; The back-end server is used to receive the authentication request from the third-party system user and control the database to perform retrieval verification; The database is used to compare the authentication information of the received authentication request with the encapsulated user information and organizational information in the database to verify the legitimacy of the user; The view layer is used to display the data model to the third-party system if the authentication is successful, so as to provide user operation functions; If the authentication fails, the user will be prompted with authentication failure information.

6. A unified identity authentication integration method, characterized in that: Applied to the unified identity authentication integrated system according to any one of claims 1 to 5, the method comprising: The third-party system is used by the system administrator to apply for data synchronization with the OpenMBEE system and push user information and organizational information to the RabbitMQ; RabbitMQ receives the user information and organization information, decouples and encapsulates the user information and organization information, and transmits the encapsulated user information and organization information to the OpenMBEE system; The OpenMBEE system receives and processes the encapsulated user information and organizational information; A third-party system for users to make authentication requests; The OpenMBEE system receives the authentication request and determines whether the authentication is successful based on the processed user information and organizational information.

7. The method according to claim 6, characterized in that The RabbitMQ includes a producer unit and an input channel; wherein, The producer unit is used to push the authentication information input by the user in the third-party system to the input channel; The input channel is used to transmit the authentication information to the switch.

8. The method according to claim 7, characterized in that The RabbitMQ also includes a switch and a message queue unit; wherein, The switch is used to classify and extract the transmitted authentication information, obtain user information and organizational information, and transmit the user information and organizational information to the information queue unit; The information queue unit is used to store the user information in a user information transmission queue and store the organization information in an organization information queue, waiting for the consumer unit to obtain it.

9. The method according to claim 8, characterized in that The RabbitMQ also includes an output channel and a consumer unit; wherein, The output channel is used to transmit the user information stored in the user information transmission queue and the organization information stored in the organization information queue to the consumer unit; The consumer unit is used to pull out user information and organizational information from the output pipeline, and determine whether the organizational data of each new user exists in the OpenMBEE system. If the determination result is that the organizational data of each new user does not exist, the data information of the new user is cleaned and discarded; and the cleaned user information and organizational information are packaged, and the packaged user information and organizational information are transmitted to the OpenMBEE system.

10. The method according to claim 9, characterized in that The OpenMBEE system includes a data integration controller, a front-end server, a back-end server, a database and a view layer; The data integration controller is used to receive the packaged user information and organizational information, and synchronize the packaged user information and organizational information into the database; The back-end server is used to receive the authentication request from the third-party system user and control the database to perform retrieval verification; The database is used to compare the authentication information of the received authentication request with the encapsulated user information and organizational information in the database to verify the legitimacy of the user; The view layer is used to display the data model to the third-party system if the authentication is successful, so as to provide user operation functions; If the authentication fails, the user will be prompted with authentication failure information.

Images