This is an updated and improved version of the OneLogin connector! If you’re setting up OneLogin with ConductorOne for the first time, you’re in the right place.

Capabilities

• Sync user identities from OneLogin to ConductorOne

• Resources supported:

  • Roles
  • Groups
  • Application assignments

• Provisioning supported:

  • Roles

Add a new OneLogin connector

This task requires either the Connector Administrator or Super Administrator role in ConductorOne.

1. In ConductorOne, click Connectors > Add connector.

2. Search for OneLogin v2 and click Add.

   Don’t see the OneLogin v2 connector? Reach out to support@conductorone.com to add OneLogin v2 to your Connectors page.

3. Choose how to set up the new OneLogin connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

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

   A OneLogin connector owner must have the following permissions:

   • Connector Administrator or Super Administrator role in ConductorOne
   • Administrator or account owner access to your OneLogin account

5. Click Next.

Next steps

• If you are the connector owner, proceed to Configure your OneLogin connector for instructions on integrating OneLogin with ConductorOne.

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

Configure your OneLogin connector

A user with the Connector 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>.onelogin.com.

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, navigate to the OneLogin connector by either:

   • Clicking the Set up connector link in the email you received about configuring the connector.

   • Navigate to Connectors > OneLogin v2 (if there is more than one OneLogin v2 listed, click the one with your name listed as owner and the status Not connected).

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

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

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

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

6. Click Save.

7. 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 connector is now pulling access data into ConductorOne.

What’s next?

If OneLogin is your company’s identity provider (meaning that it is used to SSO into other software), the connector 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 connectors for 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.