Real-time
Two-way sync
Changes in Exasol or Ldap instantly reflect in both systems. No stale data, no manual imports.
Data warehouse ⇄ Developer tools
Exasol to Ldap integration — real-time, two-way sync
Keep Exasol and Ldap in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Exasol and Ldap
Close the gap between analytics and operations: Exasol holds the record while Ldap runs the day-to-day work, and Stacksync keeps the two in step in real time, in both directions.
Exasol is the central store where teams keep Users and roles, Schemas, Tables, Views for reporting and analysis; Ldap runs the operational side of engineering work — tracking issues, moving messages and events, watching systems, and managing users and access. The two overlap wherever the same operational data matters to both: the Entries, Person entries (inetOrgPerson / user), Groups (groupOfNames / posixGroup), Organizational units (ou) produced in Ldap are exactly what analysts want to measure in Exasol, and the curated rows in Exasol are what should drive the next action in Ldap. When that overlap is bridged by nightly ETL or hand-written scripts, dashboards lag a day behind reality and the tools that should react to warehouse signals never see them.
Stacksync syncs Users and roles, Schemas, Tables, Views in Exasol with Entries, Person entries (inetOrgPerson / user), Groups (groupOfNames / posixGroup), Organizational units (ou) in Ldap field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync matches records on a stable external key, keeps every copy consistent, and resolves conflicts by rules you set — so analytics and operations work from the same current data instead of two drifting copies.
Common use cases
- 01 Keep dimension tables such as customers and products aligned with the systems of record.
- 02 Load CRM and ERP records into Exasol tables on a schedule so analysts query fresh operational data.
- 03 Keep group member and uniqueMember attributes aligned with application entitlement tables so directory access reflects the right teams as they change.
- 04 Two-way sync person and group entries between an LDAP directory (OpenLDAP or AD DS) and an HRIS or Postgres so joiners, movers, and leavers provision and deprovision automatically.
Common sync patterns
Keep user and access records aligned
Where Ldap manages users, directory, or access data, those records stay current in Exasol — and can be provisioned back from it — so ownership and permissions match across both.
Operational data lands in Exasol for analytics
Records created in Ldap — issues, events, messages, metrics, or user changes — replicate into Exasol tables as they happen, so reporting runs on current data instead of last night's export.
Warehouse signals reach Ldap
A row scored, flagged, or enriched in Exasol creates or updates the matching record in Ldap, so the operational tool acts on the same data the analysts already see.
What you can sync between Exasol and Ldap
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Exasol objects | Ldap objects | How this pairing syncs | |
|---|---|---|---|
| Users and roles Grant read/write access for the dedicated integration account. | Entries The fundamental unit of an LDAP directory, each addressed by a distinguished name (DN) and typed by its objectClass; synced two-way as records, with the DN driving upserts and attribute-level updates. | Users and roles is specific to Exasol and Entries to Ldap — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that group the tables a sync reads from or writes into. | Person entries (inetOrgPerson / user) People held under objectClasses such as inetOrgPerson, person, or Active Directory user; synced two-way to create accounts and update attributes like mail, cn, and telephoneNumber. | Schemas is specific to Exasol and Person entries (inetOrgPerson / user) to Ldap — each maps to any object or custom field on the other side. | |
| Tables Primary sync target; columnar relational tables written with standard SQL. | Groups (groupOfNames / posixGroup) Group entries whose member or uniqueMember attributes list DNs; synced two-way to add and remove membership as teams and entitlements change. | Tables is specific to Exasol and Groups (groupOfNames / posixGroup) to Ldap — each maps to any object or custom field on the other side. | |
| Views Read-only query surfaces often used as curated sources for reverse ETL. | Organizational units (ou) Container entries that structure the DIT and scope which subtree a sync reads or writes; used to limit a sync to a branch such as ou=People,dc=corp,dc=com. | Views is specific to Exasol and Organizational units (ou) to Ldap — each maps to any object or custom field on the other side. | |
| Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. | Attributes The typed name/value pairs on each entry (cn, mail, memberOf, objectClass); the schema defines which attributes each objectClass allows, and mappings are built per attribute. | Virtual schemas is specific to Exasol and Attributes to Ldap — each maps to any object or custom field on the other side. | |
| UDF scripts In-database functions that can transform synced data after load. | Operational attributes Server-maintained metadata such as modifyTimestamp, createTimestamp, entryUUID, entryCSN, and uSNChanged; read to drive incremental polling and to key entries stably across syncs. | UDF scripts is specific to Exasol and Operational attributes to Ldap — each maps to any object or custom field on the other side. |
How changes propagate between Exasol and Ldap
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Exasol Ldap Interval-based propagation
DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.
DeliveryEach detected change is written to Ldap through its API, with automatic retries and rate-limit backoff.
Ldap Exasol Interval-based propagation
DetectionStacksync polls Ldap for changes on an incremental schedule, reading only records changed since the previous pass. No universal native change feed.
DeliveryEach detected change is applied to Exasol as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Exasol: No API quota; concurrency is bounded by cluster resources and session limits.
- Ldap: LDAP defines no request quota; throughput is bounded by the server's sizelimit and timelimit administrative limits, connection and thread caps, and the CPU/IO it shares with live authentication traffic, so large syncs can contend with production lookups and must page results.
What ships with Exasol ⇄ Ldap
Connect Exasol and Ldap for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Exasol–Ldap connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Exasol or Ldap data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Exasol or Ldap record.
Observability
Monitoring
Track your Exasol ⇄ Ldap sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Exasol and Ldap.
How the Exasol and Ldap connectors work
Exasol
- Integration surface
- SQL over JDBC/ODBC drivers and a WebSocket-based client protocol
- Authentication
- Database credentials (username and password)
- Change detection
- Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients
- Capabilities
- read · write
- Rate limits
- No API quota; concurrency is bounded by cluster resources and session limits
Ldap
- Integration surface
- LDAPv3 protocol (RFC 4511) over TCP, typically LDAPS on port 636 or StartTLS on 389; reaches any LDAPv3 directory server - OpenLDAP, Microsoft Active Directory, 389 Directory Server, Oracle Unified Directory, PingDS/ForgeRock, NetIQ eDirectory, Apache Directory.
- Authentication
- A bind DN and password (simple bind), typically over TLS, using a service account with rights to the target subtree. SASL mechanisms - GSSAPI/Kerberos, DIGEST-MD5, or EXTERNAL with a client certificate - are available where the server supports them.
- Change detection
- No universal native change feed. Incremental sync polls the modifyTimestamp operational attribute (or entryCSN / uSNChanged on servers that expose them) for entries changed since the last cursor; detecting deletes needs a server changelog or tombstones because a plain search cannot see removed entries. Some servers add Persistent Search or RFC 4533 content-sync (syncrepl), but that support is server-specific. No webhooks.
- Capabilities
- read · write
- Rate limits
- LDAP defines no request quota; throughput is bounded by the server's sizelimit and timelimit administrative limits, connection and thread caps, and the CPU/IO it shares with live authentication traffic, so large syncs can contend with production lookups and must page results.
How it works
How to connect Exasol to Ldap — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Exasol and Ldap with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Exasol
connected
Ldap
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Exasol and Ldap objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Exasol ⇄ LdapCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Exasol LdapCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Exasol and Ldap integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Exasol and Ldap: authenticate both systems, choose the objects to sync (such as Exasol's Users and roles and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Exasol side: Users and roles, Schemas, Tables, Views, plus custom fields where Exasol exposes them. On the Ldap side: Entries, Person entries (inetOrgPerson / user), Groups (groupOfNames / posixGroup), Organizational units (ou). Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Exasol and Ldap: Keep user and access records aligned; Operational data lands in Exasol for analytics; Warehouse signals reach Ldap. Where Ldap manages users, directory, or access data, those records stay current in Exasol — and can be provisioned back from it — so ownership and permissions match across both.
-
Exasol: SQL over JDBC/ODBC drivers and a WebSocket-based client protocol. Authentication: Database credentials (username and password). Ldap: LDAPv3 protocol (RFC 4511) over TCP, typically LDAPS on port 636 or StartTLS on 389; reaches any LDAPv3 directory server - OpenLDAP, Microsoft Active Directory, 389 Directory Server, Oracle Unified Directory, PingDS/ForgeRock, NetIQ eDirectory, Apache Directory. Authentication: A bind DN and password (simple bind), typically over TLS, using a service account with rights to the target subtree. SASL mechanisms - GSSAPI/Kerberos, DIGEST-MD5, or EXTERNAL with a client certificate - are available where the server supports them. Stacksync manages authentication, retries, and rate limits on both sides.
-
Exasol: Virtual schemas let Exasol query external sources in place, which affects whether data needs to be physically synced at all. Ldap: LDAP is a protocol (RFC 4511), not a product; it reaches any LDAPv3 directory - OpenLDAP, Active Directory, 389 Directory Server, Oracle Unified Directory, eDirectory - and server-specific behavior like changelogs and controls varies. Stacksync's field mapping accounts for these differences between Exasol and Ldap without custom code.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 311 integrations available for Exasol and Ldap.
Popular · 6 of 311
-
Exasol ⇄ Jms -
Exasol ⇄ Newrelic -
Exasol ⇄ Opsgenie -
Ldap ⇄ Databricks -
Ldap ⇄ AWS S3 -
Ldap ⇄ Amazon Redshift
No integrations match .
