Two-way sync
Changes in Cloudera Data Platform or Onelogin instantly reflect in both systems. No stale data, no manual imports.
Keep Cloudera Data Platform 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.
Onelogin is the record of who exists and what they can reach; Cloudera Data Platform 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 Cloudera Data Platform. Getting them there usually means a brittle export that runs overnight and hands auditors a snapshot that is already out of date.
Stacksync syncs Apps (app instances), Groups, Mappings (mapping rules), Events from Onelogin into tables in Cloudera Data Platform in real time, and the connection works in both directions: values computed in Cloudera Data Platform, 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.
Sign-in and access events from Onelogin land in Cloudera Data Platform, so security and compliance teams can query who reached what, and when, alongside the rest of the business's data.
Join Onelogin's users and group memberships with HR, product, and usage data already in Cloudera Data Platform to surface who holds access they no longer need.
A continuously synced copy in Cloudera Data Platform gives you a durable, queryable record of identity and access state for access reviews, SOC 2, and audit questions.
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.
| Cloudera Data Platform objects | Onelogin objects | How this pairing syncs | |
|---|---|---|---|
| Partitions Table partitions (often by date) that incremental extraction jobs use to scope reads. | 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. | Partitions is specific to Cloudera Data Platform and Groups to Onelogin — each maps to any object or custom field on the other side. | |
| Object store / HDFS files Underlying Parquet or ORC files on HDFS or cloud storage backing the tables. | Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. | Object store / HDFS files is specific to Cloudera Data Platform and Mappings (mapping rules) to Onelogin — each maps to any object or custom field on the other side. | |
| Databases Logical namespaces in the shared Hive Metastore that group tables for access control and syncs. | Events Audit log of every authentication and admin action; read-only, filtered by since/until, and pushed live through the Event Webhook. | Databases is specific to Cloudera Data Platform and Events to Onelogin — each maps to any object or custom field on the other side. | |
| Hive tables Warehouse tables queried over JDBC/ODBC; classic managed tables are append-oriented. | Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. | Hive tables is specific to Cloudera Data Platform and Authentication factors (MFA) to Onelogin — each maps to any object or custom field on the other side. | |
| Impala tables The same metastore tables served through Impala for lower-latency SQL reads. | Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. | Impala tables is specific to Cloudera Data Platform and Custom user fields to Onelogin — each maps to any object or custom field on the other side. | |
| Kudu tables Storage engine tables that support row-level inserts, updates, and deletes. | 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. | Kudu tables is specific to Cloudera Data Platform and Users to Onelogin — each maps to any object or custom field on the other side. |
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.
DetectionStacksync polls Cloudera Data Platform for changes on an incremental schedule, reading only records changed since the previous pass. Polling via SQL on timestamp or partition columns.
DeliveryEach detected change is written to Onelogin through its API, with automatic retries and rate-limit backoff.
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 Cloudera Data Platform as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Cloudera Data Platform–Onelogin connection.
Changes in Cloudera Data Platform or Onelogin instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Cloudera Data Platform or Onelogin data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Cloudera Data Platform or Onelogin record.
Track your Cloudera Data Platform ⇄ Onelogin sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Cloudera Data Platform and Onelogin.
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.
Authenticate Cloudera Data Platform 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.
Pick the Cloudera Data Platform 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Cloudera Data Platform and Onelogin: authenticate both systems, choose the objects to sync (such as Cloudera Data Platform's Partitions and Object store / HDFS files), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Cloudera Data Platform and Onelogin records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Cloudera Data Platform and Onelogin connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Cloudera Data Platform–Onelogin integration in-house.
Yes — Stacksync ships production-grade connectors for both Cloudera Data Platform and Onelogin. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Cloudera Data Platform: Polling via SQL on timestamp or partition columns; no consumer-facing change feed. On Onelogin: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Cloudera Data Platform side: Views, Partitions, Object store / HDFS files, Databases, plus custom fields where Cloudera Data Platform exposes them. On the Onelogin side: Apps (app instances), Groups, Mappings (mapping rules), Events. Stacksync auto-detects both schemas and converts types between the two systems.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 434 integrations available for Cloudera Data Platform and Onelogin.