Set up a Cisco Duo connector

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

Availability

This connector uses the Duo Admin API, which is available to users on the Duo Premier, Advantage, and Essentials plans.

Capabilities

Resource	Sync	Provision
Accounts
Roles
Groups

Gather Duo credentials

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

A user with the Owner role in Duo must perform this task.

1. Log into the Duo Admin Panel and navigate to Applications.

2. Click Protect an Application and locate the entry for Admin API in the applications list.

3. Click Protect.

4. In the Permissions section, grant the following permissions based on your use case:

   Required for sync (read-only):

   • Grant administrators — Read
   • Grant read information
   • Grant settings
   • Grant resource — Read

   Also required for provisioning (group membership):

   • Grant resource — Write
5. Click Save changes. Scroll to the Details section, where the integration key, secret key, and API hostname are shown, and carefully copy and save these credentials.

Done. Next, move on to the connector configuration instructions.

Configure the Duo connector

To complete this task, you’ll need:

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

Cloud-hosted

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

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

2. Search for Duo and click Add.

3. Choose how to set up the new Duo 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 C1)
   • 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 C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 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. Enter the credentials into the Integration key, Secret key, and API hostname fields.

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.

Done. Your Duo connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the Duo connector, hosted and run in your own environment.

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 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 Duo connector

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

2. Search for Baton and click Add.

3. Choose how to set up the new Duo 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 C1)
   • 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 C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 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 Duo connector deployment:

Secrets configuration

# baton-duo-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-duo-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Duo credentials
  BATON_API_HOSTNAME: <Duo API hostname>
  BATON_INTEGRATION_KEY: <Duo integration key>
  BATON_SECRET_KEY: <Duo secret key>

  # Optional: include if you want C1 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-duo.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-duo
  labels:
    app: baton-duo
spec:
  selector:
    matchLabels:
      app: baton-duo
  template:
    metadata:
      labels:
        app: baton-duo
        baton: true
        baton-app: duo
    spec:
      containers:
      - name: baton-duo
        image: public.ecr.aws/conductorone/baton-duo:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-duo
        envFrom:
        - secretRef:
            name: baton-duo-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

2. Check that the connector data uploaded correctly. In C1, click Apps. On the Managed apps tab, locate and click the name of the application you added the Duo connector to. Duo data should be found on the Entitlements and Accounts tabs.

Done. Your Duo connector is now pulling access data into C1.