Bi-directional Sync

Bi-directional Connectors

Sync identities in both directions across Active Directory, SQL Server, and File (CSV/TXT) with confidence-based conflict resolution. Extensible via the Connector SDK.

Why Bi-directional?

Always in Sync

Changes made in any connected system are automatically reflected everywhere. No more manual reconciliation or stale data.

Confidence-Based Resolution

When the same attribute is contributed by multiple sources, confidence scores on each flow rule determine which value wins — no manual conflict resolution needed.

Delta Sync

Watermark-based delta detection ensures only changed records are processed each sync run, keeping all systems current with minimal overhead.

How It Works

Three steps to enable bi-directional identity synchronization

1

Configure Both Connectors

Define source and target connectors with their connection details, authentication, and schema mappings.

// Active Directory connector — configured via Admin UI
Connector: "Corporate AD"
  Type: Active Directory
  Server: dc01.corp.local
  Base DN: DC=corp,DC=local
  Auth: Windows Negotiate
  Delta: uSNChanged watermark

// SQL Server connector — configured via Admin UI
Connector: "HR Database"
  Type: SQL Server
  Connection: (configured in Admin UI, stored encrypted)
  Import Query: SELECT * FROM Employees WHERE ModifiedDate > @watermark
  Delta Column: ModifiedDate
2

Define Sync Rules

Set up attribute mappings, conflict resolution strategies, and authoritative source rules.

// Every connector supports three operations:
//   Full import     — reads all objects from source
//   Delta import    — reads only changes since last watermark
//   Export          — writes pending changes to target
//
// Conflict resolution uses confidence scoring:
//   Each flow rule assigns a confidence (0-100) per attribute
//   Highest confidence value wins when multiple sources contribute
3

Monitor & Manage

Track sync health, monitor throughput, and manage conflicts from the admin dashboard.

Active Directory → MeshHealthy
12,847 objects importedLast run: 5 min ago
Mesh → SQL DatabaseHealthy
12,841 objects exportedLast run: 5 min ago

Use Cases

AD ↔ SQL Sync

Keep Active Directory and SQL Server databases in sync. Import users from AD into a central mesh, then export normalized identities to SQL-based applications and databases.

HR Database Integration

Import employee records from your HR database (SQL Server) and provision them into Active Directory with proper attributes, group memberships, and OU placement.

Custom Connectors

Build custom connectors with the Connector SDK. A connector implements full import, delta import, and export to integrate any identity source.

M&A Integration

During mergers and acquisitions, connect multiple AD forests and SQL databases to consolidate identities into a unified mesh with anchor-based correlation.

Ready to Enable Bi-directional Sync?

See how bi-directional connectors can eliminate identity silos across your organization.