> ## Documentation Index
> Fetch the complete documentation index at: https://conductorone-docs-baton-kubernetes.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up a OneLogin connector

> Integrate your OneLogin instance with C1 to run user access reviews, enable just-in-time access requests, and easily provision and deprovision access.

<Tip>
  **A newer version of this connector is available.** This version of the connector is no longer available for installation. If you're setting up a OneLogin connector with C1 for the first time, use the [v2 version](/baton/onelogin).
</Tip>

## Capabilities

* Sync user identities from OneLogin to C1

* Resources supported:
  * Roles
  * Application assignments

* Provisioning supported:
  * Role assignment

## Add a new OneLogin connector

<Warning>
  This task requires either the **Connector Administrator** or **Super Administrator** role in C1.
</Warning>

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

  <Step>
    Search for **OneLogin** 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.

    <Warning>
      A OneLogin connector owner must have the following permissions:

      * **Connector Administrator** or **Super Administrator** role in C1
      * **Administrator** or **account owner** access to your OneLogin account
    </Warning>
  </Step>

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

### Next steps

* **If you are the connector owner**, proceed to [Configure your OneLogin connector](/baton/v1/onelogin#configure-your-onelogin-connector) for instructions on integrating OneLogin with C1.

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

## Configure your OneLogin connector

<Warning>
  A user with the **Connector Administrator** or **Super Administrator** role in C1 and **Administrator** or **account owner** access to your OneLogin account must perform this task.
</Warning>

### Step 1: Locate your OneLogin domain

<Steps>
  <Step>
    Look up your OneLogin domain, which is found in the URL of your OneLogin instance: `<YOUR DOMAIN>.onelogin.com`.
  </Step>

  <Step>
    Make a note of your domain. We'll use it in Step 3.
  </Step>
</Steps>

### Step 2: 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**. We'll use these in Step 3.
  </Step>
</Steps>

### Step 3: Add your OneLogin credentials to C1

<Steps>
  <Step>
    In C1, navigate to the OneLogin connector by either:

    * Clicking the **Set up connector** link in the email you received about configuring the connector.
    * Navigate to **Integrations** > **Connectors** > **OneLogin** (if there is more than one **OneLogin** listed, click the one with your name listed as owner and the status **Not connected**).
  </Step>

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

  <Step>
    In the **OneLogin domain** field, enter the domain you looked up in Step 1.
  </Step>

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

  <Step>
    Paste the client secret from Step 2 into the **OneLogin client secret** field.
  </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.

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