> ## 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 LDAP connector

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

## Capabilities

| Resource                              | Sync                                                          | Provision                                                     |
| :------------------------------------ | :------------------------------------------------------------ | :------------------------------------------------------------ |
| Accounts                              | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Roles (`organizationalRole` in LDAP)  | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Groups (`groupOfUniqueNames` in LDAP) | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |

The LDAP connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning).

### POSIX account provisioning

The LDAP connector supports provisioning `posixAccount` entries with automatic UID number assignment. When creating a new POSIX account, the connector can look up the highest `uidNumber` currently in use across all existing `posixAccount` entries in your directory and automatically assign the next available value.

To use this feature, configure the following account provisioning mappings:

| Mapping field                           | Destination value         | Description                                      | Example CEL expression                                                                |
| :-------------------------------------- | :------------------------ | :----------------------------------------------- | :------------------------------------------------------------------------------------ |
| **RDN Key**                             | `rdnKey`                  | The RDN attribute for the new entry              | `"uid"`                                                                               |
| **RDN Value**                           | `rdnValue`                | The value for the RDN attribute                  | `subject.profile.login`                                                               |
| **Path**                                | `path`                    | The DN path where the account will be created    | `"ou=users,o=Example Org"`                                                            |
| **Suffix**                              | `suffix`                  | The top-level entry DN (naming context)          | `"dc=example,dc=com"`                                                                 |
| **Object Class(es)**                    | `objectClass`             | Must include `posixAccount`                      | `["top", "person", "organizationalPerson", "posixAccount"]`                           |
| **Calculate the next valid UID Number** | `calculatePosixUIDNumber` | Set to `true` to enable automatic UID assignment | `true`                                                                                |
| **Additional Attributes**               | `additionalAttributes`    | Other required POSIX attributes                  | `{"cn": "Jane Doe", "sn": "Doe", "homeDirectory": "/home/jdoe", "gidNumber": "5000"}` |

<Note>
  Automatic UID number calculation assigns `uidNumber` only. You must provide `gidNumber` manually in the **Additional Attributes** mapping. If you set **Calculate the next valid UID Number** to `true`, any `uidNumber` value provided in **Additional Attributes** is ignored.
</Note>

## Gather LDAP credentials

Configuring the connector requires you to pass in credentials for LDAP. Gather these credentials before you move on.

Here's the set of credentials you'll need when setting up the connector:

* The username and password of an LDAP account
* URL of the LDAP server, which can use either `ldap:` or `ldaps:` schemes, and optionally includes a port number

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

## Configure the LDAP connector

<Warning>
  To complete this task, you'll need:

  * The **Connector Administrator** or **Super Administrator** role in C1
  * Access to the set of LDAP 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.**

    *Cloud-hosted connector not currently available.*
  </Tab>

  <Tab title="Self-hosted">
    **Follow these instructions to use the LDAP 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-ldap): For stable binaries (Windows/Linux/macOS) and container images.

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

    ### Step 1: Set up a new LDAP 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 LDAP 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 LDAP connector deployment:

    #### Secrets configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-ldap-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-ldap-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>
      
      # LDAP credentials
      BATON_BIND_DN: <Username to bind to the LDAP server with>
      BATON_PASSWORD: <Password to bind to the LDAP server with>
      BATON_URL: <URL to the LDAP server, optionally including port number>

      # Optional: include if you want C1 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

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-ldap.yaml
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: baton-ldap
      labels:
        app: baton-ldap
    spec:
      selector:
        matchLabels:
          app: baton-ldap
      template:
        metadata:
          labels:
            app: baton-ldap
            baton: true
            baton-app: ldap
        spec:
          containers:
          - name: baton-ldap
            image: ghcr.io/conductorone/baton-ldap:latest
            imagePullPolicy: IfNotPresent
            env:
            - name: BATON_HOST_ID
              value: baton-ldap
            envFrom:
            - secretRef:
                name: baton-ldap-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 LDAP connector to. LDAP data should be found on the **Entitlements** and **Accounts** tabs.
      </Step>
    </Steps>

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