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

Available hosting methods

Choose the hosting method that best suits your needs:

Gather OneLogin credentials

Each setup method requires you to pass in credentials generated in OneLogin. Gather these credentials before you move on.

A user with Administrator or account owner access to your OneLogin account must perform this task.

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.

   

That’s it! Next, move on to the instructions for your chosen setup method.

Set up a OneLogin cloud-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of OneLogin credentials generated by following the instructions above

1. In ConductorOne, click Connectors > Add connector.

2. Search for OneLogin v2 and click Add.

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.

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

5. Click Next.

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

7. In the OneLogin domain field, enter your OneLogin domain, which is found in the URL of your OneLogin instance: <YOUR DOMAIN>.onelogin.com.

8. In the OneLogin client ID field, enter the client ID.

9. Paste the client secret into the OneLogin client secret field.

10. Click Save.

11. 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.

Set up a OneLogin cloud-hosted connector using Terraform

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

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

Set up a OneLogin self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of OneLogin credentials generated by following the instructions above

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the OneLogin connector

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

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.

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

5. Click Next.

6. In the Settings area of the page, click Edit.

7. Click Rotate to generate a new Client ID and Secret.

   Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your OneLogin connector deployment:

Secrets configuration

# baton-onelogin-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-onelogin-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # OneLogin credentials
  BATON_ONELOGIN_CLIENT_ID: <OneLogin client ID>
  BATON_ONELOGIN_CLIENT_SECRET: <OneLogin client secret>
  BATON_SUBDOMAIN: <OneLogin domain (YOUR DOMAIN.onelogin.com)>

  # Optional: include if you want ConductorOne to provision access using this connector
  BATON_PROVISIONING: true

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-onelogin.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-onelogin
  labels:
    app: baton-onelogin
spec:
  selector:
    matchLabels:
      app: baton-onelogin
  template:
    metadata:
      labels:
        app: baton-onelogin
        baton: true
        baton-app: onelogin
    spec:
      containers:
      - name: baton-onelogin
        image: ghcr.io/conductorone/baton-onelogin:latest
        args: ["service"]
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-onelogin-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace baton-onelogin
   

2. Apply the secret configuration:

   kubectl -n baton-onelogin apply -f baton-onelogin-secrets.yaml
   

3. Apply the deployment:

   kubectl -n baton-onelogin apply -f baton-onelogin.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n c1 get pods
   

2. View the connector logs:

   kubectl -n c1 logs -l app=baton-${baton-onelogin}
   

3. Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the OneLogin connector to. OneLogin data should be found on the Entitlements and Accounts tabs.

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.