Skip to main content

​
What this integration contributes

OneLogin can contribute normalized user lifecycle, authentication, MFA, and administrative activity. Reviewed examples include:
  • mfa.success — completes MFA challenges
  • mfa.failed — fails MFA challenges
  • account.locked — account locked
See how integration data becomes signals.

​
What Living Security needs

​
Setup

1

Create API credentials in OneLogin

As an account owner or administrator, open Developers → API Credentials, create a dedicated credential, and select a scope that can read users and events. Store the client ID and secret securely.
Living Security exchanges the credential pair for an access token and renews it before it expires, so there is no token for you to generate or rotate. Rotate the credential pair itself on your usual schedule and reconnect the tile afterwards.

​
Verify and troubleshoot

Verify that the connection can read at least one user. Audit events may be empty when the tenant has no recent activity.
The client ID or client secret is wrong, or the credential pair was deleted in OneLogin. Confirm the pair still exists under Developers → API Credentials, then reconnect with the current values.
Recreate the API credential with permission to read OneLogin resource APIs, users, and events.
Enter only the tenant subdomain, not a full URL and not the administrative display name.If the subdomain is correct and the tenant still cannot be reached, check whether OneLogin restricts API access by source IP address in your account. This integration needs two sets of addresses allowlisted, because Living Security mints the access token itself and renews it continuously — so token requests and scheduled syncs leave from different networks.
For vendor-side details, see OneLogin’s API credential guide.