Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Elastic credentials

Each setup method requires you to pass in credentials generated in Elastic. Gather these credentials before you move on.

A user with the Organization owner role in Elastic must perform this task.

Generate an Elastic Cloud API key

1. In the Elasticsearch Service Console, click your avatar in the upper right corner and select Organization.

2. Navigate to the API keys tab and click Create API key.

3. Give the new API key a name, such as “ConductorOne integration”.

4. Select an expiration for the API key.

5. In the Assign roles area, give the API key the Organization owner role.

6. Click Create API key.

7. Carefully and copy and save the new API key.

(Optional) Generate an Elastic deployment API key and look up the deployment’s endpoint

The credentials generated in this step are required for ConductorOne to sync information on Elastic deployment users and deployment roles, and to provision Elastic deployment role assignments. If you do not want to sync or provision deployment users or deployment roles, skip this section.

1. Back on the Elasticsearch Service Console homepage, find the Hosted deployments area of the page and click the name of the deployment you want to integrate.

2. On the deployment’s page, click Manage permissions.

3. In the sidebar, click API keys > Create API key.

4. Give the new API key a name, such as “ConductorOne deployment info integration”.

5. Select the Personal API key option.

6. Click Create API key.

7. Carefully and copy and save the new API key.

8. We also need to look up the deployment’s Elasticsearch endpoint. Click the Elastic logo to return to your deployment’s home page.

9. Click Add integrations.

10. In the upper right corner of the screen, click Connection details.

11. Carefully copy and save the Elasticsearch endpoint.

That’s it! Next, move on to the instructions for your chosen setup method.

Set up an Elastic cloud-hosted connector

To complete this task, you’ll need:

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

1. In ConductorOne, click Connectors > Add connector.

2. Search for Elastic and click Add.

3. Choose how to set up the new Elastic 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

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

5. Click Next.

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

7. Paste the API key into the API key field.

8. Optional. If you want to sync information on Elastic deployment users and deployment roles, paste the Deployment API key and Deployment endpoint into their respective fields.

9. Optional. By default, ConductorOne will sync information about all users in all organizations. If you want to limit the sync to a single organization, paste that organization’s ID into the Organization ID field.

10. Click Save.

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

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

Set up an Elastic cloud-hosted connector using Terraform

As an alternative to the cloud-hosted integration process described above, you can use Terraform to configure the integration between Elastic and ConductorOne.

See the ConductorOne Elastic integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.

Set up an Elastic self-hosted connector

To complete this task, you’ll need:

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

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.

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the Elastic connector

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new Elastic 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

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

5. Click Next.

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

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

Secrets configuration

# baton-elastic-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-elastic-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Elastic credentials
  BATON_API_KEY: <Elastic API key>
  BATON_DEPLOYMENT_API_KEY: <Elasticsearch deployment API key>
  BATON_DEPLOYMENT_ENDPOINT: <Elasticsearch deployment endpoint>

  # 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-elastic.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-elastic
  labels:
    app: baton-elastic
spec:
  selector:
    matchLabels:
      app: baton-elastic
  template:
    metadata:
      labels:
        app: baton-elastic
        baton: true
        baton-app: elastic
    spec:
      containers:
      - name: baton-elastic
        image: ghcr.io/conductorone/baton-elastic:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-elastic-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace conductorone
   

2. Apply the secret configuration:

   kubectl -n conductorone apply -f baton-elastic-secrets.yaml
   

3. Apply the deployment:

   kubectl -n conductorone apply -f baton-elastic.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n conductorone get pods
   

2. View the connector logs:

   kubectl -n conductorone logs -l app=baton-${baton-elastic}
   

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

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