Skip to content
Security and identity ⇄ Data warehouse

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

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

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

Stacksync syncs Roles, Apps (app instances), Groups, Mappings (mapping rules) from Onelogin into tables in Rockset in real time, and the connection works in both directions: values computed in Rockset, 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 Serve real-time dashboards over CRM and ERP records synced from operational databases.
  • 02 Sync Postgres or DynamoDB tables into collections for low-latency aggregations without loading a batch warehouse.
  • 03 Keep Role membership aligned with application or database entitlement tables so each role's assigned users match who should hold that access.
  • 04 Read Users, Apps, and Groups into a database for identity, license, and app-assignment inventory across the OneLogin account.

Common sync patterns

Risk and review results back on the account

Risk scores, anomaly flags, or access-review outcomes computed in Rockset 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 Rockset 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 Rockset, 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 Rockset

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 Rockset objects How this pairing syncs
Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. Collections Schemaless document containers that ingested and synced records land in. Apps (app instances) is specific to Onelogin and Collections to Rockset — each maps to any object or custom field on the other side.
Groups Account groups used for mapping and reporting; listed and read through the API, which has no create or update endpoint, so groups are read-only. Documents JSON records addressable by _id, written via the Write API in sync pipelines. Groups is specific to Onelogin and Documents to Rockset — each maps to any object or custom field on the other side.
Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. Workspaces Namespaces that group collections and query lambdas per team or environment. Mappings (mapping rules) is specific to Onelogin and Workspaces to Rockset — each maps to any object or custom field on the other side.
Events Audit log of every authentication and admin action; read-only, filtered by since/until, and pushed live through the Event Webhook. Query Lambdas Named, parameterized SQL queries invoked over REST to read synced data. Events is specific to Onelogin and Query Lambdas to Rockset — 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. Aliases Stable names that point at collections, used to swap datasets without changing queries. Authentication factors (MFA) is specific to Onelogin and Aliases to Rockset — 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. Integrations Managed source connections (databases, streams, object storage) feeding collections. Custom user fields is specific to Onelogin and Integrations to Rockset — each maps to any object or custom field on the other side.

How changes propagate between Onelogin and Rockset

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

Rockset Onelogin Interval-based propagation

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

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.
What ships with Onelogin ⇄ Rockset

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Onelogin ⇄ Rockset 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 Rockset.

How the Onelogin and Rockset 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.

Rockset

Integration surface
REST API (SQL over HTTP, plus a document Write API)
Authentication
API key
Change detection
Polling via SQL queries on timestamp fields; ingestion-side change capture is handled by Rockset's managed source connectors
Capabilities
read · write
How it works

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

    Choose tables

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

Onelogin and Rockset 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 500 integrations available for Onelogin and Rockset.

Popular · 7 of 500
All Onelogin integrations All Rockset 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