> ## Documentation Index
> Fetch the complete documentation index at: https://www.c1.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

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

<Tip>
  **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.
</Tip>

## Capabilities

| Resource                | Sync                                                            | Provision                                                     |
| :---------------------- | :-------------------------------------------------------------- | :------------------------------------------------------------ |
| Accounts                | <Icon icon="square-check" iconType="solid" color="#c937ae" />   |                                                               |
| Roles                   | <Icon icon="square-check" iconType="solid" color="#c937ae" />   | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Groups                  | <Icon icon="square-check" iconType="solid" color="#c937ae" />   |                                                               |
| Application assignments | <Icon icon="square-check" iconType="solid" color="#c937ae" />   |                                                               |
| Privileges              | <Icon icon="square-check" iconType="solid" color="#c937ae" />\* |                                                               |

\*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.

<Warning>
  A user with **Administrator** or **account owner** access to your OneLogin account must perform this task.
</Warning>

### Create an API credential

<Steps>
  <Step>
    Sign into OneLogin as an **Account owner** or **Administrator**.
  </Step>

  <Step>
    Navigate to **Developers** > **API Credentials**.
  </Step>

  <Step>
    Click **New Credential**
  </Step>

  <Step>
    Give the API credential a name, such as **C1**.
  </Step>

  <Step>
    Select the **Manage all** scope.
  </Step>

  <Step>
    Click **Save**.
  </Step>

  <Step>
    When the new API credential is created, copy and save the **Client ID** and **Client Secret**.
  </Step>
</Steps>

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

## Configure the OneLogin connector

<Warning>
  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
</Warning>

<Tabs>
  <Tab title="Cloud-hosted">
    **Follow these instructions to use a built-in, no-code connector hosted by C1.**

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** and click **Add connector**.
      </Step>

      <Step>
        Search for **OneLogin v2** and click **Add**.
      </Step>

      <Step>
        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
      </Step>

      <Step>
        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.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        Find the **Settings** area of the page and click **Edit**.
      </Step>

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

      <Step>
        In the **OneLogin client ID** field, enter the client ID.
      </Step>

      <Step>
        Paste the client secret into the **OneLogin client secret** field.
      </Step>

      <Step>
        **Optional.** If desired, click to enable **Sync privileges**.
      </Step>

      <Step>
        Click **Save**.
      </Step>

      <Step>
        The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing.
      </Step>
    </Steps>

    **Done.** Your OneLogin connector is now pulling access data into C1.
  </Tab>

  <Tab title="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](https://dist.conductorone.com/ConductorOne/baton-onelogin): For stable binaries (Windows/Linux/macOS) and container images.

    * [GitHub repository](https://github.com/conductorone/baton-onelogin): Access the source code, report issues, or contribute to the project.

    ### Step 1: Set up a new OneLogin connector

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** > **Add connector**.
      </Step>

      <Step>
        Search for **Baton** and click **Add**.
      </Step>

      <Step>
        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
      </Step>

      <Step>
        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.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        In the **Settings** area of the page, click **Edit**.
      </Step>

      <Step>
        Click **Rotate** to generate a new Client ID and Secret.

        Carefully copy and save these credentials. We'll use them in Step 2.
      </Step>
    </Steps>

    ### Step 2: Create Kubernetes configuration files

    Create two Kubernetes manifest files for your OneLogin connector deployment:

    #### Secrets configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # 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

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # 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
            imagePullPolicy: IfNotPresent
            env:
            - name: BATON_HOST_ID
              value: baton-onelogin
            envFrom:
            - secretRef:
                name: baton-onelogin-secrets
    ```

    ### Step 3: Deploy the connector

    <Steps>
      <Step>
        Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
      </Step>

      <Step>
        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.
      </Step>
    </Steps>

    **Done.** Your OneLogin connector is now pulling access data into C1.
  </Tab>
</Tabs>

### 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](/product/admin/applications) page for important information about how to set up connectors for the SCIMed apps.