Event-driven identity data synchronization method

Abstract

The invention provides a method for synchronizing identity data based on event driving. The method comprises the following steps: S1, event subscription; s2, event monitoring; s3, task scheduling; s4, data processing; s5, sending the data; s6, receiving the data; s7, state feedback; and S8, logging and auditing. According to the event-driven identity data synchronization method provided by the invention, through an intelligent and real-time data processing strategy, a plurality of pain points in a traditional timing synchronization mode are effectively solved, the real-time performance and accuracy of data synchronization and the utilization efficiency of system resources are remarkably improved, and the method has great significance in constructing efficient and reliable digital infrastructures and has great significance in the field of data synchronization. The method has important significance in supporting enterprises or organizations to keep competitive power in a rapidly changing market environment, a traditional data synchronization mode is changed fundamentally, real-time sensing, instant processing and accurate synchronization of identity data changes are achieved, and therefore the consistency and timeliness of data and the use efficiency of system resources are greatly improved.

Description

Technical Field

[0001] The present invention relates to the field of information technology security and management, and in particular to a method for synchronizing identity data based on event-driven synchronization. Background Art

[0002] In the era of digital transformation, the complexity of information systems is increasing day by day. Especially for large enterprises or government agencies, it is particularly important to maintain a unified and accurate identity information management system. Identity data, including user profiles, organizational structure information, etc., is the basis for supporting the smooth progress of various business processes. However, with the diversification and decentralization of business systems, how to maintain the consistency and real-time nature of identity data between multiple systems has become a key issue that needs to be solved in the field of information technology.

[0003] Although the traditional scheduled synchronization mechanism has alleviated the problem of data inconsistency to a certain extent, its inherent defects are becoming increasingly prominent: first, the scheduled synchronization strategy often sets a fixed period (such as once every hour or every day), which means that during the period between two synchronizations, new data changes cannot be immediately reflected in all related systems, causing data delays; second, scheduled synchronization will be executed regardless of whether the data has changed, which not only wastes computing resources, but also may cause unnecessary burden on system performance; third, faced with large-scale data sets or high-frequency change scenarios, the scheduled synchronization mechanism is difficult to respond effectively, which can easily lead to data processing bottlenecks.

[0004] Therefore, it is necessary to provide a method for event-driven identity data synchronization to solve the above technical problems. Summary of the invention

[0005] The present invention provides a method for synchronizing identity data based on event-driven, which solves the problem that new data changes generated by the traditional timing synchronization mechanism cannot be immediately reflected in all related systems, causing data delay. The execution will be performed regardless of whether the data has changed, which not only wastes computing resources, but also may cause unnecessary burden on system performance.

[0006] In order to solve the above technical problems, the present invention provides a method for synchronizing identity data based on event-driven, comprising the following steps:

[0007] S1: Event subscription: Subscribers subscribe to identity change events of interest through the management interface or API, covering various operations related to users and organizations, such as creation, deletion, update, password change, enablement and disablement, and register the data synchronization receiving API address;

[0008] S2: Event Listener: An efficient event listener is embedded in the identity source system, which can capture the change events of user and organizational identities in real time and generate event notifications immediately.

[0009] S3: Task scheduling: When an event occurs, the importance of data changes and synchronization priority are logically determined based on the event type and subscriber configuration information, and the corresponding asynchronous data synchronization task is triggered;

[0010] S4: Data processing: Parse the captured event data, extract key information, and convert the event data into the format required by the subscriber according to the preset data conversion rules;

[0011] S5: Data sending: Use JWT to digitally sign the event content and securely send the signed data to the subscriber through an encrypted HTTP POST request;

[0012] S6: Data reception: After receiving the data, the subscriber first performs JWT signature verification to ensure that the data has not been tampered with during transmission, and then updates the converted data to the database or data storage;

[0013] S7: Status feedback: After the data update is completed, the subscriber sends detailed execution status feedback to the synchronization service, including success, failure, or retry indication, to achieve closed-loop feedback;

[0014] S8: Log and Audit: Real-time monitoring of the status and progress of synchronization tasks, and recording of the source, target, and timestamp of each operation, thereby achieving transparency, compliance, and traceability of the data synchronization process.

[0015] Preferably, the event subscription allows business applications to subscribe to specific types of data change events as needed, such as user creation, deletion, update, password change, enablement and disablement, organization creation, deletion, update, member change, etc., and by defining precise event filtering rules, ensure that only subscribed events are captured. Each subscriber needs to provide one or more callback API addresses when registering. When relevant events occur, these API addresses will be called to trigger data synchronization operations.

[0016] Preferably, the event listener is a high-performance, low-latency event listening system, which captures any events related to user or organization identity data by real-time monitoring of database transaction logs, message queues or API calls of identity data sources. The event listener has efficient event identification and filtering capabilities to ensure that event notifications are generated only for data that has actually changed.

[0017] Preferably, after receiving the notification from the event monitoring module, the task scheduling logically determines the importance of the data change and the synchronization priority according to the subscription configuration information, and triggers the corresponding asynchronously scheduled data synchronization task.

[0018] Preferably, the task scheduling center has task scheduling and load balancing capabilities to ensure efficient and stable operation under high-concurrency change events.

[0019] Preferably, after the event is triggered, the system first parses the original event data, and then converts it into the format required by the subscriber according to the preset processing rules. Data conversion supports high customization, allowing users to configure conversion logic, including field mapping, data type conversion, and even embedding complex business logic to ensure data compatibility and accuracy.

[0020] Preferably, the data sends the processed data and immediately enters the synchronous callback execution phase. First, the transmitted event content is signed in JWT format and sent to the event subscriber via HTTP POST.

[0021] Preferably, the data receiver performs JWT signature verification on the received synchronization event content to confirm whether the synchronization request is from a valid source to prevent counterfeit requests. Only after the verification is passed will the data be updated and stored on the subscriber side.

[0022] Preferably, after receiving the status feedback data, the system needs to send detailed execution status feedback to the synchronization service, including the operation result, whether it is successful, and the error code and description in case of failure, to provide a basis for subsequent error handling and monitoring.

[0023] Preferably, in order to ensure compliance and traceability, the log and audit records system comprehensively records all event subscriptions, data conversion, and synchronous execution processes, including timestamps, event content, operation details, result feedback, etc. These logs are not only used for daily operation and maintenance analysis, but also serve as a key source of information for security audits and troubleshooting.

[0024] Compared with the related art, the method for synchronizing identity data based on event-driven provided by the present invention has the following beneficial effects:

[0025] The present invention provides a method for synchronizing identity data based on event-driven. Through intelligent and real-time data processing strategies, it effectively solves many pain points in the traditional timed synchronization mode, significantly improves the real-time performance, accuracy and utilization efficiency of system resources of data synchronization, and is of great significance for building an efficient and reliable digital infrastructure and supporting enterprises or organizations to maintain competitiveness in a rapidly changing market environment. It has the advantages of efficient resource utilization, flexibility and scalability, security and compliance assurance, and intelligent decision-making. The real-time performance and accuracy are improved. The event-driven mechanism ensures that data changes are captured and processed instantly, eliminating the delay of traditional timed synchronization, improving the consistency and real-time of data, and triggering synchronization only when the data actually changes, which greatly reduces unnecessary calculations and network latency. It reduces network resource consumption and improves the overall system operation efficiency and response speed. Through modular design and configuration management, the system can easily cope with changes such as new system access and synchronization strategy adjustment, providing a solid foundation for future business expansion and technology upgrades. The selection of event processing and synchronization strategies fully considers business logic and system status, realizes intelligent scheduling of synchronization operations, further optimizes synchronization efficiency and system stability, and improves monitoring, logging and auditing mechanisms to ensure the transparency and traceability of the data processing process, comply with data protection regulations, enhance the system's security protection capabilities, fundamentally change the traditional synchronization mode, and realize real-time perception, instant processing and accurate synchronization of identity data changes, thereby greatly improving data consistency, timeliness and system resource utilization efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 A schematic diagram of the structure of a method for event-driven identity data synchronization provided by the present invention. DETAILED DESCRIPTION

[0027] The present invention will be further described below in conjunction with the accompanying drawings and implementation modes.

[0028] Please refer to Figure 1 ,in, Figure 1 A schematic diagram of a method for event-driven identity data synchronization provided by the present invention. A method for event-driven identity data synchronization comprises the following steps: S1: Event subscription: Subscribers subscribe to identity change events of interest through a management interface or API, covering various operations related to users and organizations, such as creation, deletion, update, password change, enablement and disablement, and register a data synchronization receiving API address;

[0029] S2: Event Listener: An efficient event listener is embedded in the identity source system, which can capture the change events of user and organizational identities in real time and generate event notifications immediately.

[0030] S3: Task scheduling: When an event occurs, the importance of data changes and synchronization priority are logically determined based on the event type and subscriber configuration information, and the corresponding asynchronous data synchronization task is triggered;

[0031] S4: Data processing: Parse the captured event data, extract key information, and convert the event data into the format required by the subscriber according to the preset data conversion rules;

[0032] S5: Data sending: Use JWT to digitally sign the event content and securely send the signed data to the subscriber through an encrypted HTTP POST request;

[0033] S6: Data reception: After receiving the data, the subscriber first performs JWT signature verification to ensure that the data has not been tampered with during transmission, and then updates the converted data to the database or data storage;

[0034] S7: Status feedback: After the data update is completed, the subscriber sends detailed execution status feedback to the synchronization service, including success, failure, or retry indication, to achieve closed-loop feedback;

[0035] S8: Log and Audit: Real-time monitoring of the status and progress of synchronization tasks, and recording of the source, target, and timestamp of each operation, thereby achieving transparency, compliance, and traceability of the data synchronization process.

[0036] The event subscription allows business applications to subscribe to specific types of data change events as needed, such as user creation, deletion, update, password change, enablement and disablement, organization creation, deletion, update, member change, etc., and ensures that only subscribed events are captured by defining precise event filtering rules. Each subscriber needs to provide one or more callback API addresses when registering. When related events occur, these API addresses will be called to trigger data synchronization operations.

[0037] The event listener is a high-performance, low-latency event listening system that captures any events related to user or organization identity data by real-time monitoring of database transaction logs, message queues or API calls of identity data sources. The event listener has efficient event identification and filtering capabilities to ensure that event notifications are generated only for data that has actually changed.

[0038] After receiving the notification from the event monitoring module, the task scheduling logically determines the importance of data changes and synchronization priority according to the subscription configuration information, and triggers the corresponding asynchronously scheduled data synchronization task.

[0039] The task scheduling center has task scheduling and load balancing capabilities to ensure efficient and stable operation under high-concurrency change events.

[0040] After the event is triggered, the system first parses the original event data, and then converts it into the format required by the subscriber according to the preset processing rules. Data conversion supports high customization, allowing users to configure conversion logic, including field mapping, data type conversion, and even embedding complex business logic to ensure data compatibility and accuracy.

[0041] The data sends the processed data and immediately enters the synchronous callback execution phase. First, the transmitted event content will be signed in JWT format and sent to the event subscriber via HTTP POST.

[0042] The data recipient performs JWT verification on the received synchronization event content to confirm whether the synchronization request is from a valid source to prevent counterfeit requests. Only after the verification is passed will the data be updated and stored on the subscriber side.

[0043] After receiving the status feedback data, the system needs to send detailed execution status feedback to the synchronization service, including the operation result, whether it is successful, and the error code and description in case of failure, to provide a basis for subsequent error handling and monitoring.

[0044] To ensure compliance and traceability, the log and audit records comprehensively record all event subscriptions, data conversions, and synchronous execution processes, including timestamps, event content, operation details, result feedback, etc. These logs are not only used for daily operation and maintenance analysis, but also serve as a key source of information for security audits and troubleshooting.

[0045] Assume that in a large enterprise environment, the human resource management system (HRMS) is the main source of identity data and needs to synchronize employee information to multiple downstream systems such as the email system and the rights management system in real time. The implementation process of the present invention is as follows:

[0046] (1) Event subscription: Subscribe to and configure key events such as employee joining, leaving, and job change in HRMS, and register email system and permission management system API callback addresses.

[0047] (2) Event monitoring: Filter out events that really need to be synchronized, such as responding only to changes in key fields (such as position and department).

[0048] (3) Event processing and scheduling: After receiving an event, the center automatically converts the data format and intelligently arranges the synchronization task priority based on the event type and target system status.

[0049] (4) Synchronous execution: The synchronization engine adopts an incremental synchronization strategy, extracting and converting only the changed data and transmitting it to the target system through an encrypted channel.

[0050] (5) Logging and auditing: Log synchronization operations throughout the process, monitor the status and progress of synchronization tasks, and record the source, target, and timestamp of each operation to achieve transparency, compliance, and traceability of the data synchronization process.

[0051] The working principle of the event-driven identity data synchronization method provided by the present invention is as follows:

[0052] When working, first allow business applications to subscribe to specific types of data change events as needed, such as user creation, deletion, update, password change, enable and disable, organization creation, deletion, update, member change, etc. By defining precise event filtering rules, ensure that only subscribed events are captured. Each subscriber needs to provide one or more callback API addresses when registering. When related events occur, these API addresses will be called to trigger data synchronization operations.

[0053] A high-performance, low-latency event listening system that captures any events related to user or organization identity data by real-time monitoring of the database transaction log, message queue or API call of the identity data source. The event listener has efficient event identification and filtering capabilities to ensure that event notifications are generated only for data that has actually changed.

[0054] After receiving notifications from the event monitoring module, the center will logically determine the importance of data changes and synchronization priorities based on the subscription configuration information, and trigger the corresponding asynchronously scheduled data synchronization tasks. This center must also have task scheduling and load balancing capabilities to ensure efficient and stable operation under high-concurrency change events.

[0055] After an event is triggered, the system first parses the original event data, and then converts it into the format required by the subscriber according to the preset processing rules. Data conversion supports high customization, allowing users to configure conversion logic, including field mapping, data type conversion, and even embedding complex business logic to ensure data compatibility and accuracy.

[0056] The processed data immediately enters the callback execution phase. First, the passed event content will be signed in JWT format and sent to the event subscriber via HTTP POST.

[0057] The received synchronization event content is verified by JWT to confirm whether the synchronization request is from a valid source to prevent counterfeit requests. Only after the verification is passed will the data be updated and stored on the subscriber side.

[0058] After data reception is completed, the system needs to send detailed execution status feedback to the synchronization service, including the operation result, whether it is successful, and the error code and description in case of failure, to provide a basis for subsequent error handling and monitoring.

[0059] To ensure compliance and traceability, the system comprehensively records all event subscriptions, data conversions, and synchronous execution processes, including timestamps, event content, operation details, result feedback, etc. These logs are not only used for daily operation and maintenance analysis, but also serve as a key source of information for security audits and troubleshooting.

[0060] Compared with the related art, the method for synchronizing identity data based on event-driven provided by the present invention has the following beneficial effects:

[0061] The present invention provides a method for synchronizing identity data based on event-driven. Through intelligent and real-time data processing strategies, it effectively solves many pain points in the traditional timed synchronization mode, significantly improves the real-time performance, accuracy and utilization efficiency of system resources of data synchronization, and is of great significance for building an efficient and reliable digital infrastructure and supporting enterprises or organizations to maintain competitiveness in a rapidly changing market environment. It has the advantages of efficient resource utilization, flexibility and scalability, security and compliance assurance, and intelligent decision-making. The real-time performance and accuracy are improved. The event-driven mechanism ensures that data changes are captured and processed instantly, eliminating the delay of traditional timed synchronization, improving the consistency and real-time of data, and triggering synchronization only when the data actually changes, which greatly reduces unnecessary calculations and network latency. It reduces network resource consumption and improves the overall system operation efficiency and response speed. Through modular design and configuration management, the system can easily cope with changes such as new system access and synchronization strategy adjustment, providing a solid foundation for future business expansion and technology upgrades. The selection of event processing and synchronization strategies fully considers business logic and system status, realizes intelligent scheduling of synchronization operations, further optimizes synchronization efficiency and system stability, and improves monitoring, logging and auditing mechanisms to ensure the transparency and traceability of the data processing process, comply with data protection regulations, enhance the system's security protection capabilities, fundamentally change the traditional synchronization mode, and realize real-time perception, instant processing and accurate synchronization of identity data changes, thereby greatly improving data consistency, timeliness and system resource utilization efficiency.

[0062] The above descriptions are merely embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A method for synchronizing identity data based on event-driven, characterized in that: The following steps are involved: S1: Event subscription: Subscribers subscribe to identity change events of interest through the management interface or API, covering various operations related to users and organizations, such as creation, deletion, update, password change, enablement and disablement, and register the data synchronization receiving API address; S2: Event Listener: An efficient event listener is embedded in the identity source system, which can capture the change events of user and organizational identities in real time and generate event notifications immediately. S3: Task scheduling: When an event occurs, the importance of data changes and synchronization priority are logically determined based on the event type and subscriber configuration information, and the corresponding asynchronous data synchronization task is triggered; S4: Data processing: Parse the captured event data, extract key information, and convert the event data into the format required by the subscriber according to the preset data conversion rules; S5: Data sending: Use JWT to digitally sign the event content and securely send the signed data to the subscriber through an encrypted HTTP POST request; S6: Data reception: After receiving the data, the subscriber first performs JWT signature verification to ensure that the data has not been tampered with during transmission, and then updates the converted data to the database or data storage; S7: Status feedback: After the data update is completed, the subscriber sends detailed execution status feedback to the synchronization service, including success, failure, or retry indication, to achieve closed-loop feedback; S8: Log and Audit: Real-time monitoring of the status and progress of synchronization tasks, and recording of the source, target, and timestamp of each operation, thereby achieving transparency, compliance, and traceability of the data synchronization process.

2. The method for synchronizing identity data based on event-driven according to claim 1, characterized in that: The event subscription allows business applications to subscribe to specific types of data change events as needed, such as user creation, deletion, update, password change, enablement and disablement, organization creation, deletion, update, and member change, and ensures that only subscribed events are captured by defining precise event filtering rules. Each subscriber needs to provide one or more callback API addresses when registering. When related events occur, these API addresses will be called to trigger data synchronization operations.

3. The method for synchronizing identity data based on event-driven according to claim 1, characterized in that: The event listener is a high-performance, low-latency event listening system that captures any events related to user or organization identity data by real-time monitoring of the database transaction log, message queue or API call path of the identity data source. The event listener has efficient event identification and filtering capabilities to ensure that event notifications are generated only for data that has actually changed.

4. The method for event-driven identity data synchronization according to claim 1, characterized in that: After receiving the notification from the event monitoring module, the task scheduling logically determines the importance of data changes and synchronization priority according to the subscription configuration information, and triggers the corresponding asynchronously scheduled data synchronization task.

5. The method for synchronizing identity data based on event-driven according to claim 4, characterized in that: The task scheduling center has task scheduling and load balancing capabilities to ensure efficient and stable operation under high-concurrency change events.

6. The method for event-driven identity data synchronization according to claim 4, characterized in that: After the event is triggered, the system first parses the original event data, and then converts it into the format required by the subscriber according to the preset processing rules. Data conversion supports high customization, allowing users to configure conversion logic, including field mapping, data type conversion, and even embedding complex business logic to ensure data compatibility and accuracy.

7. The method for synchronizing identity data based on event-driven according to claim 4, characterized in that: The data sends the processed data and immediately enters the synchronous callback execution phase. First, the transmitted event content will be signed in JWT format and sent to the event subscriber via HTTP POST.

8. The method for synchronizing identity data based on event-driven according to claim 4, characterized in that: The data recipient performs JWT verification on the received synchronization event content to confirm whether the synchronization request is from a valid source to prevent counterfeit requests. Only after the verification is passed will the data be updated and stored on the subscriber side.

9. The method for synchronizing identity data based on event-driven according to claim 4, characterized in that: After receiving the status feedback data, the system needs to send detailed execution status feedback to the synchronization service, including the operation result, whether it is successful, and the error code and description in case of failure, to provide a basis for subsequent error handling and monitoring.

10. The method for synchronizing identity data based on event-driven according to claim 4, characterized in that: To ensure compliance and traceability, the log and audit records comprehensively record all event subscriptions, data conversions, and synchronous execution processes, including timestamps, event content, operation details, and result feedback. These logs are not only used for daily operation and maintenance analysis, but also serve as a key source of information for security audits and troubleshooting.

Images