Set up an Asana connector

Capabilities

Resource	Sync	Provision
Accounts
Teams
Workspaces
Licenses*

The Asana connector supports automatic account provisioning. New users are created with a view-only license. This connector does not support account deprovisioning. You must deprovision accounts directly in Asana. *License syncing and provisioning is only available for Asana Enterprise accounts. You must use a service account token to set up the connector in order to sync and provision licenses. When provisioning licenses, the connector supports the following actions:

Grant an enterprise license to a user with a view-only license
Revoke an enterprise license (automatically grants a view-only license instead)
Revoke a view-only license (deprovisions the user’s access to Asana)

Gather Asana credentials

Configuring the connector requires you to pass in credentials generated in Asana. Gather these credentials before you move on. You can configure the Asana connector using either a personal access token or a service account token.

Option 1: Generate a personal access token

This option does not support syncing and provisioning licenses.

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

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

Give the new token a name, such as ConductorOne.

Click Create token.

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

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

Option 2: Generate a service account token

ImportantAn Asana super admin using an Asana Enterprise plan must complete this task.

If you haven’t already done so, create or identify a service account in Asana that will be used for the ConductorOne integration.The service account needs, at minimum, the Users: Read and Teams: Read permissions in order to sync user data. To provision accounts and other access with ConductorOne, give the service account full permissions.

Click the three-dots icon next to the name of your service account and select Edit service account.

Click Reset and generate new token.

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

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

Configure the Asana 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

Cloud-hosted
Self-hosted

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

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

Search for Asana and click Add.

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

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.

Find the Settings area of the page and click Edit.

Paste the personal access token you generated in Step 1 into the Personal access token field.Service account users: Click to enable Is service account and enter your service account token in the Personal access token field.

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.

Optional. If want to use ConductorOne to sync and provision Asana licenses, click to enable Use SCIM API.

Click Save.

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

In ConductorOne, navigate to Connectors > Add connector.

Search for Baton and click Add.

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

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

  # Optional: Include to use the Asana SCIM API for enterprise license management
  BATON_USE_SCIM_API: true

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
        env:
        - name: BATON_HOST_ID
          value: baton-asana
        envFrom:
        - secretRef:
            name: baton-asana-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 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.

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

Set up an Asana connector

Capabilities

Gather Asana credentials

Option 1: Generate a personal access token

Option 2: Generate a service account token

Configure the Asana connector

Step 1: Set up a new Asana connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

​Capabilities

​Gather Asana credentials

​Option 1: Generate a personal access token

​Option 2: Generate a service account token

​Configure the Asana connector

​Step 1: Set up a new Asana connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Asana credentials

Option 1: Generate a personal access token

Option 2: Generate a service account token

Configure the Asana connector

Step 1: Set up a new Asana connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector