Real-time
Two-way sync
Changes in MySQL or Onelogin instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Security and identity
MySQL to Onelogin integration — real-time, two-way sync
Keep MySQL 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 MySQL and Onelogin
Close the gap between your application data and your directory: MySQL 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. MySQL 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 Columns, Primary and Unique Keys, JSON Columns, Stored Procedures in MySQL with Users, Roles, Apps (app instances), Groups 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 Two-way sync between a MySQL application database and a CRM so operational records and sales records stay identical
- 02 Expose SaaS objects as MySQL tables so legacy internal tools built on MySQL can read live business data
- 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
Keep group and role membership aligned
A group or role change made in either system updates the other, so the entitlements an application enforces match what the directory grants.
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 MySQL, Stacksync creates the matching user in Onelogin with the right attributes, so access starts from live data instead of a manual ticket.
What you can sync between MySQL 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.
| MySQL objects | Onelogin objects | How this pairing syncs | |
|---|---|---|---|
| Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. | Databases (Schemas) is specific to MySQL and Mappings (mapping rules) to Onelogin — each maps to any object or custom field on the other side. | |
| Tables The primary sync target; rows map to records in connected systems. | Events Audit log of every authentication and admin action; read-only, filtered by since/until, and pushed live through the Event Webhook. | Tables is specific to MySQL and Events to Onelogin — each maps to any object or custom field on the other side. | |
| Views Read-side projections used as outbound sync sources. | Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. | Views is specific to MySQL and Authentication factors (MFA) to Onelogin — each maps to any object or custom field on the other side. | |
| Columns Field-level mapping targets with engine-typed values. | Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. | Columns is specific to MySQL and Custom user fields to Onelogin — each maps to any object or custom field on the other side. | |
| Primary and Unique Keys Match keys for idempotent upserts and conflict handling. | 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. | Primary and Unique Keys is specific to MySQL and Users to Onelogin — each maps to any object or custom field on the other side. | |
| JSON Columns Validated semi-structured payloads for nested SaaS data. | Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. | JSON Columns is specific to MySQL and Roles to Onelogin — each maps to any object or custom field on the other side. |
How changes propagate between MySQL 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.
MySQL Onelogin Sub-second propagation
DetectionChanges in MySQL are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when.
DeliveryEach detected change is written to Onelogin through its API, with automatic retries and rate-limit backoff.
Onelogin MySQL 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 MySQL as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- MySQL: No API rate limits; throughput is bounded by connection limits and server resources.
- 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 MySQL ⇄ Onelogin
Connect MySQL and Onelogin for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MySQL–Onelogin connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever MySQL 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 MySQL or Onelogin record.
Observability
Monitoring
Track your MySQL ⇄ Onelogin sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between MySQL and Onelogin.
How the MySQL and Onelogin connectors work
MySQL
- Integration surface
- SQL wire protocol (MySQL client/server protocol)
- Authentication
- Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host)
- Change detection
- Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled)
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by connection limits and server resources
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 MySQL 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 MySQL 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.
MySQL
connected
Onelogin
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the MySQL 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 · MySQL ⇄ 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.
MySQL OneloginCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
MySQL and Onelogin integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between MySQL and Onelogin: authenticate both systems, choose the objects to sync (such as MySQL's Databases (Schemas) and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both MySQL and Onelogin. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on MySQL: Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled). 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 MySQL side: Columns, Primary and Unique Keys, JSON Columns, Stored Procedures, plus custom fields where MySQL exposes them. On the Onelogin side: Users, Roles, Apps (app instances), Groups. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for MySQL and Onelogin: Keep group and role membership aligned; One profile, kept current; Provision accounts from the source of truth. A group or role change made in either system updates the other, so the entitlements an application enforces match what the directory grants.
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 544 integrations available for MySQL and Onelogin.
Popular · 8 of 544
-
MySQL ⇄ Azure Active Directory -
MySQL ⇄ Okta -
MySQL ⇄ Auth0 -
MySQL ⇄ Jumpcloud -
Onelogin ⇄ Jdbc -
Onelogin ⇄ Render Postgres -
Onelogin ⇄ PostgreSQL -
Onelogin ⇄ Amazon RDS
No integrations match .
