CN111221900A

CN111221900A - Method for synchronizing user data to ldap by multiple heterogeneous systems

Info

Publication number: CN111221900A
Application number: CN201811425511.2A
Authority: CN
Inventors: 文新; 张来卿; 庞严冬
Original assignee: Zhuhai Hengqin Shengda Zhaoye Technology Investment Co Ltd
Current assignee: Zhuhai Hengqin Shengda Zhaoye Technology Investment Co Ltd
Priority date: 2018-11-27
Filing date: 2018-11-27
Publication date: 2020-06-02

Abstract

The invention relates to the technical field of software, in particular to a java software development technology. The method and the system obtain system user data by configuring SQL query statements of various heterogeneous systems, and lead a plurality of heterogeneous system user data into an LDAP server through the mapping relation from the configuration data table column to the LDAP attribute name, so that other systems can use the data conveniently and the data source can be used as a single sign-on data source. When the method is used together with the scheduling, the effect of timing and synchronizing data can be achieved. Therefore, the method does not need to modify the system, greatly reduces the integration cost, and is a very simple and efficient solution for many-to-one user centralized management.

Description

Method for synchronizing user data to ldap by multiple heterogeneous systems

Technical Field

The invention relates to the technical field of software, in particular to a heterogeneous system integrated single sign-on technology.

Background

At present, a large enterprise generally operates a plurality of sets of business systems, such as an HR system, an OA system, an electronic mail system and the like, if a unified user center is not provided, the situation that user data copies need to be manually maintained in a plurality of systems occurs, if user information needs to be modified in each system one by one, the login system needs to be logged in by a single input password, and thus, a large amount of repeated work is brought, and the maintenance cost is increased.

Disclosure of Invention

The technical problem to be solved by the invention is to provide a unified user center, and as long as the main data source is modified, the system automatically synchronizes to the user center on the LDAP, and informs the subsystem to capture data for updating, and the pain of verifying account passwords and remembering multiple passwords by a user can be realized by combining with a single-point login system. The system administrator also only needs to maintain a single organizational structure on the primary data source to coordinate all of the integrated subsystems.

The scheme of the invention for solving the problems is as follows: the user data is transferred and stored through an international standard lightweight directory access protocol LDAP, application software compatible with various large manufacturers is sought, and meanwhile, any SQL data source is supported by combining configuration of SQL statements and DN path mounted data.

The method comprises the following steps:

the first step is as follows: and configuring DN paths to be mounted aiming at different data sources. I.e., configure different data sources to mount on different DNs.

The second step is that: and writing a user data query SQL statement and a user upper-layer organization linked list query statement aiming at the data source.

The third step: and configuring the mapping relation from the field name of the database table of the user and the upper organization linked list to the attribute name of the LDAP data.

The fourth step: and (4) the user data of the iterative data source system and the upper layer organization linked list thereof are written into the LDAP, and the updating time is set.

The fifth step: inquiring user data under the synchronous DN, forbidding the user whose updating time is not modified, deleting user data after the user seals the password by LDAP, judging whether the user in the sealed password library exists in LDAP again, automatically recovering the password by the data on the re-matching, and deleting the sealed password

And a sixth step: and empty nodes without users in the LDAP are cleared, and the tidiness of data is ensured.

The main advantages of the invention are: the code coupling of each system is reduced, the international universal unified data interface standard is used, the integration difficulty of developers is reduced, and the enterprise organization architecture management efficiency is improved.

Drawings

The invention is further described below with reference to the accompanying drawings:

FIG. 1 is a flow chart of the present invention;

Detailed Description

As shown in fig. 1, there are the following operations in the process of integrating the isochronous data sources:

The third step: mapping relation from database table field name to LDAP data attribute name of configuration user and upper layer organization linked list

Claims

1. A method for synchronizing user data to an ldap by a plurality of heterogeneous systems, comprising: and reading data by configuring SQL statements of a specific database and then transferring the data to different DN nodes of the LDAP, thereby finishing data import integration.

2. The method for realizing data integration according to claim 1, comprising the steps of:

the first step is as follows: configuring DN paths to be mounted aiming at different data sources, namely configuring different data sources to be mounted on different DNs;

the second step is that: writing a user data query SQL statement and a user upper organization linked list query statement aiming at a data source;

the third step: configuring a mapping relation from a database table field name of a user and an upper layer organization linked list to an LDAP data attribute name;

the fourth step: the user data of the iterative data source system and the upper layer organization linked list thereof are written into the LDAP, and the updating time is set;

the fifth step: inquiring user data under the synchronous DN, forbidding the user whose updating time is not modified, deleting the user data after the user seals the password by the LDAP, judging whether the user in the sealed password library exists in the LDAP, automatically recovering the password by the data on the re-matching, and deleting the sealed password;