Set up an OneLogin connector

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

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

Capabilities

Resource	Sync	Provision
Accounts
Roles
Groups
Application assignments
System Privileges
Privileges	*

*You can opt into syncing privilege data; this is not synced by default.

Gather OneLogin credentials

Configuring the connector 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 C1.

5. Select the Manage all scope.

6. Click Save.

7. When the new API credential is created, carefully copy and save the Client ID and Client Secret.

Done. Next, move on to the connector configuration instructions.

Enable automatic user mapping sync (optional)

When C1 grants or revokes a role, OneLogin’s user mapping rules are not automatically re-evaluated. If you have mapping rules that should take effect immediately after a role change, you can enable Apply user mappings. When enabled, the connector instructs OneLogin to re-evaluate and apply all user mapping rules immediately after every role grant or revoke.

This feature requires a custom user field named c1_last_action to exist in your OneLogin account before you enable it.

Create the c1_last_action custom user field

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

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

2. Navigate to Users > Custom User Fields.

3. Click New User Field.

4. Set the Name to c1_last_action and the Shortname to c1_last_action.

5. Click Save.

Once the field exists, enable the Apply user mappings option when configuring the connector (see below).

Configure the OneLogin connector

To complete this task, you’ll need:

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

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

1. In C1, navigate to Integrations > Connectors and click 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 C1)

   • 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 C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 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. Optional. If desired, click to enable Sync privileges.

11. Click Save.

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

Done. Your OneLogin connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the OneLogin connector, hosted and run in your own environment.

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

Resources

• Official download center: For stable binaries (Windows/Linux/macOS) and container images.

• GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new OneLogin connector

1. In C1, navigate to Integrations > 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 C1)

   • 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 C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 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:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 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 C1 to provision access using this connector
  BATON_PROVISIONING: true

  # Optional: include if you want C1 to sync OneLogin privileges data 
  BATON_PRIVILEGES_ENABLED: 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: public.ecr.aws/conductorone/baton-onelogin:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-onelogin
        envFrom:
        - secretRef:
            name: baton-onelogin-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

2. Check that the connector data uploaded correctly. In C1, click Apps. 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.

Done. Your OneLogin connector is now pulling access data into C1.

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