Real-time
Two-way sync
Changes in CockroachDB or Onelogin instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Security and identity
CockroachDB to Onelogin integration — real-time, two-way sync
Keep CockroachDB 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 CockroachDB and Onelogin
Close the gap between your application data and your directory: CockroachDB and Onelogin share users, groups, and access in real time, in both directions.
Onelogin 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. CockroachDB 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 Changefeeds, Databases, Schemas, Tables in CockroachDB with Mappings (mapping rules), Events, Authentication factors (MFA), Custom user fields in Onelogin 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 Write application events from CockroachDB back to CRM fields to give go-to-market teams product context.
- 02 Use changefeeds to propagate row changes from a multi-region cluster into a warehouse or search index.
- 03 Two-way sync Users between OneLogin and an HRIS or Postgres so new hires, attribute changes, and terminations provision and deprovision SSO accounts automatically.
- 04 Read the OneLogin Events audit log into a warehouse or SIEM for login analytics, access reviews, and SOC 2 audit evidence.
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 CockroachDB, Stacksync creates the matching user in Onelogin 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 CockroachDB, the matching account in Onelogin is disabled within seconds, closing the window between a departure and a login that still works.
What you can sync between CockroachDB 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.
| CockroachDB objects | Onelogin objects | How this pairing syncs | |
|---|---|---|---|
| Sequences ID generators that matter when writes originate from an external system. | Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. | Sequences is specific to CockroachDB and Authentication factors (MFA) to Onelogin — each maps to any object or custom field on the other side. | |
| Changefeeds Built-in CDC streams that emit row-level changes to external sinks. | Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. | Changefeeds is specific to CockroachDB and Custom user fields to Onelogin — each maps to any object or custom field on the other side. | |
| Databases Logical containers a sync connects to, addressed like PostgreSQL databases. | 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. | Databases is specific to CockroachDB and Users to Onelogin — each maps to any object or custom field on the other side. | |
| Schemas Namespaces within a database used to isolate synced tables from application tables. | Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. | Schemas is specific to CockroachDB and Roles to Onelogin — each maps to any object or custom field on the other side. | |
| Tables The core read/write target; rows sync bi-directionally with SaaS objects or other databases. | Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. | Tables is specific to CockroachDB and Apps (app instances) to Onelogin — each maps to any object or custom field on the other side. | |
| Views Read-only projections used as curated sync sources. | 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. | Views is specific to CockroachDB and Groups to Onelogin — each maps to any object or custom field on the other side. |
How changes propagate between CockroachDB 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.
CockroachDB Onelogin Sub-second propagation
DetectionChanges in CockroachDB are captured at the source via change data capture — no polling loop against its API. CDC via changefeeds, which stream row-level changes.
DeliveryEach detected change is written to Onelogin through its API, with automatic retries and rate-limit backoff.
Onelogin CockroachDB 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 CockroachDB as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- CockroachDB: No API rate limits in the SaaS sense; throughput is bounded by cluster capacity.
- 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 CockroachDB ⇄ Onelogin
Connect CockroachDB and Onelogin for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every CockroachDB–Onelogin connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever CockroachDB 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 CockroachDB or Onelogin record.
Observability
Monitoring
Track your CockroachDB ⇄ Onelogin sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between CockroachDB and Onelogin.
How the CockroachDB and Onelogin connectors work
CockroachDB
- Integration surface
- SQL wire protocol (PostgreSQL-compatible)
- Authentication
- Database credentials with TLS; client certificates or SCRAM password auth
- Change detection
- CDC via changefeeds, which stream row-level changes; polling as a fallback
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits in the SaaS sense; throughput is bounded by cluster capacity
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 CockroachDB 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.
- 01
Connect your apps
Authenticate CockroachDB 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.
CockroachDB
connected
Onelogin
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the CockroachDB 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.
objects · CockroachDB ⇄ OneloginCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
CockroachDB OneloginCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
CockroachDB and Onelogin integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between CockroachDB and Onelogin: authenticate both systems, choose the objects to sync (such as CockroachDB's Sequences and Changefeeds), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for CockroachDB and Onelogin: One profile, kept current; Provision accounts from the source of truth; Deprovision the moment the record changes. 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.
-
CockroachDB: SQL wire protocol (PostgreSQL-compatible). Authentication: Database credentials with TLS; client certificates or SCRAM password auth. Onelogin: 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. Stacksync manages authentication, retries, and rate limits on both sides.
-
CockroachDB: Multi-region clusters let operators pin table data to specific regions while keeping a single logical database. Onelogin: The Event Webhook (Event Broadcaster) delivers batches of events to a registered URL for near-real-time triggers, while the Events API filters by since/until for historical pulls; there is no database-level CDC. Stacksync's field mapping accounts for these differences between CockroachDB and Onelogin without custom code.
-
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 CockroachDB and Onelogin records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed CockroachDB and Onelogin connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom CockroachDB–Onelogin integration in-house.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 441 integrations available for CockroachDB and Onelogin.
Popular · 8 of 441
-
CockroachDB ⇄ Jumpcloud -
CockroachDB ⇄ Active Directory - CockroachDB ⇄ Azure Active Directory
-
CockroachDB ⇄ Okta -
Onelogin ⇄ Azure Cosmos DB -
Onelogin ⇄ Azure SQL Database -
Onelogin ⇄ Citus -
Onelogin ⇄ Couchbase
No integrations match .
