Real-time
Two-way sync
Changes in Active Directory or Citus instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Database
Active Directory to Citus integration — real-time, two-way sync
Keep Active Directory and Citus 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 Active Directory and Citus
Close the gap between your application data and your directory: Citus and Active Directory share users, groups, and access in real time, in both directions.
Active Directory is the system of record for who people are and what they can reach: users, the groups they belong to, and the applications assigned to them. Citus holds the operational data those same people show up in, whether an employee or member table that decides who should have an account at all, a customers list, or the rows an application checks before it authorizes an action. The two describe overlapping users and groups, and when a nightly export or a hand-run script is all that connects them, accounts lag joiners and leavers and the application authorizes against a stale picture of who has access.
Stacksync syncs Distributed tables, Reference tables, Local tables, Schemas in Citus with Organizational contacts, Users, Groups, Group memberships in Active Directory field by field, in real time, and in both directions. You decide which system owns which fields, with the directory holding credentials and group membership and the database holding the source list of people who should exist at all, and Stacksync keeps every copy consistent, resolving conflicts by rules you set. A person added to a table becomes an account within seconds, a departure disables one just as fast, and the directory's users and groups are always present in your tables as ordinary rows.
Common use cases
- 01 Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
- 02 Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
- 03 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.
- 04 Read Devices and service principals into a database for identity, asset, and license inventory across the tenant.
Common sync patterns
Deprovision the moment the record changes
When someone is marked inactive or removed in Citus, the matching account in Active Directory is disabled within seconds, closing the window between a departure and a login that still works.
Read users and groups as ordinary tables
Users, groups, and their memberships from Active Directory land in Citus as rows your application and queries can join, so authorization checks and access reporting run against the database instead of the directory API.
Keep group and role membership aligned
A group or role change made in either system updates the other, so the entitlements an application enforces match what the directory grants.
What you can sync between Active Directory and Citus
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.
| Active Directory objects | Citus objects | How this pairing syncs | |
|---|---|---|---|
| Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. | Views Curated projections over distributed data, often used as read-only sync sources. | Groups is specific to Active Directory and Views to Citus — each maps to any object or custom field on the other side. | |
| Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. | Sequences Key generators that matter when external writes must not collide with application inserts. | Group memberships is specific to Active Directory and Sequences to Citus — each maps to any object or custom field on the other side. | |
| Devices Registered and joined device objects; typically read into a database for inventory and compliance reporting. | Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Devices is specific to Active Directory and Distributed tables to Citus — each maps to any object or custom field on the other side. | |
| Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. | Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Directory roles is specific to Active Directory and Reference tables to Citus — each maps to any object or custom field on the other side. | |
| Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. | Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Service principals & applications is specific to Active Directory and Local tables to Citus — each maps to any object or custom field on the other side. | |
| Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. | Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Organizational units is specific to Active Directory and Schemas to Citus — each maps to any object or custom field on the other side. |
How changes propagate between Active Directory and Citus
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.
Active Directory Citus Sub-second propagation
DetectionActive Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers.
DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.
Citus Active Directory Sub-second propagation
DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.
DeliveryEach detected change is written to Active Directory through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Active Directory: Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
What ships with Active Directory ⇄ Citus
Connect Active Directory and Citus for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Citus connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Active Directory or Citus 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 Active Directory or Citus record.
Observability
Monitoring
Track your Active Directory ⇄ Citus sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Active Directory and Citus.
How the Active Directory and Citus connectors work
Active Directory
- Integration surface
- Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS)
- Authentication
- OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS.
- Change detection
- Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling.
- Capabilities
- read · write · webhooks
- Rate limits
- Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
Citus
- Integration surface
- PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
- Authentication
- Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
- Change detection
- PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
- Capabilities
- read · write · CDC
How it works
How to connect Active Directory to Citus — 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 Active Directory and Citus with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Active Directory
connected
Citus
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Active Directory and Citus 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 · Active Directory ⇄ CitusCustomers 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.
Active Directory CitusCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Active Directory and Citus integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Citus: authenticate both systems, choose the objects to sync (such as Active Directory's Groups and Group memberships), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Active Directory: Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling. On Citus: PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Citus side: Distributed tables, Reference tables, Local tables, Schemas, plus custom fields where Citus exposes them. On the Active Directory side: Organizational contacts, Users, Groups, Group memberships. 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 Active Directory and Citus: Deprovision the moment the record changes; Read users and groups as ordinary tables; Keep group and role membership aligned. When someone is marked inactive or removed in Citus, the matching account in Active Directory is disabled within seconds, closing the window between a departure and a login that still works.
-
Active Directory: Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS). Authentication: OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS. Citus: PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node. Authentication: Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options). Stacksync manages authentication, retries, and rate limits on both sides.
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 430 integrations available for Active Directory and Citus.
Popular · 8 of 430
-
Active Directory ⇄ CockroachDB -
Active Directory ⇄ Google AlloyDB -
Active Directory ⇄ Dynamo DB -
Active Directory ⇄ IBM Db2 -
Citus ⇄ Okta -
Citus ⇄ Onelogin -
Citus ⇄ Auth0 -
Citus ⇄ Jumpcloud
No integrations match .
