Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Asana credentials

Each setup method requires you to pass in credentials generated in Asana. Gather these credentials before you move on.

Generate a new personal access token

1. Log into Asana and navigate to app.asana.com/0/my-apps.

2. In the Personal access tokens area of the page, click + Create new token.

3. Give the new token a name, such as ConductorOne.

4. Click Create token.

5. The new token is generated for you. Carefully copy and save the token.

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

Set up an Asana cloud-hosted connector

This task requires either the Connector Administrator or Super Administrator role in ConductorOne.

1. In ConductorOne, click Connectors > 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.

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

Set up an Asana 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 Asana and ConductorOne.

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

Set up an Asana self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Asana 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 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
data:
  # ConductorOne credentials
  BATON_CLIENT_ID: <base64 encoded ConductorOne client ID>
  BATON_CLIENT_SECRET: <base64 encoded ConductorOne client secret>
  
  # Asana specific credentials
  BATON_TOKEN: <base64 encoded Asana personal access token>

Base64 Encoding: Use echo -n "your-value" | base64 to encode your secrets.

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
        args: ["service"]
        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):

   kubectl create namespace baton-asana
   

2. Apply the secret configuration:

   kubectl -n baton-asana apply -f baton-asana-secrets.yaml
   

3. Apply the deployment:

   kubectl -n baton-asana apply -f baton-asana.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n c1 get pods
   

2. View the connector logs:

   kubectl -n c1 logs -l app=baton-${baton-asana}
   

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 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.