Skip to content
Database ⇄ Security and identity

Citus to Okta integration — real-time, two-way sync

Keep Citus and Okta 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 Citus and Okta

Close the gap between your application data and your directory: Citus and Okta share users, groups, and access in real time, in both directions.

Okta 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 Sequences, Distributed tables, Reference tables, Local tables in Citus with Policies, System Log, Devices, Users in Okta 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 Read Application assignments and Factors into a database to report on who can reach which app and which users have strong MFA enrolled.
  • 04 Drive Group Rules and policy assignments from HR attributes so access changes the moment a title, department, or location changes.

Common sync patterns

One profile, kept current

A name, department, email, or manager corrected in either system updates the other, so the profile the directory shows and the data the application reads stop drifting apart.

Provision accounts from the source of truth

When a person is added to the employee, member, or customer table in Citus, Stacksync creates the matching user in Okta with the right attributes, so access starts from live data instead of a manual ticket.

Deprovision the moment the record changes

When someone is marked inactive or removed in Citus, the matching account in Okta is disabled within seconds, closing the window between a departure and a login that still works.

What you can sync between Citus and Okta

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.

Citus objects Okta objects How this pairing syncs
Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. Group Rules Dynamic rules that add users to groups from profile attributes; read and written to automate access based on department, title, or location. Reference tables is specific to Citus and Group Rules to Okta — each maps to any object or custom field on the other side.
Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. Factors (Authenticators) MFA enrollments per user (Okta Verify, WebAuthn, SMS, email); read for security-posture reporting and reset when a device is lost or rotated. Local tables is specific to Citus and Factors (Authenticators) to Okta — each maps to any object or custom field on the other side.
Schemas Standard Postgres namespaces used to scope what a sync user can read and write. Policies Sign-on, password, and authenticator-enrollment policies with their rules; read to audit access controls or updated to manage them centrally. Schemas is specific to Citus and Policies to Okta — each maps to any object or custom field on the other side.
Views Curated projections over distributed data, often used as read-only sync sources. System Log Immutable audit event stream of logins, admin changes, and lifecycle events; read-only, polled by timestamp and used as the change feed and SIEM source. Views is specific to Citus and System Log to Okta — each maps to any object or custom field on the other side.
Sequences Key generators that matter when external writes must not collide with application inserts. Devices Registered and managed device records tied to users; read to correlate access with device posture and to feed inventory or conditional-access reporting. Sequences is specific to Citus and Devices to Okta — each maps to any object or custom field on the other side.
Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. Users Universal Directory user records with profile attributes, credentials, and lifecycle status (staged, active, suspended, deprovisioned); full CRUD, so users are created, updated, activated, and deactivated to match an HR or identity source. Distributed tables is specific to Citus and Users to Okta — each maps to any object or custom field on the other side.

How changes propagate between Citus and Okta

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.

Citus Okta 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 Okta through its API, with automatic retries and rate-limit backoff.

Okta Citus Sub-second propagation

DetectionOkta notifies Stacksync of record changes through webhook events. Event Hooks send an HTTPS POST to a subscribed endpoint on events such as user.lifecycle.create and group.user_membership.add (after a one-time.

DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Okta: Rate limits are enforced per org, per endpoint group, per minute and vary by Okta edition; responses carry X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Reset headers and exceeding one returns HTTP 429. The System Log is more tightly limited (about 120 requests/minute) and a separate concurrent-request cap (default 75 in-flight transactions) also applies.
What ships with Citus ⇄ Okta

Connect Citus and Okta for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Okta connection.

Real-time

Two-way sync

Changes in Citus or Okta instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Citus or Okta 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 Citus or Okta record.

Observability

Monitoring

Track your Citus ⇄ Okta sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Citus and Okta.

How the Citus and Okta connectors work

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

Okta

Integration surface
REST API (Okta Management API, /api/v1) with Event Hooks for outbound events and the System Log API as the change feed
Authentication
SSWS API tokens (Authorization: SSWS {token}) scoped to the creating admin's permissions, or OAuth 2.0 for Okta service apps using a private-key-JWT client-credentials grant with granular scopes (DPoP supported)
Change detection
Event Hooks send an HTTPS POST to a subscribed endpoint on events such as user.lifecycle.create and group.user_membership.add (after a one-time verification handshake); the System Log API (/api/v1/logs) is polled by the since parameter and the next Link header for a near-real-time change feed
Capabilities
read · write · webhooks
Rate limits
Rate limits are enforced per org, per endpoint group, per minute and vary by Okta edition; responses carry X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Reset headers and exceeding one returns HTTP 429. The System Log is more tightly limited (about 120 requests/minute) and a separate concurrent-request cap (default 75 in-flight transactions) also applies.
How it works

How to connect Citus to Okta — 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 Citus and Okta 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
    Citus connected
    Okta connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Citus and Okta 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 · Citus ⇄ Okta
    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
    Citus Okta
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Citus and Okta 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 430 integrations available for Citus and Okta.

Popular · 8 of 430
All Citus integrations All Okta 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