Set up an ArgoCD connector

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

Capabilities

Resource	Sync	Provision
Accounts	✅	✅
Roles	✅	✅

The ArgoCD connector supports automatic account provisioning.

Gather ArgoCD credentials

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

The username and password for your ArgoCD admin account, or for a dedicated service account you’ve set up.
Make sure the account used to configure the connector has the relevant permissions:
- To sync (read) users and roles: get and list permissions for users and roles
- To provision (read-write) users and roles: get and list permissions for users and roles, plus create permission for users and update permission for user role assignments. The built-in admin role has these permissions, or you can create a custom role.
Your ArgoCD API URL, which is the URL you use to access the ArgoCD UI.

That’s it! Next, move on to the connector configuration instructions.

Configure the ArgoCD connector

To complete this task, you’ll need:
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of ArgoCD credentials generated by following the instructions above

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

Ths connector does not support cloud hosting.

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

In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new ArgoCD 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.
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 ArgoCD connector deployment:

Secrets configuration

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

  # Asana specific credentials
  BATON_USERNAME: <ArgoCD account username>
  BATON_PASSWORD: <ArgoCD account password>
  BATON_API_URL: <ArgoCD tenant API URL>

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

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