Set up LaunchDarkly connector

Capabilities
Gather LaunchDarkly configuration information
Configure the LaunchDarkly connector

Capabilities

Resource	Sync	Provision
Member
Role
Team

Additional functionality: None.

Gather LaunchDarkly configuration information

Configuring the connector requires you to pass in information from LaunchDarkly. Gather these configuration details before you move on. Here’s the information you’ll need:

API Access Token

See the LaunchDarkly docs for information on how to acquire credentials: View the documentation This connector requires the following scopes:

Reader

Configure the LaunchDarkly connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of LaunchDarkly configuration information gathered by following the instructions above

Cloud-hosted
Self-hosted

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

In ConductorOne, navigate to Integrations > Connectors and click Add connector.

Search for LaunchDarkly and click Add.

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

Find the Settings area of the page and click Edit.

Enter the configuration information from the previous section.

Click Save.

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 LaunchDarkly connector is now pulling access data into ConductorOne.

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

Resources

Contact ConductorOne’s support team to download the latest version of the connector.

Step 1: Set up a new LaunchDarkly connector

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

Search for Baton and click Add.

Choose how to set up the new LaunchDarkly 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

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

Secrets configuration

# baton-launchdarkly-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-launchdarkly-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>

  # LaunchDarkly config
  BATON_LAUNCHDARKLY_API_TOKEN: <LaunchDarkly API Access Token>

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

Deployment configuration

# baton-launchdarkly.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-launchdarkly
  labels:
    app: baton-launchdarkly
spec:
  selector:
    matchLabels:
      app: baton-launchdarkly
  template:
    metadata:
      labels:
        app: baton-launchdarkly
        baton: true
        baton-app: launchdarkly
    spec:
      containers:
      - name: baton-launchdarkly
        image: ghcr.io/conductorone/baton-launchdarkly:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-launchdarkly
        envFrom:
        - secretRef:
            name: baton-launchdarkly-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 Apps. On the Managed apps tab, locate and click the name of the application you added the launchdarkly connector to. launchdarkly data should be found on the Entitlements and Accounts tabs.

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

Set up LastPass connector

Set up an LDAP connector

⌘I

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up LaunchDarkly connector

Capabilities

Gather LaunchDarkly configuration information

Configure the LaunchDarkly connector

Resources

Step 1: Set up a new LaunchDarkly connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

​Capabilities

​Gather LaunchDarkly configuration information

​Configure the LaunchDarkly connector

​Resources

​Step 1: Set up a new LaunchDarkly connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather LaunchDarkly configuration information

Configure the LaunchDarkly connector

Resources

Step 1: Set up a new LaunchDarkly connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector