This guide explains how to enable your Duo users to authenticate on Cmd-enabled servers.
Your users' Cmd accounts must use email addresses that are associated with their Duo accounts (as aliases). They must also link a phone with their Duo accounts, and install the Duo mobile application.
Before a Duo integration can be added to a project, a global admin must enable Duo integrations. After that, a manager or admin can follow the steps in this guide to integrate Duo with a Cmd project.
- Step one: Configure Duo
- Step two: Configure Cmd
- Step three: Enable Duo for 2FA
- Step four: Create a trigger for testing
Step one: Configure Duo
- Log into the Duo portal.
- Select Applications from the left-hand menu.
- Click Protect an Application in the top-right corner.
- Search for the integration called 'Auth API' and click Protect this application.
5. Next, take note of the information shown in the 'Details' section. You'll need it to
complete the integration in the Cmd web app.
6. Go to the bottom and click Save.
Step two: Configure Cmd
- Log into the Cmd web app.
- Confirm that you are adding the integration to the correct project by reviewing the name of the current project in the top-right corner of the page. Click it to open the drop-down list.
Note: Need to switch projects? Click the name of the current project, then select a different project from the drop-down list.
- Select Project & app settings from the drop-down list.
- Select Integration preferences from the left-hand menu.
- Select Duo Security:
6. Add the API URL, integration key, and secret key from Duo:
7. Click Save.
Step three: Enable Duo for 2FA
Once your Duo integration is configured, you can enable duo as a 2FA option for your Cmd project.
- Click your project name in the top right to open the drop down menu.
- Click Project and app settings.
- Select Agent from the menu on the left.
- Scroll down to the '2-factor authentication options' section.
- Check the box next to where it says 'Duo'.
Step four: Create a trigger for testing
For instructions on adding a trigger which will prompt your users for 2FA, see Adding new triggers.
To learn more about third-party integrations, including other SSO providers, see:
Our integrations overview