Identity Synchronization via Normalization Layer and Event Bus

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing identity management systems face challenges in consistency, efficiency, and usability due to the need for manual management of user identities across multiple systems with different protocols, leading to time-consuming synchronization and custom coding requirements.

Innovation Solution

A method and system for identity synchronization across multiple domains, utilizing a normalization layer to decouple identity data from source channel protocols, creating normalized event objects, and coupling them with target channel protocols for seamless data transmission, implemented on a distributed system for high throughput and scalability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If identity data is manually managed across multiple systems with different protocols, then each system can be configured independently, but synchronization time increases and consistency deteriorates

Engineering Contradiction:
Improvesystem independenceVSAvoidsynchronization time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent introduces an identity management system as an intermediary component that mediates between multiple enterprise systems. This intermediary handles protocol translation and identity data synchronization automatically, eliminating the need for manual management while maintaining system independence. The identity management system acts as a broker that receives identity data from one system and distributes it to other systems through appropriate protocol conversions.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If protocol-specific code is written for each system integration, then custom requirements can be met, but device complexity and development effort increase

Engineering Contradiction:
Improvecustom integration capabilityVSAvoidcustom coding requirements
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The identity management system implements a universal interface that can handle multiple protocols and system types through a single integrated platform. Rather than requiring separate protocol-specific code for each integration, the system provides a multi-functional architecture that automatically adapts to different protocols (such as LDAP, X.500, SQL) through configurable connection parameters and protocol handlers.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Loss of information

If identity data is accessed directly from multiple systems, then data availability is maintained, but reliability decreases due to synchronization errors

Engineering Contradiction:
Improvedata availabilityVSAvoidsynchronization accuracy
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The identity management system serves as a centralized intermediary that maintains the authoritative copy of identity data and distributes it to all connected systems. This mediator architecture ensures that all systems receive consistent, synchronized data from a single source of truth, eliminating synchronization errors that occur when systems access or modify data independently. The intermediary handles all data access requests and ensures atomic transactions across the distributed system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7702747B1Identity synchronization across multiple domains
Publication Date: 2010.04.20 ORACLE AMERICAN INC
  • US7702747B1 patent drawing
  • US7702747B1 patent drawing
  • US7702747B1 patent drawing

AI summary

A method for identity synchronization across multiple domains includes obtaining identity data from a source channel, wherein the identity data is associated with a source channel protocol, decoupling the identity data from the source channel protocol to obtain decoupled identity data, creating a normalized event object using the decoupled identity data, placing the normalized event object into an event bus, coupling the normalized event object with a target channel protocol to create a target-specific change object for a target channel, and forwarding the target-specific change object to the target channel.