Skip to content
Security and identity ⇄ Data warehouse

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

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

Land the users, groups, and access events from Onelogin in Starburst Enterprise continuously for security analytics, and write computed results back — without building or maintaining a pipeline.

Onelogin is the record of who exists and what they can reach; Starburst Enterprise is where the business measures everything else. The two overlap on people and their access — the same users, groups, roles, and events that Onelogin governs are what security, compliance, and analytics teams want to query in Starburst Enterprise. Getting them there usually means a brittle export that runs overnight and hands auditors a snapshot that is already out of date.

Stacksync syncs Mappings (mapping rules), Events, Authentication factors (MFA), Custom user fields from Onelogin into tables in Starburst Enterprise in real time, and the connection works in both directions: values computed in Starburst Enterprise, such as risk scores or access-review decisions, can be written back to attributes in Onelogin where the identity team acts on them. Schema changes are handled, API limits are managed, and the sync is something you configure rather than a pipeline you keep alive.

Common use cases

  • 01 Consolidate reads from multiple databases behind a single connection instead of maintaining one integration per source
  • 02 Write curated or reconciled results back to lakehouse tables through connectors that support inserts
  • 03 Read the OneLogin Events audit log into a warehouse or SIEM for login analytics, access reviews, and SOC 2 audit evidence.
  • 04 Keep Role membership aligned with application or database entitlement tables so each role's assigned users match who should hold that access.

Common sync patterns

Risk and review results back on the account

Risk scores, anomaly flags, or access-review outcomes computed in Starburst Enterprise write back to attributes on the matching user in Onelogin, where the identity team can act on them.

Directory data in the warehouse, minus the pipeline

Users, groups, and roles from Onelogin arrive in Starburst Enterprise as queryable tables, current within seconds instead of a nightly directory export.

Access and sign-in analytics

Sign-in and access events from Onelogin land in Starburst Enterprise, so security and compliance teams can query who reached what, and when, alongside the rest of the business's data.

What you can sync between Onelogin 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.

Onelogin objects Starburst Enterprise objects How this pairing syncs
Events Audit log of every authentication and admin action; read-only, filtered by since/until, and pushed live through the Event Webhook. Tables Queryable relations; writes pass through to sources whose connectors support them. Events is specific to Onelogin and Tables to Starburst Enterprise — each maps to any object or custom field on the other side.
Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. Views Engine-level SQL views used to shape federated data before syncing it out. Authentication factors (MFA) is specific to Onelogin and Views to Starburst Enterprise — each maps to any object or custom field on the other side.
Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. Materialized views Precomputed results that make repeated sync reads cheaper. Custom user fields is specific to Onelogin and Materialized views to Starburst Enterprise — each maps to any object or custom field on the other side.
Users User accounts (email, username, custom attributes, status, roles); full CRUD via the v2 Users API - create, update, delete, set password, lock/unlock, and add or remove role assignments. Columns Typed per the Trino type system, mapped from each source's native types. Users is specific to Onelogin and Columns to Starburst Enterprise — each maps to any object or custom field on the other side.
Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. Roles is specific to Onelogin and Catalogs to Starburst Enterprise — each maps to any object or custom field on the other side.
Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. Apps (app instances) is specific to Onelogin and Schemas to Starburst Enterprise — each maps to any object or custom field on the other side.

How changes propagate between Onelogin 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.

Onelogin Starburst Enterprise Sub-second propagation

DetectionOnelogin notifies Stacksync of record changes through webhook events. Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time.

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

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

Rate-limit considerations

  • Onelogin: Account-level limit of 5,000 API calls per hour shared across all access tokens; responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, over-limit calls return HTTP 429, and the count resets each hour. Paid plans can request an increase.
  • Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with Onelogin ⇄ Starburst Enterprise

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Onelogin ⇄ 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 Onelogin and Starburst Enterprise.

How the Onelogin and Starburst Enterprise connectors work

Onelogin

Integration surface
OneLogin API (REST, v1 and v2 resource endpoints on <subdomain>.onelogin.com) plus the Event Webhook (Event Broadcaster) for event delivery
Authentication
OAuth 2.0 client credentials - an admin generates an API credential pair (client_id + client_secret) in the OneLogin portal and exchanges it at POST /auth/oauth2/v2/token for a bearer access token sent on every call; each credential carries a scope (Manage all, Manage users, Read users, etc.) that governs read vs write.
Change detection
Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time; the Events API also supports polling with since/until time filters and pagination for historical backfill.
Capabilities
read · write · webhooks
Rate limits
Account-level limit of 5,000 API calls per hour shared across all access tokens; responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, over-limit calls return HTTP 429, and the count resets each hour. Paid plans can request an increase.

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 Onelogin 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 Onelogin 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
    Onelogin connected
    Starburst Enterprise connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Onelogin 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 434 integrations available for Onelogin and Starburst Enterprise.

Popular · 8 of 434
All Onelogin 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