Skip to content
Data warehouse ⇄ Security and identity

Dremio to Onelogin integration — real-time, two-way sync

Keep Dremio and Onelogin 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 Dremio and Onelogin

Land the users, groups, and access events from Onelogin in Dremio 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; Dremio 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 Dremio. Getting them there usually means a brittle export that runs overnight and hands auditors a snapshot that is already out of date.

Stacksync syncs Events, Authentication factors (MFA), Custom user fields, Users from Onelogin into tables in Dremio in real time, and the connection works in both directions: values computed in Dremio, 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 Publish operational database tables into Iceberg via Dremio so the lakehouse reflects current application state.
  • 02 Consolidate data from multiple lake sources through one Dremio semantic layer into a single warehouse target.
  • 03 Read Users, Apps, and Groups into a database for identity, license, and app-assignment inventory across the OneLogin account.
  • 04 Two-way sync Users between OneLogin and an HRIS or Postgres so new hires, attribute changes, and terminations provision and deprovision SSO accounts automatically.

Common sync patterns

Directory data in the warehouse, minus the pipeline

Users, groups, and roles from Onelogin arrive in Dremio 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 Dremio, so security and compliance teams can query who reached what, and when, alongside the rest of the business's data.

Access governance on joined data

Join Onelogin's users and group memberships with HR, product, and usage data already in Dremio to surface who holds access they no longer need.

What you can sync between Dremio and Onelogin

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.

Dremio objects Onelogin objects How this pairing syncs
Reflections Materialized accelerations that make repeated extraction queries cheaper. Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. Reflections is specific to Dremio and Mappings (mapping rules) to Onelogin — each maps to any object or custom field on the other side.
Jobs Query execution records useful for monitoring sync workloads. Events Audit log of every authentication and admin action; read-only, filtered by since/until, and pushed live through the Event Webhook. Jobs is specific to Dremio and Events to Onelogin — each maps to any object or custom field on the other side.
Sources Connected storage and database systems (S3, ADLS, relational databases) Dremio queries in place. Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. Sources is specific to Dremio and Authentication factors (MFA) to Onelogin — each maps to any object or custom field on the other side.
Physical datasets Tables and files promoted from sources; the raw data a sync ultimately reads. Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. Physical datasets is specific to Dremio and Custom user fields to Onelogin — each maps to any object or custom field on the other side.
Virtual datasets (views) SQL views layering semantics over physical data; the preferred sync target for curated extracts. 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. Virtual datasets (views) is specific to Dremio and Users to Onelogin — each maps to any object or custom field on the other side.
Apache Iceberg tables Lakehouse tables supporting DML and snapshot metadata usable for incremental reads. Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. Apache Iceberg tables is specific to Dremio and Roles to Onelogin — each maps to any object or custom field on the other side.

How changes propagate between Dremio and Onelogin

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.

Dremio Onelogin Interval-based propagation

DetectionStacksync polls Dremio for changes on an incremental schedule, reading only records changed since the previous pass. Polling via SQL.

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

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

Rate-limit considerations

  • Dremio: Bounded by engine capacity and workload management rather than API rate limits.
  • 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.
What ships with Dremio ⇄ Onelogin

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dremio and Onelogin.

How the Dremio and Onelogin connectors work

Dremio

Integration surface
Arrow Flight SQL, JDBC/ODBC, and a REST API
Authentication
Personal access tokens or username/password; OAuth-based SSO on Dremio Cloud
Change detection
Polling via SQL; Iceberg table snapshots can anchor incremental reads; no consumer-facing change feed
Capabilities
read · write
Rate limits
Bounded by engine capacity and workload management rather than API rate limits

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.
How it works

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

    Choose tables

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

Dremio and Onelogin 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 432 integrations available for Dremio and Onelogin.

Popular · 8 of 432
All Dremio integrations All Onelogin 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