Skip to content
Security and identity ⇄ Database

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

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

Close the gap between your application data and your directory: OpenSearch 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. OpenSearch 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 Ingest pipelines, Data streams, Snapshots, Indexes in OpenSearch with Apps (app instances), Groups, Mappings (mapping rules), Events 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 Stream CRM records such as accounts, contacts, and tickets into OpenSearch to power internal search across customer data.
  • 02 Sync product catalogs from an ERP or database into the indexes that back storefront search.
  • 03 Read the OneLogin Events audit log into a warehouse or SIEM for login analytics, access reviews, and SOC 2 audit evidence.
  • 04 Keep Role membership aligned with application or database entitlement tables so each role's assigned users match who should hold that access.

Common sync patterns

Deprovision the moment the record changes

When someone is marked inactive or removed in OpenSearch, the matching account in Onelogin is disabled within seconds, closing the window between a departure and a login that still works.

Read users and groups as ordinary tables

Users, groups, and their memberships from Onelogin land in OpenSearch 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.

What you can sync between Onelogin and OpenSearch

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 OpenSearch objects How this pairing syncs
Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. Ingest pipelines Server-side processors that transform documents as they are written Authentication factors (MFA) is specific to Onelogin and Ingest pipelines to OpenSearch — 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. Data streams Append-oriented time-series storage for logs and events pushed from source systems Custom user fields is specific to Onelogin and Data streams to OpenSearch — each maps to any object or custom field on the other side.
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. Snapshots Backup artifacts, relevant when reseeding an index from a repository Users is specific to Onelogin and Snapshots to OpenSearch — each maps to any object or custom field on the other side.
Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. Indexes The core container; synced records land in indexes with defined mappings Roles is specific to Onelogin and Indexes to OpenSearch — each maps to any object or custom field on the other side.
Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. Documents JSON records written via the index and bulk APIs and read via search queries Apps (app instances) is specific to Onelogin and Documents to OpenSearch — 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. Index aliases Stable names over rotating indexes, used for zero-downtime reindex during backfills Groups is specific to Onelogin and Index aliases to OpenSearch — each maps to any object or custom field on the other side.

How changes propagate between Onelogin and OpenSearch

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 OpenSearch 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 written to OpenSearch through its API, with automatic retries and rate-limit backoff.

OpenSearch Onelogin Interval-based propagation

DetectionStacksync polls OpenSearch for changes on an incremental schedule, reading only records changed since the previous pass. No native change feed.

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.
  • OpenSearch: Throughput bounded by cluster sizing rather than fixed API quotas.
What ships with Onelogin ⇄ OpenSearch

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

OpenSearch

Integration surface
REST API over HTTP(S) with JSON payloads
Authentication
basic authentication with the security plugin, or AWS IAM request signing on Amazon OpenSearch Service
Change detection
no native change feed; reads rely on queries with scroll or point-in-time polling
Capabilities
read · write
Rate limits
throughput bounded by cluster sizing rather than fixed API quotas
How it works

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

    Choose tables

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

Onelogin and OpenSearch 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 422 integrations available for Onelogin and OpenSearch.

Popular · 8 of 422
All Onelogin integrations All OpenSearch 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