Set up an OpenSearch connector

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

This connector is in beta. This means it’s undergoing ongoing testing and development while we gather feedback, validate functionality, and improve stability. Beta connectors are generally stable, but they may have limited feature support, incomplete error handling, or occasional issues.

We recommend closely monitoring workflows that use this connector and contacting our Support team with any issues or feedback.

Capabilities

Resource	Sync	Provision
Accounts
Groups
Roles

This connector pulls account and group information from another connector. You’ll configure this relationship when setting up the connector.

Gather OpenSearch credentials

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

A user with the Owner or Admin role (or a custom user role with the Edit Configuration user right) in OpenSearch must perform this task.

To set up the connector, you’ll need:

• Your OpenSearch server address

  Use your OpenSearch cluster endpoint (for example, https://your-opensearch-cluster.com:9200). For cloud deployments, use the provided endpoint from your OpenSearch service provider.

• An OpenSearch username and password

  The Opensearch account used to configure the connector must have OpenSearch cluster administrator access and access to the OpenSearch Dashboards or API for user management.

If your OpenSearch cluster uses a custom certificate, you’ll also need:

• A (PEM-encoded) CA certificate or the path to a CA certificate

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

Configure the OpenSearch connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of OpenSearch credentials generated by following the instructions above

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for OpenSearch and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

7. Find the Settings area of the page and click Edit.

8. In the Address field, enter your OpenSearch cluster endpoint (for example, https://your-opensearch-cluster.com:9200) or the endpoint provided by your OpenSearch service provider (if yours is a cloud deployment).

9. Enter the OpenSearch account username and password into the next two fields.

10. In the User match key field, enter the value (such as name or id) that will tell the connector which piece of data to use to match OpenSearch accounts with the accounts synced from the shared identity source. The default value is email.

11. Optional. If configuring this connector for use with a development or testing environment, click to enable Insecure Skip Verify. Do not use this option for production environments.

    If this option is not selected, you must include a CA certificate. If insecure verification skip is enabled, you do not need to provide a certificate.

12. If needed (see above), upload a CA certificate. The certificate must be PEM-encoded.

    CA certificates are used for production TLS verification.

13. Click Save.

14. In the Shared identity source area of the page, click Edit.

15. Select the connector from which you want to pull identities.

16. Optional. Limit the identities pulled from the connector you selected to only those with a certain entitlement by setting the entitlement.

17. Click Save.

18. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your OpenSearch connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the OpenSearch 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

• GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new OpenSearch connector

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for Baton and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

7. In the Settings area of the page, click Edit.

8. 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 OpenSearch connector deployment:

Secrets configuration

# baton-opensearch-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-opensearch-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # OpenSearch credentials
  BATON_OPENSEARCH_ADDRESS: <Your OpenSearch server address>
  BATON_OPENSEARCH_USERNAME: <Username for an OpenSearch account with security API access>
  BATON_OPENSEARCH_PASSWORD: <Password for the OpenSearch account>
  BATON_OPENSEARCH_USER_MATCH_KEY: <Field name for matching users, such as `email`, `name`, or `id` (defaults to `email`)>

  # Optional: include these credentials to perform TLS certification validation
  BATON_OPENSEARCH_INSECURE_SKIP_VERIFY: true
  BATON_OPENSEARCH_CA_CERT_PATH: <Path to PEM-encoded certificate file>

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-opensearch.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-opensearch
  labels:
    app: baton-opensearch
spec:
  selector:
    matchLabels:
      app: baton-opensearch
  template:
    metadata:
      labels:
        app: baton-opensearch
        baton: true
        baton-app: opensearch
    spec:
      containers:
      - name: baton-opensearch
        image: public.ecr.aws/conductorone/baton-opensearch:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-opensearch
        envFrom:
        - secretRef:
            name: baton-opensearch-secrets

Step 3: Deploy the connector

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

2. 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 OpenSearch connector to. OpenSearch data should be found on the Entitlements and Accounts tabs.

Done. Your OpenSearch connector is now pulling access data into C1.