> ## 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 a PostgreSQL connector

> C1 provides identity governance and just-in-time provisioning for PostgreSQL. Integrate your PostgreSQL instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.

## Capabilities

| Resource      | Sync                                                          | Provision                                                     |
| :------------ | :------------------------------------------------------------ | :------------------------------------------------------------ |
| Accounts      | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Columns       | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |                                                               |
| Databases     | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Functions     | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |                                                               |
| Large objects | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |                                                               |
| Procedures    | <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" /> |
| Schemas       | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |                                                               |
| Sequences     | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |                                                               |
| Tables        | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |                                                               |
| Views         | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |                                                               |

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

When a new account is created by C1, the account's password will be sent to a [vault](/product/admin/vaults).

## Gather PostgreSQL credentials

Configuring the connector requires you to pass in credentials generated in PostgreSQL. Gather these credentials before you move on.

* The DSN used to connect to the PostgreSQL database

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

## Configure the PostgreSQL connector

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

  * The **Connector Administrator** or **Super Administrator** role in C1
  * Access to the set of PostgreSQL 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 PostgreSQL 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-postgresql): For stable binaries (Windows/Linux/macOS) and container images.

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

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

    #### Secrets configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-postgresql-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-postgresql-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>
      
      # PostgreSQL credentials
      BATON_DSN: <PostgreSQL DSN used to connect to the database>
      BATON_SCHEMAS: <The schemas to include in the sync (default is "public")>

      # Optional: Include if you want to sync these data-intensive resources 
      BATON_INCLUDE_COLUMNS: true
      BATON_INCLUDE_LARGE_OBJECTS: true

      # 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-postgresql.yaml
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: baton-postgresql
      labels:
        app: baton-postgresql
    spec:
      selector:
        matchLabels:
          app: baton-postgresql
      template:
        metadata:
          labels:
            app: baton-postgresql
            baton: true
            baton-app: postgresql
        spec:
          containers:
          - name: baton-postgresql
            image: ghcr.io/conductorone/baton-postgresql:latest
            imagePullPolicy: IfNotPresent
            env:
            - name: BATON_HOST_ID
              value: baton-postgresql
            envFrom:
            - secretRef:
                name: baton-postgresql-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 PostgreSQL connector to. PostgreSQL data should be found on the **Entitlements** and **Accounts** tabs.
      </Step>
    </Steps>

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