Skip to main content
Connect using API client credentials. Requires OneLogin administrator access to create API credentials.

​
Prerequisites

Before you begin, ensure you have:
  • OneLogin administrator access
  • Permissions to create API credentials in the OneLogin Admin Console

​
Setup guide

​
Create API credentials in OneLogin

1

Access the OneLogin Admin Console

Log in to your OneLogin Admin Console as an administrator
2

Navigate to API credentials

Go to Developers > API Credentials
3

Create a new credential

Click New Credential and provide a descriptive name (e.g., “Ravenna Integration”)
4

Select the appropriate scope

Choose Manage All to enable both sync and workflow actions, or Read All for read-only sync.
Manage All is required if you want to use workflow actions like activating users, managing group memberships, or resetting passwords.
5

Copy your credentials

Copy the Client ID and Client Secret.
Store these credentials securely. You will not be able to view the client secret again after navigating away.
For more details, see OneLogin’s API credentials documentation

​
Add integration in Ravenna

1

Navigate to integrations

Go to Settings > Integrations
2

Select OneLogin

Find OneLogin in the available integrations and click Connect
3

Enter credentials

Provide the following information:
​
clientId
string
required
The client ID from your OneLogin API credential
​
clientSecret
string
required
The client secret from your OneLogin API credential
​
subdomain
string
required
Your OneLogin subdomain (e.g., acme for acme.onelogin.com)
​
region
string
Your OneLogin region, if outside the US
4

Complete setup

Click Add OneLogin to complete the integration. Ravenna will validate your credentials and begin syncing users, groups, roles, and applications.

​
Troubleshooting

Cause: Client ID or client secret is incorrect.Solution:
  • Verify the client ID and client secret are copied correctly
  • Ensure there are no extra spaces or characters
  • Check that the API credential still exists in OneLogin
  • Try creating a new credential if the original was regenerated
Cause: The API credential lacks the required scopes.Solution:
  • Verify the credential has at least Read All scope
  • For workflow actions, ensure Manage All scope is selected
  • Try creating a new credential with the correct scope
Cause: Incorrect OneLogin subdomain.Solution:
  • Verify the subdomain matches your OneLogin organization URL (e.g., acme for acme.onelogin.com)
  • Ensure the subdomain is active and accessible
  • Check for typos in the subdomain value
Cause: Sync may still be in progress or the credential has limited scope.Solution:
  • Allow a few minutes for the initial sync to complete
  • Verify the integration status shows as connected in Settings > Integrations
  • Check that users and groups exist in the OneLogin organization linked to your credentials