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

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

2. Search for Asana and click Add.

3. Choose how to set up the new Asana 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 personal access token you generated in Step 1 into the Personal access token field.

Service account users: Check to enable the Is service account checkbox and enter your service account token in the Personal access token field.

1. Optional. If you want ConductorOne to provision new Asana accounts, enter the ID of the workspace new accounts should be added to in the Default workspace field.

   If you do not set the default workspace ID here, you can set it when configuring account provisioning. The workspace ID must be set in at least one of these places, or account provisioning will fail.

2. Click Save.

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

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

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

2. Search for Baton and click Add.

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

Secrets configuration

# baton-asana-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-asana-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Asana specific credentials
  BATON_TOKEN: <Asana personal access token or service account token>

  # Optional: Include if using a service account token
  BATON_USE_SERVICE_ACCOUNT: true

  # Optional: Include if you want ConductorOne to provision access using this connector
  BATON_PROVISIONING: true

  # Optional: The workspace where ConductorOne should add newly provisioned Asana accounts
  BATON_DEFAULT_WORKSPACE_ID: <Asana workspace ID>

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

Deployment configuration

# baton-asana.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-asana
  labels:
    app: baton-asana
spec:
  selector:
    matchLabels:
      app: baton-asana
  template:
    metadata:
      labels:
        app: baton-asana
        baton: true
        baton-app: asana
    spec:
      containers:
      - name: baton-asana
        image: ghcr.io/conductorone/baton-asana:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-asana-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 Asana connector to. Asana data should be found on the Entitlements and Accounts tabs.

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