ConductorOne Docs

OneLogin integration

ConductorOne provides identity governance and just-in-time provisioning for OneLogin. Integrate your OneLogin instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access.


OneLogin is a popular cloud directory and SSO solution for enterprises. OneLogin stores identity, role, and application information for your organization. ConductorOne connects with your OneLogin instance to sync identities and entitlements.


โœ… General availability. The OneLogin integration is available to all ConductorOne users.


  • Sync user identities from OneLogin to ConductorOne
  • Resources supported:
    • OneLogin Roles
    • OneLogin Application Assignments

Set up the OneLogin integration

A user with the Super Administrator role in ConductorOne must perform this task.

  1. In ConductorOne, open Admin and click Integrations > OneLogin.

  2. If this is your first OneLogin integration, the integration form opens automatically. Otherwise, click Add connector.

  3. Choose whether to add the new OneLogin connector to an existing application (and select the app of your choice) or to create a new application.

  4. Set the integration owner for this connector. You can manage the integration yourself, or choose someone else from the list of ConductorOne users. Setting multiple integration owners is allowed.

    A OneLogin integration owner must have the following permissions:

    • Integration Administrator or Super Administrator role in ConductorOne
    • Administrator or account owner access to your OneLogin account
  1. Click Create and add details.

Next steps

  • If you are the integration owner, proceed to Integrate your OneLogin instance for instructions on integrating OneLogin with ConductorOne.

  • If someone else is the integration owner, ConductorOne will notify them by email that their help is needed to complete the integration.

Integrate your OneLogin instance

A user with the Integration Administrator or Super Administrator role in ConductorOne and Administrator or account owner access to your OneLogin account must perform this task.

Step 1: Locate your OneLogin domain

  1. Look up your OneLogin domain, which is found in the URL of your OneLogin instance: <YOUR DOMAIN>

  2. Make a note of your domain. We’ll use it in Step 3.

Step 2: Create an API credential

  1. Sign into OneLogin as an Account owner or Administrator.

  2. Navigate to Developers > API Credentials.

  3. Click New Credential

  4. Give the API credential a name, such as ConductorOne.

  5. Select the Manage all scope.

  6. Click Save.

  7. When the new API credential is created, copy and save the Client ID and Client Secret. We’ll use these in Step 3.

Step 3: Add your OneLogin credentials to ConductorOne

  1. In ConductorOne, open Admin and click Integrations > OneLogin.

  2. In the list of connectors, locate and click on the name of the connector with the Not connected label.

  3. Find the Settings area of the page and click Edit.

  4. In the OneLogin domain field, enter the domain you looked up in Step 1.

  5. In the OneLogin client ID field, enter the client ID from Step 2.

  6. Paste the client secret from Step 2 into the OneLogin client secret field.

  7. Click Save.

  8. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your OneLogin instance is now integrated with ConductorOne.

What’s next?

If OneLogin is your company’s identity provider (meaning that it is used to SSO into other software), the integration sync will automatically create applications in ConductorOne for all of your SCIMed software. Before you move on, review the Create applications page for important information about how to set up integrations with the SCIMed apps.

Configure the OneLogin integration using Terraform

As an alternative to the integration process described above, you can use Terraform to configure the integration between OneLogin and ConductorOne.

See the ConductorOne OneLogin integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.