Skip to main content


Visualize OneLogin users, groups, roles, devices, apps, and services, map OneLogin users to employees, and monitor changes through alerts and queries.



For this integration, you will need to create an API Client ID and Client Secret on OneLogin with the Read All scope as an administrator. See their documentation for more information.

Configuration in JupiterOne

To install the OneLogin integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select OneLogin. Click New Instance to begin configuring your integration.

Creating a configuration requires the following:

  • The Account Name used to identify the OneLogin account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

  • Description to assist in identifying the integration instance, if desired.

  • Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.

  • Your OneLogin API Client ID, API Client Secret, and your Organization Domain (format: <yourdomain>

Click Create once all values are provided to finalize the integration.


This integration's authentication is achieved by fetching an OAuth token from OneLogin. You can reproduce this authentication strategy by running the following curl, replacing <CLIENT_ID> and <CLIENT_SECRET> with your own. <API_HOSTNAME> defaults to

curl --request POST \
--url <API_HOSTNAME> \
--header 'authorization: client_id:<CLIENT_ID>, client_secret:<CLIENT_SECRET>' \
--header 'content-type: application/json' \
--data '{

Next steps

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.