Skip to content
Security and identity ⇄ Database

Onelogin to SQL Server integration — real-time, two-way sync

Keep Onelogin and SQL Server 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 SQL Server

Close the gap between your application data and your directory: SQL Server 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. SQL Server 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 Schemas, Tables, Views, Columns in SQL Server 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 Expose SaaS records as SQL Server tables that existing SSRS reports and internal apps can query
  • 02 Mirror on-premises ERP data held in SQL Server into cloud CRM and support systems
  • 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

Read users and groups as ordinary tables

Users, groups, and their memberships from Onelogin land in SQL Server as rows your application and queries can join, so authorization checks and access reporting run against the database instead of the directory API.

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.

What you can sync between Onelogin and SQL Server

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 SQL Server 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. Primary and Unique Keys Match keys for idempotent upserts and conflict handling. Apps (app instances) is specific to Onelogin and Primary and Unique Keys to SQL Server — 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. CDC Change Tables System-populated tables holding captured inserts, updates, and deletes for consumers. Groups is specific to Onelogin and CDC Change Tables to SQL Server — 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. Stored Procedures T-SQL logic that can validate or post-process synced rows. Mappings (mapping rules) is specific to Onelogin and Stored Procedures to SQL Server — 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. Databases Instance-level databases that scope a sync's reads and writes. Events is specific to Onelogin and Databases to SQL Server — 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. Schemas Namespaces (dbo and custom) used to organize synced tables. Authentication factors (MFA) is specific to Onelogin and Schemas to SQL Server — 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. Tables The primary sync target; rows map to records in connected systems. Custom user fields is specific to Onelogin and Tables to SQL Server — each maps to any object or custom field on the other side.

How changes propagate between Onelogin and SQL Server

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

SQL Server Onelogin Sub-second propagation

DetectionChanges in SQL Server are captured at the source via change data capture — no polling loop against its API. SQL Server Native Change Data Capture (CDC).

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.
  • SQL Server: No API rate limits; throughput depends on instance resources, licensing tier, and connection limits.
What ships with Onelogin ⇄ SQL Server

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

SQL Server

Integration surface
SQL over the TDS wire protocol (Tabular Data Stream), via ODBC/JDBC/ADO.NET drivers
Authentication
Database credentials entered as a connection string or as parameters (host/user/password) in the Create New Sync page
Change detection
SQL Server Native Change Data Capture (CDC); a DBA runs a one-time setup script with sysadmin privileges to enable CDC and create Stacksync wrapper procedures
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput depends on instance resources, licensing tier, and connection limits
SQL Server setup guide
How it works

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

    Choose tables

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

Onelogin and SQL Server 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 537 integrations available for Onelogin and SQL Server.

Popular · 8 of 537
All Onelogin integrations All SQL Server 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