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 Jenkins 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 Jenkins connector

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

2. Search for Baton and click Add.

3. Choose how to set up the new Jenkins 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 Jenkins connector deployment:

Secrets configuration

# baton-jenkins-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-jenkins-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Jenkins credentials
  BATON_BASE_URL: <Jenkins base URL (default is http://localhost:8080)>
  BATON_USERNAME: <Username of admin used to connect to the Jenkins API>
  BATON_PASSWORD: <Admin password used to connect to the Jenkins API (omit if using a token)>

  # Optional: use instead of the admin password, if desired 
  BATON_TOKEN: <HTTP access token in Jenkins>

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

Step 3: Deploy the connector

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

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

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