Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Docker Hub credentials

Each setup method requires you to pass in credentials for Docker Hub. Gather these credentials before you move on.

Here’s the set of credentials you’ll need when setting up the connector:

• The username and password of a Docker Hub account

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

Set up a Docker Hub cloud-hosted connector

To complete this task, you’ll need:

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

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

2. Search for Docker Hub and click Add.

3. Choose how to set up the new Docker Hub 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. Enter the username and password for the Docker Hub account you’ll use for this integration in the Username and Password fields.

8. Click Save.

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

Set up a Docker Hub 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 Docker Hub and ConductorOne.

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

Set up a Docker Hub self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Docker Hub 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 Docker Hub connector

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

2. Search for Baton and click Add.

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

Secrets configuration

# baton-dockerhub-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-dockerhub-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Docker Hub credentials
  BATON_USERNAME: <username for the Docker Hub account>
  BATON_PASSWORD: <password to the Docker Hub account>

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

Deployment configuration

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

3. Apply the deployment:

   kubectl -n conductorone apply -f baton-dockerhub.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-dockerhub}
   

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

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