Skip to main content

​
Part 1: Duo Data Ingestion

Set up a Duo Admin API application so ConfigView can pull your Duo data into the dashboard.

​
Step 1: Create the Admin API Application

  1. In the Duo Admin Panel, navigate to Applications > Application Catalog.
  2. In the search box, type admin and find Admin API in the list.
  3. Click Add next to it.
  4. On the application page, under Details, document the Integration key, the Secret key, and the API hostname (e.g. api-XXXXXXXX.duosecurity.com).
Note: The secret key is only fully visible when the application is first created. If you lose it, use Reset Secret Key on the same page and update the value in ConfigView.

​
Step 2: Set the Application Permissions

On the same page, under Settings & Permissions, enable the permissions below, then click Save Changes. ConfigView only reads from Duo — no write permission is required.
Note: Grant applications and Grant settings are single checkboxes in Duo that permit both read and write — Duo does not offer read-only variants. Grant settings is required for duo_settings, so enable it. Leave Grant applications off: duo_integrations collects your protected applications without it, and enabling it does not unlock duo_policies or duo_billing_edition — those are gated by your Duo edition, not by this permission.
Note: Your Admin API application does not appear in its own duo_integrations results. Duo hides an Admin API app from the application list it serves, and /admin/v1/integrations/<its own key> returns 403. If you protect three applications, expect three rows, not four.

​
Empty tables are usually your Duo edition, not a mistake

Several Duo features are gated by edition (Essentials vs. Advantage vs. Premier) or are simply not configured on your account. Their collectors run, get refused, and leave the table empty — that is expected, and Duo is inconsistent about how it refuses: Before treating a 403 as a permission problem, confirm the grant is actually ticked in Duo. If it is, the feature is not in your Duo edition.

​
Step 3: Restrict API Access by Network (Optional)

If you use Networks for API Access on the application page, add the public IP address of your ConfigView server to the allowlist. Leaving the field blank allows API access from any network.

​
Step 4: Add the Secrets to ConfigView

  1. Go to your ConfigView dashboard: https://{companyname}.configview.com/admin/integrations/duo
  2. Under Credentials, enter each value and click the save icon on its row:
    • DUO_IKEY: The Integration key
    • DUO_SKEY: The Secret key
    • DUO_API_HOST: The API hostname (e.g. api-XXXXXXXX.duosecurity.com)

​
Step 5: Enable the Duo App in ConfigView

  1. Go to: https://{companyname}.configview.com/admin/integrations/duo
  2. Click Connect. ConfigView creates its tables and schedules every collector at your default run time.
  3. Click Verify now to confirm the credentials work.

​
Step 6: Verify

  1. Go to: https://{companyname}.configview.com/admin/status/
  2. Run the Duo health check.
  3. All checks should pass.
If a check fails, verify that your secrets are saved correctly and the app has the required permissions. A 403 from Duo means a missing permission; a 40103 signature error means the integration key, secret key, or API hostname is wrong.

​
Data Tables

Once the scripts run, the corresponding Duo tables will be created in your database. All tables include a run_at column for historical tracking.