CN114928620A - User information synchronization method, device, equipment, storage medium and program product - Google Patents

Abstract

The application relates to a user information synchronization method, a device, equipment, a storage medium and a program product. The method comprises the following steps: detecting whether an information synchronization condition is met; if the information synchronization condition is met, acquiring updating data from the source domain; the source domain is one of an AD domain and an LDAP domain, and the update data at least comprises target user information to be updated; synchronizing the update data to a target domain using a synchronization script; the target domain is the other of the AD domain and the LDAP domain. By adopting the method, the synchronization complexity of the heterogeneous cluster user information can be reduced, and the synchronization efficiency and accuracy can be improved.

Description

User information synchronization method, device, equipment, storage medium and program product

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, a storage medium, and a program product for synchronizing user information.

Background

With the continuous development of internet technology, the business logic of application programs is also increasingly complex, and in order to ensure the reliability and convenience of maintenance and management of users in a cluster environment, centralized user management service is often adopted.

Generally, a plurality of devices in a cluster may be devices belonging to different architectures or adopting different systems, and two heterogeneous devices are taken as an example for description, and generally, user information in a device one is manually added to a device two, and user information in the device two is manually added to the device one at the same time, so as to implement synchronization and unified management on the user information in the two devices.

However, the method for synchronizing the user information in the heterogeneous cluster in the above manner has the problems of high synchronization complexity, low efficiency and easy error.

Disclosure of Invention

In view of the foregoing, it is necessary to provide a user information synchronization method, apparatus, device, storage medium, and program product capable of reducing complexity of heterogeneous cluster user information synchronization and improving synchronization efficiency and accuracy.

In a first aspect, the present application provides a user information synchronization method, including:

detecting whether an information synchronization condition is met;

if the information synchronization condition is met, acquiring updating data from the source domain; the source domain is one of an AD domain and an LDAP domain, and the update data at least comprises target user information to be updated;

synchronizing the update data into the target domain using the synchronization script; the target domain is the other of the AD domain and the LDAP domain.

In this embodiment, since the source domain and the target domain are AD domains or LDAP domains, synchronization of user information in a plurality of different domains can be achieved. Meanwhile, the updated data in the source domain can be automatically synchronized to the target domain through detection and when the condition of information synchronization is detected to be met, and the data synchronization does not need to be realized manually, so that the complexity of synchronizing the data in a plurality of different domains can be reduced, the problem of easy error caused by manual reasons can be reduced, and the synchronization efficiency can be improved.

In one embodiment, the information synchronization condition includes at least one of the following conditions:

the method comprises the following steps that a change operation for user information exists in equipment carrying a source domain;

detecting a synchronous information instruction input by a user;

the current time reaches the set synchronous time.

In one embodiment, the synchronizing the update data to the target domain using the synchronization script includes:

analyzing the updated data to obtain at least one user attribute corresponding to the target user information;

writing the target user information into a preset user file according to the user attribute;

the update data is synchronized into the target domain using the synchronization script and the user file.

In the embodiment, the updated data is analyzed, and the target user information is written into the user file according to the analyzed user attribute, so that the content included in the updated data can be conveniently and clearly obtained, and data omission is avoided; and then the updating data is synchronized to the target domain by adopting the synchronization script and the user file, so that the complexity of synchronizing the updating data to the target domain can be reduced, and the synchronization efficiency of the updating data is improved.

In one embodiment, the synchronizing the update data to the target domain using the synchronization script and the user file includes:

detecting whether the user file is empty or not;

if not, adding the user file into the synchronous script to obtain a synchronous script to be updated;

and running a synchronization script to be updated to synchronize the updated data to the target domain.

In the embodiment, whether the user file is empty or not is detected, and synchronization is performed when the user file is not empty, so that the problems that time is wasted due to empty file synchronization, and the synchronization efficiency and the accuracy are reduced can be solved.

In one embodiment, the method further includes:

detecting whether the updating data is successfully synchronized;

and if the synchronization is unsuccessful, acquiring the reason of unsuccessful synchronization, analyzing the reason of unsuccessful synchronization, and acquiring a synchronization strategy for resynchronization of the updated data.

In the embodiment, the synchronization of the update data is not successfully obtained through detection, and the reason of the unsuccessful acquisition is analyzed to obtain the resynchronization synchronization strategy, so that the resynchronization of the update data can be accurately performed, and the success rate of the synchronization of the update data is improved.

In one embodiment, the AD domain is used to store a user identifier corresponding to user information in a first device that mounts the AD domain, the LDAP domain is used to store a user identifier corresponding to user information in a second device that mounts the LDAP domain, and the number ranges of the user identifiers that can be stored in the AD domain and the LDAP domain are the same.

In this embodiment, the number ranges of the user identifiers storable in the AD domain and the LDAP domain are the same, so that the user identifier of the AD domain user is consistent with the user identifier of the LDAP domain user, and the same user uses the same user identifier, so as to quickly and accurately identify the user as the same user.

In one embodiment, after the synchronizing the update data to the target domain by using the synchronization script, the method further includes:

after application data corresponding to target user information is generated on a device carrying a target domain, the application data and the target user information are both stored in a home directory of shared storage.

In this embodiment, after the application data corresponding to the target user information is generated on the device corresponding to the target domain, the target user information and the application data thereof may be stored in the home directory of the shared storage, so that the application data may be prevented from being stored in other places by mistake, and the integrity and accuracy of the application data corresponding to the user may be ensured.

In one embodiment, the method further includes:

after a login request input by a user corresponding to the target user information is received, logging in the shared storage according to a user password included in the login request so as to access application data in a home directory corresponding to the target user information in the shared storage.

In the embodiment, the application data in the shared storage home directory is accessed through the user password, so that the user can conveniently and quickly access the application data in the shared storage home directory, and meanwhile, the data security is higher.

In one embodiment, the method further includes:

detecting whether a mapping relation exists between first equipment carrying an AD domain or second equipment carrying an LDAP domain and shared storage;

if the mapping relation does not exist between the first equipment and the shared storage, establishing the mapping relation between the first equipment and the shared storage; or if the mapping relationship does not exist between the second device and the shared storage, establishing the mapping relationship between the second device and the shared storage.

In this embodiment, the mapping relationship between the multiple devices and the shared storage is established, so that the devices can conveniently access the shared storage normally.

In a second aspect, the present application further provides a user information synchronization apparatus, including:

the detection module is used for detecting whether the information synchronization condition is met;

the data acquisition module is used for acquiring the updating data from the source domain if the information synchronization condition is met; the source domain is one of an AD domain and an LDAP domain, and the update data at least comprises target user information to be updated;

a synchronization module for synchronizing the update data to the target domain using the synchronization script; the target domain is the other of the AD domain and the LDAP domain.

In a third aspect, the present application further provides a computer device, which includes a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:

detecting whether an information synchronization condition is met;

if the information synchronization condition is met, acquiring updating data from the source domain; the source domain is one of an AD domain and an LDAP domain, and the update data at least comprises target user information to be updated;

synchronizing the update data to the target domain using the synchronization script; the target domain is the other of the AD domain and the LDAP domain.

In a fourth aspect, the present application also provides a computer readable storage medium having a computer program stored thereon, which when executed by a processor, performs the steps of:

detecting whether an information synchronization condition is met;

if the information synchronization condition is met, acquiring updating data from the source domain; the source domain is one of an AD domain and an LDAP domain, and the update data at least comprises target user information to be updated;

synchronizing the update data into the target domain using the synchronization script; the target domain is the other of the AD domain and the LDAP domain.

In a fifth aspect, the present application also provides a computer program product comprising a computer program which, when executed by a processor, performs the steps of:

detecting whether an information synchronization condition is met;

if the information synchronization condition is met, acquiring updating data from the source domain; the source domain is one of an AD domain and an LDAP domain, and the update data at least comprises target user information to be updated;

synchronizing the update data into the target domain using the synchronization script; the target domain is the other of the AD domain and the LDAP domain.

According to the user information synchronization method, the user information synchronization device, the user information synchronization equipment, the storage medium and the program product, whether the information synchronization condition is met is detected, the update data are obtained from the source domain when the information synchronization condition is met, and the update data are synchronized to the target domain by using the synchronization script; the updating data at least comprises target user information to be updated, the source domain is one of the AD domain and the LDAP domain, and the target domain is the other one of the AD domain and the LDAP domain. In the method, the source domain and the target domain are AD domains or LDAP domains, so that the synchronization of user information in a plurality of different domains can be realized. Meanwhile, the updated data in the source domain can be automatically synchronized to the target domain through detection and when the condition of information synchronization is detected to be met, and data synchronization does not need to be manually realized, so that the complexity of data synchronization in a plurality of different domains can be reduced, the problem of easy error caused by manual reasons can be reduced, and the synchronization efficiency can be improved.

Drawings

FIG. 1 is a diagram of an exemplary embodiment of a user information synchronization method;

FIG. 2 is a flow diagram illustrating a method for synchronizing user information in one embodiment;

FIG. 3 is a flowchart illustrating a user information synchronization method according to another embodiment;

FIG. 4 is a flowchart illustrating a user information synchronization method according to another embodiment;

FIG. 5 is a flowchart illustrating a user information synchronization method according to another embodiment;

FIG. 6 is a block diagram showing the structure of a user information synchronization apparatus according to an embodiment;

FIG. 7 is a diagram of the internal structure of a computer device in one embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

In order to facilitate better understanding of the technical solutions of the present application, the following terms referred to in the embodiments of the present application are explained first:

LDAP field: the Lightweight Directory Access Protocol is named as Lightweight Directory Access Protocol (Lightweight Directory Access Protocol) and is also named as OpenLDAP, and the Lightweight Directory Access Protocol is similar to a storage container and can store user information on equipment.

An AD domain: an Active Directory, the name of which is an Active Directory, is similar to a storage container that can store user information on a device. The AD is an application instance of LDAP and should not be LDAP itself.

Sharing storage: is a segment of memory in physical memory that can be shared by more than two processes.

The user information synchronization method provided by the embodiment of the application can be applied to the application environment shown in fig. 1. Wherein thefirst device 102 communicates with thesecond device 104 over a network. The shared storage may store application data generated in thefirst device 102 and thesecond device 104, and the shared storage may be mounted on thefirst device 102 or thesecond device 104. Thefirst device 102 may be loaded with an AD domain, thefirst device 102 may be a device using a Windows operating system, thesecond device 104 may be loaded with an LDAP domain, and thesecond device 104 may be a device using a Linux operating system. Thefirst device 102 may perform data interaction with thesecond device 104, for example, thesecond device 104 sends thefirst device 102 whether a data change operation exists on the device, whether the device establishes a mapping relationship with the shared storage, and the like. Thefirst device 102 and thesecond device 104 may be computer devices, and the computer devices may be, but are not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices, and portable wearable devices, and the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart car-mounted devices, and the like. The portable wearable device can be a smart watch, a smart bracelet, a head-mounted device, and the like.

In one embodiment, as shown in fig. 2, a user information synchronization method is provided, which is described by taking the method as an example applied to the first device/computer device in fig. 1, and the method may include the following steps:

s202, whether the information synchronization condition is met is detected.

In this step, before the user information is synchronized, timing for information synchronization, that is, information synchronization conditions may be set in advance. For the preset information synchronization condition, optionally, at least one of the following conditions may be included: the method comprises the following steps that a change operation for user information exists in equipment carrying a source domain; detecting a synchronous information instruction input by a user; the current time reaches the set synchronous time.

In response to the first condition, the device in the source domain has a change operation for the user information. Here, the device for mounting a source domain may be determined according to the customization of a user, and the source domain refers to a domain in which data needs to be synchronized from a certain domain, and may be, for example, the first device described above, or may be a second device. When the first device is used as an execution main body and is used as a device carrying a source domain, the first device can automatically obtain whether the user information of the first device is subjected to change operation, wherein the change operation can be operations of adding, deleting, modifying, inquiring and the like on the user information; for example, the first device is used as an execution main body, the second device is a device carrying a source domain, and the second device can obtain whether the user information of the second device is changed or not by itself and send the change operation to the first device through a message, so that the first device can know that the change operation of the user information exists in the second device. In short, after the first device obtains the change operation of the user information in the device with the source domain, it can be determined that the information synchronization condition is currently satisfied, and the condition mainly aims at a scene of automatically synchronizing the user information.

And detecting a synchronous information instruction input by a user according to a second condition. The user can input the synchronous information command by adopting a keyboard input mode, a voice input mode, a synchronous button clicking input mode and the like, and mainly aims at manually clicking synchronization when unsynchronized user information exists, namely inputting the synchronous information command. Here, the user may input the synchronization information instruction on the first device, or may input the synchronization information instruction on the second device, and send the synchronization information instruction to the first device through the second device, so that the first device knows that the user inputs the synchronization information instruction, and in short, the first device may detect the synchronization information instruction input by the user. After the user inputs the synchronization information command, the first device may detect the synchronization information command and determine that the information synchronization condition is currently satisfied.

And aiming at the third condition, the current time reaches the set synchronous time. The medium condition is mainly for data backup of user information. The first device may have a preset synchronization time, that is, what time can be used for information synchronization, and the synchronization time may be a periodic time or a single time, that is, only once. The first device can monitor the current time in real time, compare the current time with the set synchronization time, and determine that the current information synchronization condition is met when the current time and the set synchronization time are consistent.

S204, if the information synchronization condition is met, acquiring update data from a source domain; the source domain is one of an AD domain and an LDAP domain, and the update data at least includes target user information to be updated.

In this step, as mentioned above, the source domain may be a target domain that is set by the user in advance according to a synchronization manner, where data is also required to be synchronized to the target domain. The source domain and the target domain are both one of the AD domain and the LDAP domain, and are different. The synchronization mode comprises two synchronization modes, wherein one mode is from an AD domain to an LDAP domain, the AD domain is a source domain, and the LDAP domain is a target domain; and the other is synchronizing from the LDAP domain to the AD domain, wherein the LDAP domain is a source domain, and the AD domain is a target domain.

After the information synchronization condition is currently satisfied, the update data may be obtained first, and may be generally obtained from the source domain. For the three information synchronization conditions, if the first device has a change operation of user information, the device records the corresponding changed data, and the changed data is the updated data; of course, the total amount of data including the changed data may be the updated data, wherein the total amount of data refers to all data in the source domain. For the second and third information synchronization conditions, in which there is no possibility that data change occurs in the source domain, this situation corresponds to a scenario in which a user needs to perform an update or a timing update, and the update data under these two conditions may be full data, that is, all data in the source domain. The update data may include information of a target user to be updated, and may of course include other data information, where the information of the target user may be a user password, a phone number, an identification number, and so on of the target user.

S206, synchronizing the updating data to the target domain by using the synchronization script; the target domain is the other of the AD domain and the LDAP domain.

In this step, it is mentioned that the target domain and the source domain are two opposite domains, and are different from each other, and after the source domain is determined, the target domain can be determined naturally, and information synchronization is performed on the target domain.

Specifically, when information synchronization is performed, the update data may be put into a preset synchronization script, and the synchronization script is used to perform information synchronization on the target domain, specifically, the synchronization script may be run on a device carrying the target domain to synchronize the update data to the target domain. Here, synchronization refers to an operation of adding the update data to the target domain, or may be an operation of overwriting the original data corresponding to the update data in the target domain. The synchronization script may be a preset script, which may be recognized by the target domain and the device mounted thereon.

The updating data is synchronized to the target domain by the synchronization script, so that the efficiency and the accuracy of data synchronization in the target domain can be improved.

In the user information synchronization method, whether the information synchronization condition is met is detected, the updating data is obtained from the source domain when the information synchronization condition is met, and the updating data is synchronized to the target domain by using the synchronization script; the updating data at least comprises target user information to be updated, the source domain is one of the AD domain and the LDAP domain, and the target domain is the other one of the AD domain and the LDAP domain. In the method, the source domain and the target domain are AD domains or LDAP domains, so that the synchronization of user information in a plurality of different domains can be realized. Meanwhile, the updated data in the source domain can be automatically synchronized to the target domain through detection and when the condition of information synchronization is detected to be met, and data synchronization does not need to be manually realized, so that the complexity of data synchronization in a plurality of different domains can be reduced, the problem of easy error caused by manual reasons can be reduced, and the synchronization efficiency can be improved.

While the above embodiments mention that the synchronization of the update data may be performed by the synchronization script, but a specific synchronization process is not specifically described, the following embodiments describe in detail how the update data is synchronized to the target domain by the synchronization script.

In another embodiment, another user information synchronization method is provided, and on the basis of the above embodiment, as shown in fig. 3, the above S206 may include the following steps:

s302, the updated data is analyzed, and at least one user attribute corresponding to the target user information is obtained.

In this step, it is mentioned above that the update data at least includes target user information to be updated, where the source domain is an LDAP domain and the target domain is an AD domain, that is, the update data needs to be read from the LDAP domain, where the update data having an ObjectClass object class is obtained in the LDAP, where the ObjectClass object class is an LDAP object class and is a built-in data model of the LDAP, such as an endoorgperson object class; each ObjectClass has its own data structure, for example, the ObjectClass of "user" has many built-in attributes, such as user name (name), password (password), telephone (mobile), etc.

After obtaining the update data from the source domain, the update data may be analyzed according to the user attribute to obtain at least one attribute/user attribute and an attribute value corresponding to each user attribute, where the user attribute is a user attribute corresponding to the target user information in the update data.

S304, writing the target user information into a preset user file according to the user attribute.

In this step, the format of the preset user file may be set according to an actual situation, and may be, for example, a CSV format, an xls (i.e., excel) format, a doc (i.e., word) format, and the like. Here, in the preset user file, a form may be set in advance according to the user attributes, where the horizontal direction of the form is each user attribute, and the lower surface of each vertical user attribute may be filled with corresponding attribute content, respectively. The user attributes here may include, for example, a user name, a user password, a user home directory, a user account control, a user uidnetwork (i.e., a user identification number), a gidnetwork (group identification number), and so on.

Then, in this step, after obtaining at least one user attribute, taking a user file in a CSV format as an example, a corresponding user attribute may be found in the CSV user file according to the user attribute, and an attribute value corresponding to the user attribute obtained through analysis is filled in a corresponding position of the CSV user file. And if the attribute value corresponding to the user attribute obtained by the analysis is null, the record of the user attribute at the corresponding position in the CSV user file is null, namely the attribute value is not filled.

S306, the updating data is synchronized to the target domain by the aid of the synchronization script and the user file.

In this step, since there may be a case where data is not written in the user file due to a write failure when the analyzed user attribute and attribute value are written in the user file, which may cause a subsequent failure in data synchronization, it is optional here to detect whether the user file is empty before synchronizing the updated data; if not, adding the user file into the synchronous script to obtain a synchronous script to be updated; and running a synchronization script to be updated to synchronize the updated data to the target domain.

That is, it may be first detected whether the user file is an empty file, and if not, it indicates that the user file has user attributes and attribute values written therein, and then the user file may be added to the synchronization script to form a synchronization script to be updated, and the synchronization script to be updated is run on the device carrying the target domain to quickly synchronize the update data to the target domain. The method and the device can avoid the problems of time waste and reduction of synchronization efficiency and accuracy due to the synchronization of the empty files by detecting whether the user files are empty and synchronizing when the user files are not empty.

In the embodiment, the updated data is analyzed, and the target user information is written into the user file according to the analyzed user attribute, so that the content included in the updated data can be conveniently and clearly obtained, and data omission is avoided; and then the updating data is synchronized to the target domain by adopting the synchronization script and the user file, so that the complexity of synchronizing the updating data to the target domain can be reduced, and the synchronization efficiency of the updating data is improved.

In the above embodiment, how to synchronize the update data is specifically described, a phenomenon that synchronization is unsuccessful once is inevitable in the synchronization process, and how to specifically operate when synchronization is unsuccessful is inevitable, which is described in detail in the following embodiment.

In another embodiment, another user information synchronization method is provided, and on the basis of the above embodiment, as shown in fig. 4, the method may further include the following steps:

s402, whether the updating data is synchronized successfully is detected.

S404, if the synchronization is unsuccessful, acquiring the reason of unsuccessful synchronization, analyzing and processing the reason of unsuccessful synchronization, and acquiring a synchronization strategy for re-synchronizing the updated data.

In S402-S404, after the update data in the target domain is synchronized, the device corresponding to the target domain may return a response message to the first device, where the response message may indicate that the update data is successfully synchronized in the target domain, or indicate that the update data is not successfully synchronized in the target domain; meanwhile, when the synchronization is unsuccessful, the reason of the unsuccessful synchronization can be output to the first device, so that the first device can know the reason of the unsuccessful synchronization. After that, the first device may obtain a synchronization policy for resynchronization by analyzing the reason for the unsuccessful synchronization, where the synchronization policy may include manual synchronization or automatic resynchronization, or may further include resynchronization of all the update data or resynchronization of part of the update data that fails to be synchronized. For example, if the reason for the unsuccessful is that the LDAP is faulty, the LDAP may be debugged or repaired, and the update data may be re-synchronized in a manual synchronization manner after the debugging or repairing.

In the embodiment, the synchronization of the update data is not successfully obtained through detection, and the obtained reasons of the unsuccessful acquisition are analyzed to obtain the resynchronization synchronization strategy, so that the update data can be conveniently and accurately resynchronized, and the success rate of the update data synchronization is improved.

In the foregoing embodiment, the AD domain and the LDAP domain are mentioned, and specifically, the AD domain is used to store a user identifier corresponding to user information in a first device that mounts the AD domain, the LDAP domain is used to store a user identifier corresponding to user information in a second device that mounts the LDAP domain, and the user information may include user information such as a user identifier and a user password, and for the size of the range of the user identifiers stored in the two domains, it is proposed in this embodiment that the number ranges of the user identifiers that can be stored in the AD domain and the LDAP domain are the same.

The User identifier may include a UID (User Identification), a GID (Group Identification), and the like. The user identifiers included in the first device and the second device are the same, for example, both the devices include the UID and the GID, or both the devices include only the UID, or both the devices include only the GID.

The user may preset the numerical ranges corresponding to the user identifications in the first device and the second device, and set the numerical ranges corresponding to the user identifications in the two devices to the same range, for example, set the numerical ranges of the UIDs in the first device and the second device to 0 to 100.

In this embodiment, the number ranges of the user identifiers storable in the AD domain and the LDAP domain are the same, so that it can be ensured that the user identifier of the AD domain user is consistent with the user identifier of the LDAP domain user, and the same user uses the same user identifier, so as to quickly and accurately identify the same user.

In the above embodiments, it is explained that the update data can be synchronized to the target domain by using the synchronization script, and then after the update data is synchronized to the target domain by using the synchronization script, the application data generated on the device can be stored, which will be described in detail below.

In another embodiment, another user information synchronization method is provided, and on the basis of the above embodiment, the method may further include the following step a:

step A, after application data corresponding to target user information is generated on equipment carrying a target domain, the application data and the target user information are stored in a home directory of shared storage.

In this step, before storing the application data, a mapping relationship between the device and the shared storage may be established in advance, so that the corresponding shared storage may be accurately accessed. Optionally, the process of establishing the mapping relationship may be: detecting whether a mapping relation exists between first equipment carrying an AD domain or second equipment carrying an LDAP domain and shared storage; if the mapping relation does not exist between the first equipment and the shared storage, establishing the mapping relation between the first equipment and the shared storage; or if the mapping relationship does not exist between the second device and the shared storage, establishing the mapping relationship between the second device and the shared storage.

Assuming that the first device is the executing entity, the first device may determine whether the second device has a mapping relationship with the shared storage through a message sent by the second device, where the message may characterize whether the second device itself has a mapping relationship with the shared storage. The first device may naturally also know whether it establishes a mapping relationship with the shared storage. Whether the mapping relation exists or not can be found in the first device or the second device, whether the information such as the bound shared storage identifier, the bound address, the bound shared storage user password and the like exists or not can be found, if the information exists, the mapping relation is established, and the user can directly use the mapping relation without repeatedly establishing the mapping relation; otherwise, no mapping relation is established. Then, assuming that the first device has no mapping relationship with the shared storage, the first device may establish a mapping relationship between the shared storage and the first device, mount the shared storage on the first device, and set to boot-up and self-start. The mapping relation between the multiple devices and the shared storage is established, so that the devices can conveniently access the shared storage normally.

In addition, home directories corresponding to each piece of user information are set in the shared storage, generally, one piece of user information corresponds to one home directory, application data, user information, application software and the like of a user corresponding to the user information can be stored in the home directories, and the application data can be operation data of the user on the application software and the like.

After the mapping relationship between the device and the shared storage is established, and after application data corresponding to the target user information is generated on the device carrying the target domain, the application data and the target user information can be stored in the shared storage, and the home directory corresponding to the target user information. In addition, the application data generated in the device carrying the source domain may also be stored in the home directory corresponding to the target user information, so as to ensure the integrity and accuracy of the application data in the shared storage.

After storing the application data in the home directory of the shared storage, optionally, after receiving a login request input by a user corresponding to the target user information, logging in the shared storage according to a user password included in the login request, so as to access the application data in the home directory corresponding to the target user information in the shared storage.

That is to say, a user may send a login request to a device (for example, a first device), where the login request may include information such as a user password and a user name, and the device may access the corresponding shared storage through the user password, find the corresponding home directory in the shared storage through the user name, and access application data in the home directory, so that the user may conveniently and quickly access the application data in the home directory of the shared storage. Meanwhile, each user can only see the application data under the home directory corresponding to the user name of the user, and operate the content or the authorized application software under the home directory, so that the safety of the data under the home directory can be ensured.

In this embodiment, after the application data corresponding to the target user information is generated on the device corresponding to the target domain, the target user information and the application data thereof may be stored in the home directory of the shared storage, so that the application data may be prevented from being stored in other places by mistake, and the integrity and accuracy of the application data corresponding to the user may be ensured.

To facilitate a more detailed description of the technical solution of the present application, the following describes the technical solution of the present application with reference to a specific embodiment, in this embodiment, it is assumed that the source domain is an AD domain and the target domain is an LDAP domain, and referring to fig. 5, the method may include the following steps:

s501, after the process is started, detecting whether an information synchronization condition is met, if the information synchronization condition is met, executing S502, and if not, directly ending the process; the information synchronization condition includes at least one of the presence of a change operation for user information in a device in which the source domain (AD domain) is installed, the detection of a synchronization information command input by a user, and the arrival of the current time at a set synchronization time.

S502, acquiring target user information to be updated from the AD domain.

S503, analyzing the target user information to obtain at least one corresponding user attribute.

S504, writing the target user information into the user file in the CSV format according to the user attribute.

S505, detecting whether the user file in the CSV format is not empty, if so, executing S506, otherwise, returning to execute S504.

S506, adding the user file in the CSV format into the synchronous script to obtain the synchronous script to be updated.

And S507, running a synchronization script to be updated to synchronize the target user information into the LDAP domain.

S508, detecting whether the update data is synchronized successfully, if not, performing S509, and if so, performing S511.

S509, a reason of unsuccessful synchronization is obtained and analyzed, and a synchronization strategy for re-synchronizing the update data is obtained.

S510, establishing a mapping relation between a first device carrying the AD domain and a second device carrying the LDAP domain and shared storage.

And S511, after the application data corresponding to the target user information is generated on the second device carrying the LDAP domain, storing the application data and the target user information in a home directory of shared storage.

S512, after receiving the user password input by the user corresponding to the target user information, logging in the shared storage through the user password so as to access the application data in the home directory corresponding to the target user information in the shared storage.

In this embodiment, whether the information synchronization condition is satisfied is detected, and when the information synchronization condition is satisfied, target user information to be updated is acquired from an AD domain (source domain), and the target user information is synchronized into an LDAP domain (target domain) using a synchronization script. In the method, the source domain and the target domain are AD domains or LDAP domains, so that the synchronization of user information in a plurality of different domains can be realized. Meanwhile, the updated data in the source domain can be automatically synchronized to the target domain through detection and when the condition of information synchronization is detected to be met, and data synchronization does not need to be manually realized, so that the complexity of data synchronization in a plurality of different domains can be reduced, the problem of easy error caused by manual reasons can be reduced, and the synchronization efficiency can be improved.

It should be understood that, although the steps in the flowcharts related to the embodiments as described above are sequentially displayed as indicated by arrows, the steps are not necessarily performed sequentially as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the flowcharts related to the embodiments described above may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the execution order of the steps or stages is not necessarily sequential, but may be performed alternately or alternately with other steps or at least a part of the steps or stages in other steps.

Based on the same inventive concept, the embodiment of the application also provides a user information synchronization device for realizing the user information synchronization method. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme described in the above method, so the specific limitations in one or more embodiments of the user information synchronization device provided below can be referred to the limitations of the user information synchronization method in the foregoing, and details are not described herein again.

In one embodiment, as shown in fig. 6, there is provided a user information synchronization apparatus including: detection module 11, data acquisition module 12 and synchronization module 13, wherein:

the detection module 11 is configured to detect whether an information synchronization condition is satisfied;

a data obtaining module 12, configured to obtain update data from the source domain if the information synchronization condition is satisfied; the source domain is one of an AD domain and an LDAP domain, and the update data at least comprises target user information to be updated;

a synchronization module 13 for synchronizing the update data into the target domain using the synchronization script; the target domain is the other of the AD domain and the LDAP domain.

Optionally, the information synchronization condition includes at least one of the following conditions: the method comprises the following steps that a change operation for user information exists in equipment carrying a source domain; detecting a synchronous information instruction input by a user; the current time reaches the set synchronous time.

In another embodiment, another user information synchronization apparatus is provided, and based on the foregoing embodiment, the synchronization module 13 may include: analysis unit, write unit and synchronization unit, wherein:

the analysis unit is used for analyzing the updated data to obtain at least one user attribute corresponding to the target user information;

the writing unit is used for writing the target user information into a preset user file according to the user attribute;

and the synchronization unit is used for synchronizing the updating data into the target domain by utilizing the synchronization script and the user file.

Optionally, the synchronization unit is specifically configured to detect whether a user file is empty; if not, adding the user file into the synchronous script to obtain a synchronous script to be updated; and running a synchronization script to be updated to synchronize the updated data to the target domain.

In another embodiment, another user information synchronization apparatus is provided, and on the basis of the above embodiment, the apparatus further includes: synchronous result detection module and analysis module, wherein:

the synchronization result detection module is used for detecting whether the updating data is successfully synchronized;

and the analysis module is used for acquiring the reason of unsuccessful synchronization if the update data is unsuccessful, analyzing the reason of unsuccessful synchronization and acquiring a synchronization strategy for resynchronization of the update data.

In another embodiment, the AD domain is used to store a user identifier corresponding to user information in a first device that mounts the AD domain, the LDAP domain is used to store a user identifier corresponding to user information in a second device that mounts the LDAP domain, and the number ranges of the user identifiers that can be stored in the AD domain and the LDAP domain are the same.

In another embodiment, another user information synchronization apparatus is provided, and based on the above embodiment, the apparatus further includes a storage module, where the storage module is configured to store, in a home directory of shared storage, both application data and target user information after the application data corresponding to the target user information is generated on a device hosting the target domain.

Optionally, the apparatus further includes a login access module, where the login access module is configured to log in the shared storage according to a user password included in a login request after receiving the login request input by the user corresponding to the target user information, so as to access, in the shared storage, application data in a home directory corresponding to the target user information.

Optionally, the apparatus further comprises: the mapping relation detection module and the establishment module are provided, wherein: the mapping relation detection module is used for detecting whether a mapping relation exists between the first device carrying the AD domain or the second device carrying the LDAP domain and the shared storage;

the establishing module is used for establishing a mapping relation between the first equipment and the shared storage if the mapping relation does not exist between the first equipment and the shared storage; or if the mapping relationship does not exist between the second device and the shared storage, establishing the mapping relationship between the second device and the shared storage.

The modules in the user information synchronization device can be wholly or partially implemented by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in fig. 7. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for communicating with an external terminal in a wired or wireless manner, and the wireless manner can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a user information synchronization method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.

Those skilled in the art will appreciate that the architecture shown in fig. 7 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:

detecting whether an information synchronization condition is met; if the information synchronization condition is met, acquiring updating data from the source domain; the source domain is one of an AD domain and an LDAP domain, and the update data at least comprises target user information to be updated; synchronizing the update data into the target domain using the synchronization script; the target domain is the other of the AD domain and the LDAP domain.

In one embodiment, the information synchronization condition includes at least one of the following conditions: the method comprises the following steps that a change operation for user information exists in equipment carrying a source domain; detecting a synchronous information instruction input by a user; the current time reaches the set synchronous time.

In one embodiment, the processor when executing the computer program further performs the steps of:

analyzing the updated data to obtain at least one user attribute corresponding to the target user information; writing the target user information into a preset user file according to the user attribute; the update data is synchronized into the target domain using the synchronization script and the user file.

In one embodiment, the processor when executing the computer program further performs the steps of:

detecting whether the user file is empty or not; if not, adding the user file into the synchronous script to obtain a synchronous script to be updated; and running a synchronization script to be updated to synchronize the updated data to the target domain.

In one embodiment, the processor when executing the computer program further performs the steps of:

detecting whether the updating data is successfully synchronized; and if the synchronization is unsuccessful, acquiring the reason of unsuccessful synchronization, analyzing the reason of unsuccessful synchronization, and acquiring a synchronization strategy for resynchronization of the updated data.

In one embodiment, the AD domain is used to store a user identifier corresponding to user information in a first device that mounts the AD domain, the LDAP domain is used to store a user identifier corresponding to user information in a second device that mounts the LDAP domain, and the number ranges of the user identifiers that can be stored in the AD domain and the LDAP domain are the same.

In one embodiment, the processor, when executing the computer program, further performs the steps of:

after application data corresponding to target user information is generated on a device carrying a target domain, the application data and the target user information are both stored in a home directory of shared storage.

In one embodiment, the processor, when executing the computer program, further performs the steps of:

after a login request input by a user corresponding to the target user information is received, logging in the shared storage according to a user password included in the login request so as to access application data in a home directory corresponding to the target user information in the shared storage.

In one embodiment, the processor when executing the computer program further performs the steps of:

detecting whether a mapping relation exists between first equipment carrying an AD domain or second equipment carrying an LDAP domain and shared storage; if the mapping relation does not exist between the first equipment and the shared storage, establishing the mapping relation between the first equipment and the shared storage; or if the mapping relationship does not exist between the second device and the shared storage, establishing the mapping relationship between the second device and the shared storage.

In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:

detecting whether an information synchronization condition is met; if the information synchronization condition is met, acquiring updating data from the source domain; the source domain is one of an AD domain and an LDAP domain, and the update data at least comprises target user information to be updated; synchronizing the update data to the target domain using the synchronization script; the target domain is the other of the AD domain and the LDAP domain.

In one embodiment, the information synchronization condition includes at least one of the following conditions: the method comprises the following steps that change operation on user information exists in equipment carrying a source domain; detecting a synchronous information instruction input by a user; the current time reaches the set synchronous time.

In one embodiment, the computer program when executed by the processor further performs the steps of:

analyzing the updated data to obtain at least one user attribute corresponding to the target user information; writing the target user information into a preset user file according to the user attribute; the update data is synchronized into the target domain using the synchronization script and the user file.

In one embodiment, the computer program when executed by the processor further performs the steps of:

detecting whether the user file is empty or not; if not, adding the user file into the synchronous script to obtain a synchronous script to be updated; and running a synchronization script to be updated to synchronize the updated data to the target domain.

In one embodiment, the computer program when executed by the processor further performs the steps of:

detecting whether the updating data is successfully synchronized; and if the synchronization is unsuccessful, acquiring the reason of unsuccessful synchronization, analyzing the reason of unsuccessful synchronization, and acquiring a synchronization strategy for resynchronization of the updated data.

In one embodiment, the AD domain is used to store a user identifier corresponding to user information in a first device that mounts the AD domain, the LDAP domain is used to store a user identifier corresponding to user information in a second device that mounts the LDAP domain, and the number ranges of the user identifiers that can be stored in the AD domain and the LDAP domain are the same.

In one embodiment, the computer program when executed by the processor further performs the steps of:

after application data corresponding to target user information is generated on a device carrying the target domain, the application data and the target user information are both stored in a home directory of shared storage.

In one embodiment, the computer program when executed by the processor further performs the steps of:

after a login request input by a user corresponding to the target user information is received, logging in the shared storage according to a user password included in the login request so as to access application data in a home directory corresponding to the target user information in the shared storage.

In one embodiment, the computer program when executed by the processor further performs the steps of:

detecting whether a mapping relation exists between first equipment carrying an AD domain or second equipment carrying an LDAP domain and shared storage; if the mapping relation does not exist between the first equipment and the shared storage, establishing the mapping relation between the first equipment and the shared storage; or if the mapping relationship does not exist between the second device and the shared storage, establishing the mapping relationship between the second device and the shared storage.

In one embodiment, a computer program product is provided, comprising a computer program which when executed by a processor performs the steps of:

detecting whether an information synchronization condition is met; if the information synchronization condition is met, acquiring updating data from the source domain; the source domain is one of an AD domain and an LDAP domain, and the update data at least comprises target user information to be updated; synchronizing the update data into the target domain using the synchronization script; the target domain is the other of the AD domain and the LDAP domain.

In one embodiment, the information synchronization condition includes at least one of the following conditions: the method comprises the following steps that a change operation for user information exists in equipment carrying a source domain; detecting a synchronous information instruction input by a user; the current time reaches the set synchronous time.

In one embodiment, the computer program when executed by the processor further performs the steps of:

analyzing the updated data to obtain at least one user attribute corresponding to the target user information; writing the target user information into a preset user file according to the user attribute; the update data is synchronized into the target domain using the synchronization script and the user file.

In one embodiment, the computer program when executed by the processor further performs the steps of:

detecting whether the user file is empty or not; if not, adding the user file into the synchronous script to obtain a synchronous script to be updated; and running a synchronization script to be updated to synchronize the updated data to the target domain.

In one embodiment, the computer program when executed by the processor further performs the steps of:

detecting whether the updating data is successfully synchronized; if the synchronization is unsuccessful, acquiring the reason of unsuccessful synchronization, analyzing and processing the reason of unsuccessful synchronization, and acquiring a synchronization strategy for re-synchronizing the updated data.

In one embodiment, the AD domain is used to store a user identifier corresponding to user information in a first device that mounts the AD domain, the LDAP domain is used to store a user identifier corresponding to user information in a second device that mounts the LDAP domain, and the number ranges of the user identifiers that can be stored in the AD domain and the LDAP domain are the same.

In one embodiment, the computer program when executed by the processor further performs the steps of:

after application data corresponding to target user information is generated on a device carrying the target domain, the application data and the target user information are both stored in a home directory of shared storage.

In one embodiment, the computer program when executed by the processor further performs the steps of:

after a login request input by a user corresponding to the target user information is received, logging in the shared storage according to a user password included in the login request so as to access application data in a home directory corresponding to the target user information in the shared storage.

In one embodiment, the computer program when executed by the processor further performs the steps of:

detecting whether a mapping relation exists between first equipment carrying an AD domain or second equipment carrying an LDAP domain and shared storage; if the mapping relation does not exist between the first equipment and the shared storage, establishing the mapping relation between the first equipment and the shared storage; or if the mapping relationship does not exist between the second device and the shared storage, establishing the mapping relationship between the second device and the shared storage.

It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above may be implemented by hardware instructions of a computer program, which may be stored in a non-volatile computer-readable storage medium, and when executed, may include the processes of the embodiments of the methods described above. Any reference to memory, databases, or other media used in the embodiments provided herein can include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high-density embedded nonvolatile Memory, resistive Random Access Memory (ReRAM), Magnetic Random Access Memory (MRAM), Ferroelectric Random Access Memory (FRAM), Phase Change Memory (PCM), graphene Memory, and the like. Volatile Memory can include Random Access Memory (RAM), external cache Memory, and the like. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others. The databases referred to in various embodiments provided herein may include at least one of relational and non-relational databases. The non-relational database may include, but is not limited to, a block chain based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, quantum computing based data processing logic devices, etc., without limitation.

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.

Claims (10)

1. A method for synchronizing user information, the method comprising:

detecting whether an information synchronization condition is met;

if the information synchronization condition is met, acquiring updating data from the source domain; the source domain is one of an AD domain and an LDAP domain, and the update data at least comprises target user information to be updated;

synchronizing the update data into a target domain using a synchronization script; the target domain is the other of the AD domain and the LDAP domain.

2. The method of claim 1, wherein synchronizing the update data into a target domain using a synchronization script comprises:

analyzing the updating data to obtain at least one user attribute corresponding to the target user information;

writing the target user information into a preset user file according to the user attribute;

and synchronizing the updating data to the target domain by utilizing the synchronization script and the user file.

3. The method of claim 2, wherein the synchronizing the update data into the target domain using the synchronization script and the user file comprises:

detecting whether the user file is empty or not;

if not, adding the user file into the synchronous script to obtain a synchronous script to be updated;

and running the synchronization script to be updated to synchronize the update data to the target domain.

4. A method according to any one of claims 1 to 3, characterized in that the method further comprises:

detecting whether the updating data is successfully synchronized;

if the synchronization is unsuccessful, acquiring the reason of unsuccessful synchronization, analyzing and processing the reason of unsuccessful synchronization, and acquiring a synchronization strategy for resynchronization of the updated data.

5. The method according to any one of claims 1 to 3, wherein the AD domain is used for storing a user identifier corresponding to user information in a first device hosting the AD domain, the LDAP domain is used for storing a user identifier corresponding to user information in a second device hosting the LDAP domain, and the AD domain and the LDAP domain have the same number range of the user identifiers which can be stored respectively.

6. The method of any of claims 1 to 3, wherein after synchronizing the update data into a target domain using a synchronization script, the method further comprises:

and after application data corresponding to the target user information is generated on the equipment carrying the target domain, storing the application data and the target user information in a home directory of shared storage.

7. An apparatus for synchronizing user information, the apparatus comprising:

the detection module is used for detecting whether the information synchronization condition is met;

the data acquisition module is used for acquiring the update data from the source domain if the information synchronization condition is met; the source domain is one of an AD domain and an LDAP domain, and the update data at least comprises target user information to be updated;

a synchronization module to synchronize the update data to a target domain using a synchronization script; the target domain is the other of the AD domain and the LDAP domain.

8. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor realizes the steps of the method of any one of claims 1 to 6 when executing the computer program.

9. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 6.

10. A computer program product comprising a computer program, characterized in that the computer program realizes the steps of the method of any one of claims 1 to 6 when executed by a processor.

Images