Skip to content
Connection Guide

Connect OneLogin Without Breaking the Audit Trail

Use this guide to connect OneLogin or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryIdentity
Checklist4 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect OneLogin and make sure the first collection lands cleanly.

  1. 1
    Create a dedicated OneLogin API credential pair with the documented Read All scope.
  2. 2
    Store the client ID and client secret securely and configure the tenant base URL.
  3. 3
    Validate user, app, group, and event reads before enabling scheduled sync.
  4. 4
    Keep governed apply out of the credential and runtime scope.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

client_idclient_secret

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.