Set up an Avalara connector

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

Capabilities

Resource	Sync	Provision
Accounts
Roles

Gather Avalara credentials

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

1. The credentials for either your Avalara account, or for a service account you’ve set up in Avalara.

2. The URL of your Avalara tenant (sandbox and production environments are both accepted).

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

Configure the Avalara connector

To complete this task, you’ll need:

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

Cloud-hosted

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

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

2. Search for Avalara and click Add.

3. Choose how to set up the new Avalara 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. In the Username and Password fields, enter the credentials for either your Avalara account, or for a service account you’ve set up in Avalara.

8. In the Environment field, enter the URL of your Avalara tenant (sandbox and production environments are both accepted).

9. Click Save.

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

Self-hosted

Follow these instructions to use the Avalara 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.

Resources

• GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new Avalara connector

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

2. Search for Baton and click Add.

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

Secrets configuration

# baton-avalara-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-avalara-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Avalara credentials
  BATON_ENVIRONMENT: <URL of the Avalara environment to connect to (either production or sandbox)>
  BATON_PASSWORD: <password to the Avalara account>
  BATON_USERNAME: <username for the Avalara account>

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

Deployment configuration

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

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