Set up a PostgreSQL connector

Capabilities
Gather PostgreSQL credentials
Configure the PostgreSQL connector

Capabilities

Resource	Sync	Provision
Accounts
Columns
Databases
Functions
Large objects
Procedures
Roles
Schemas
Sequences
Tables
Views

The PostgreSQL connector supports automatic account provisioning and deprovisioning. When a new account is created by ConductorOne, the account’s password will be sent to a vault.

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

That’s it! Next, move on to the connector configuration instructions.

Configure the PostgreSQL connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of PostgreSQL credentials generated by following the instructions above

Cloud-hosted
Self-hosted

Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.Cloud-hosted connector not currently available.

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 ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Step 1: Set up a new PostgreSQL connector

In ConductorOne, navigate to Connectors > Add connector.

Search for Baton and click Add.

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 ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app

Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

Click Next.

In the Settings area of the page, click Edit.

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 PostgreSQL connector deployment:

Secrets configuration

# baton-postgresql-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-postgresql-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne 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 ConductorOne 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

# 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

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

Check that the connector data uploaded correctly. In ConductorOne, click Applications. 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.

That’s it! Your PostgreSQL connector is now pulling access data into ConductorOne.

Set up Pipedrive connector

Set up a PrismHR connector

⌘I

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

Capabilities

Gather PostgreSQL credentials

Configure the PostgreSQL connector

Step 1: Set up a new PostgreSQL connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

​Capabilities

​Gather PostgreSQL credentials

​Configure the PostgreSQL connector

​Step 1: Set up a new PostgreSQL connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather PostgreSQL credentials

Configure the PostgreSQL connector

Step 1: Set up a new PostgreSQL connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector