Skip to content
Developer tools ⇄ Data warehouse

Ldap to Starburst Enterprise integration — real-time, two-way sync

Keep Ldap and Starburst Enterprise 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 Ldap and Starburst Enterprise

Close the gap between analytics and operations: Starburst Enterprise holds the record while Ldap runs the day-to-day work, and Stacksync keeps the two in step in real time, in both directions.

Starburst Enterprise is the central store where teams keep Views, Materialized views, Columns, Catalogs 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 Organizational units (ou), Attributes, Operational attributes, Schema (subschema subentry) produced in Ldap are exactly what analysts want to measure in Starburst Enterprise, and the curated rows in Starburst Enterprise 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 Views, Materialized views, Columns, Catalogs in Starburst Enterprise with Organizational units (ou), Attributes, Operational attributes, Schema (subschema subentry) 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 Expose Iceberg or Hive lake tables to sync jobs through one SQL endpoint without moving the data first
  • 02 Consolidate reads from multiple databases behind a single connection instead of maintaining one integration per source
  • 03 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.
  • 04 Write user entries and group memberships into an LDAP directory from an HR system of record to drive downstream application access.

Common sync patterns

One shared record, kept consistent

Where both systems track the same entity, a change on either side propagates to the other, ending the manual reconciliation between the operational copy and the warehouse copy.

Keep user and access records aligned

Where Ldap manages users, directory, or access data, those records stay current in Starburst Enterprise — and can be provisioned back from it — so ownership and permissions match across both.

Operational data lands in Starburst Enterprise for analytics

Records created in Ldap — issues, events, messages, metrics, or user changes — replicate into Starburst Enterprise tables as they happen, so reporting runs on current data instead of last night's export.

What you can sync between Ldap and Starburst Enterprise

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.

Ldap objects Starburst Enterprise objects How this pairing syncs
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. Materialized views Precomputed results that make repeated sync reads cheaper. Attributes is specific to Ldap and Materialized views to Starburst Enterprise — each maps to any object or custom field on the other side.
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. Columns Typed per the Trino type system, mapped from each source's native types. Operational attributes is specific to Ldap and Columns to Starburst Enterprise — each maps to any object or custom field on the other side.
Schema (subschema subentry) The objectClass and attribute-type definitions the server exposes; read to validate that written attributes exist and are single- or multi-valued as expected. Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. Schema (subschema subentry) is specific to Ldap and Catalogs to Starburst Enterprise — each maps to any object or custom field on the other side.
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. Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. Entries is specific to Ldap and Schemas to Starburst Enterprise — each maps to any object or custom field on the other side.
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. Tables Queryable relations; writes pass through to sources whose connectors support them. Person entries (inetOrgPerson / user) is specific to Ldap and Tables to Starburst Enterprise — each maps to any object or custom field on the other side.
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. Views Engine-level SQL views used to shape federated data before syncing it out. Groups (groupOfNames / posixGroup) is specific to Ldap and Views to Starburst Enterprise — each maps to any object or custom field on the other side.

How changes propagate between Ldap and Starburst Enterprise

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.

Ldap Starburst Enterprise 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 Starburst Enterprise as a row-level write, with types converted between the two schemas.

Starburst Enterprise Ldap Interval-based propagation

DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.

DeliveryEach detected change is written to Ldap through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • 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.
  • Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with Ldap ⇄ Starburst Enterprise

Connect Ldap and Starburst Enterprise for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Ldap–Starburst Enterprise connection.

Real-time

Two-way sync

Changes in Ldap or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Ldap or Starburst Enterprise 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 Ldap or Starburst Enterprise record.

Observability

Monitoring

Track your Ldap ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Ldap and Starburst Enterprise.

How the Ldap and Starburst Enterprise connectors work

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.

Starburst Enterprise

Integration surface
ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
Authentication
Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
Change detection
Query-based polling; Starburst is a query engine and exposes no change log of its own
Capabilities
read · write
Rate limits
Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works

How to connect Ldap to Starburst Enterprise — 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.

  1. 01

    Connect your apps

    Authenticate Ldap and Starburst Enterprise with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Ldap connected
    Starburst Enterprise connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Ldap and Starburst Enterprise 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Ldap ⇄ Starburst Enterprise
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Ldap Starburst Enterprise
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Ldap and Starburst Enterprise integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 315 integrations available for Ldap and Starburst Enterprise.

Popular · 8 of 315
All Ldap integrations All Starburst Enterprise integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own