
Duo Security SSO can be implemented in a matter of minutes using the Duo Admin Panel. This user-friendly interface allows administrators to easily configure and manage SSO settings.
To get started, you'll need to select the SSO method that best fits your organization's needs. Duo offers several options, including SAML 2.0, OAuth, and WS-Fed.
Once you've chosen your SSO method, you'll need to configure the necessary settings, such as the identity provider and the service provider. Duo provides clear instructions and examples to help you through this process.
The Duo Admin Panel also allows you to test your SSO configuration to ensure it's working correctly. This feature is especially useful for troubleshooting any issues that may arise.
See what others are reading: Wp Admin Url
Prerequisites
To get started with Duo Security SSO, you'll need to meet some prerequisites. You'll need a Duo Admin with the Owner role to enable the feature. This is a crucial step, as it will allow you to configure and manage your Duo SSO setup.
You'll also need an active authentication source, such as Active Directory or a SAML identity provider. If you're using Active Directory, you'll need a SAML 2.0 service provider or OIDC relying party web application to protect with Duo Single Sign-on.
Here are the specific requirements for each authentication source:
In addition to these requirements, you'll need to ensure that your remote access VPN configuration is fully functional and that your Secure Firewall Management Center and Threat Defense devices are up to date. This will help ensure a smooth and secure SSO experience for your users.
Enable SSO
To enable SSO, you'll need to log in to the Duo Admin Panel and navigate to Applications → SSO Settings. This is where you'll review the information on the "Single Sign-On" page and agree to the terms by clicking Get Started.
You can specify a subdomain you'd like your users to see when logging in with Duo Single Sign-On, such as acme, which would display acme.login.duosecurity.com in the URL. Trial accounts are restricted from creating a subdomain, however.
A different take: Logout Sign in Google Accounts
Next, you'll choose between using Active Directory or a SAML Identity Provider as your authentication source. Click the button at the bottom of the option you'd like to use to add that source type, and follow the instructions in the next section.
Here are the general steps for enabling SSO:
- Log in to the Duo Admin Panel and navigate to Applications → SSO Settings.
- Review the information on the "Single Sign-On" page and agree to the terms.
- Choose between using Active Directory or a SAML Identity Provider as your authentication source.
- Follow the instructions in the next section to complete the setup.
If you're configuring your first Active Directory, you'll be prompted to review and accept a privacy statement. This statement won't be shown again for additional Active Directory authentication sources or for SAML sources.
Setup and Configuration
To set up Duo Security SSO, you'll first need to install the Duo Authentication Proxy on a Windows or Linux server. This is a crucial step to connect Duo Single Sign-On and Active Directory together.
You'll need to install Duo Authentication Proxy 5.5.1 or higher on the server, and confirm that it can communicate with your Active Directory domain controllers over LDAP/LDAPS.
To connect the Authentication Proxy to Duo Single Sign-On, you'll need to add the proxy to the Duo Admin Panel, and then generate and copy a command to run on the proxy server. This will connect the proxy to Duo Single Sign-On.
Related reading: Dns Server Recursive Query Cache Poisoning Weakness
Here are the specific steps to connect the Authentication Proxy to Duo Single Sign-On:
- On the "Active Directory Configuration" page, click Add Authentication Proxy.
- Locate and open the authproxy.cfg file on the Authentication Proxy server with elevated permissions.
- Copy the service account credentials from the Duo Admin Panel and append them to the authproxy.cfg file.
- Save and close the authproxy.cfg file, and then follow the instructions in the Admin Panel to generate and copy the command to run on the proxy server.
- Click Run test to confirm the Authentication Proxy is connected to Duo.
Remember, you can add additional Authentication Proxy servers by repeating these steps.
Install Proxy
To install a Duo Authentication Proxy, you'll need a Windows or Linux server. Install Duo Authentication Proxy 5.5.1 or higher on the server, following the installation instructions provided.
For high availability, it's recommended to have three Authentication Proxy servers. Each server must be able to connect to every domain controller you plan to use for authentication.
To confirm that your Authentication Proxy can communicate with your Active Directory domain controllers, check that it can connect over LDAP/LDAPS (commonly ports 389/636). Also, ensure that your Authentication Proxy has outbound internet access over port 443.
Here are the steps to confirm these settings:
- Confirm that your Authentication Proxy can communicate with your Active Directory domain controllers over LDAP/LDAPS (commonly ports 389/636).
- Confirm that your Authentication Proxy has outbound internet access over port 443.
You can install the Duo Authentication Proxy on a Windows or Linux server, following the installation instructions. For high availability, you'll need three servers, each able to connect to every domain controller.
Google Workspace App

To configure Google Workspace app for Duo Single Sign-On, you'll need to follow these steps.
First, on the Duo Admin Panel, scroll up to 1. Configure your SAML Identity Provider to get the Duo Single Sign-On metadata information.
You'll need to copy the Assertion Consumer Service URL from the Duo Admin Panel and paste it into the ACS URL field in Google. This is found on the "Service Provider Details" page.
The Entity ID from the Duo Admin Panel should be copied and pasted into the Entity ID field in Google. This is also found on the "Service Provider Details" page.
Leave the Start URL field empty in Google.
Check the box next to Signed response in Google to ensure secure communication.
Set Name ID Format to UNSPECIFIED in Google.
You'll need to set Name ID to an attribute in Google that matches your Duo usernames.
Here's a table showing the attribute mapping required:
Custom Subdomain
Custom Subdomain configuration is a straightforward process that allows you to create a custom SSO login URL for your users.
If you didn't configure your custom subdomain during initial setup, you can do it from the main Single Sign-On page. Trial accounts are restricted from creating a subdomain, so make sure you're on a paid account.
To configure your custom subdomain, click the Subdomain tab while on the Single Sign-On page. You'll see your current default SSO login URL, and a "Customize subdomain" option to start creating your custom URL.
Enter the subdomain you'd like your users to see when logging in with Duo Single Sign-On. For example, you can enter "acme" and users would see "acme.login.duosecurity.com" in the URL.
Click Save to apply your changes, and you'll see a success message. Your custom subdomain will now be displayed in the URL on the "Subdomain" tab.
Here's a quick summary of the steps:
- Click the Subdomain tab on the Single Sign-On page.
- Click Customize subdomain to start creating your custom SSO login URL.
- Enter your desired subdomain and click Save.
End-to-End Configuration Overview
To configure Duo Single Sign-On, you'll need to follow a specific workflow. This process involves several steps, which we'll outline below.

First, ensure that you have met the prerequisites for configuring Duo Single Sign-On. This includes having an active Entra ID subscription, a Duo admin account with Owner role, a fully functional remote access VPN configuration, and specific versions of Secure Firewall Management Center and Secure Firewall Threat Defense.
The end-to-end configuration overview is as follows:
1. Configure a fully functional remote access VPN connection.
2. Configure the required users in your Entra Admin Center.
3. Create a Duo administrator account.
4. Log in to your Duo Admin Panel and configure single sign-on.
5. Add a primary authentication source for Duo SSO.
6. Configure Duo Single Sign-On Application in Entra ID.
7. Configure Entra ID as the Identity Provider in Duo.
8. Create a Protected Application in Duo.
9. Upload the Identity Provider Certificate to the Threat Defense Device.
10. Create a Single Sign-On Server Object.
11. Configure SAML Authentication for Remote Access VPN Users.
12. Deploy Your Configuration to the Threat Defense Device.
By following these steps, you'll be able to configure Duo Single Sign-On and ensure secure access to your applications.
Suggestion: Openssl 1.1.1 End of Life
Entra ID and Integration
You can configure Duo Single Sign-On to use Entra ID by downloading the SAML certificate from Entra ID, which Duo can use for decrypting tokens. The certificate is available under Set up Duo SSO in the Entra ID admin console.
To download the certificate, you need to copy the metadata information for Entra ID and return to the Duo Admin Panel. From there, you can specify a unique display name to identify the SAML identity provider, such as Entra ID.
In the Duo Admin Panel, you'll need to copy and paste the Microsoft Entra ID Identifier from the Entra ID into the Entity ID field. You'll also need to copy and paste the Login URL from Entra ID into the Single Sign-On URL field.
Broaden your view: How Much Data Do Security Cameras Use
Active Directory
To connect to Duo Single Sign-On, you'll need to configure an on-premises Authentication Proxy to talk to your Active Directory domain controllers.
The Authentication Proxy will allow Duo Single Sign-On to communicate with your Active Directory forest, which should have a Global Catalog.
With Active Directory as the Duo SSO authentication source, enter the primary username (email address) on the Duo SSO login page and click or tap Next.
You'll then need to enter the AD primary password and click or tap Log in to continue.
Enabling Duo Passwordless will allow you to log in to Duo SSO backed by Active Directory authentication without entering a password in the future.
This means you'll be able to access Duo SSO without having to remember or type a password.
Check this out: Wireless Security Cameras without Subscription
App in Entra ID
To configure the Duo Single Sign-On app in Entra ID, you'll need to follow these steps. Log into your Microsoft Entra admin center and click on the menu icon in the upper left-hand side of the page. Click on Entra ID, then navigate to Applications → Enterprise Applications and click + New application.
You'll need to create a new application for Duo SSO. Type "Duo SSO" or a descriptive name into the Input name field under "What's the name of your app?" and select the "non-gallery" option. After creating the application, navigate to the application's "Overview" page and click Assign users and groups to add users and groups that should have access to log in with Entra ID credentials to Duo Single Sign-On.
Readers also liked: Pentesting Azure Applications Pdf
To complete the configuration, you'll need to set up Single Sign-On with SAML. In the Entra ID admin center, click on the application's "Manage" tab and select Single sign-on. Choose SAML as the single sign-on method and click the Edit icon to edit the Basic SAML Configuration.
Here are the required fields to fill out in the Basic SAML Configuration:
Leave all other fields empty and click Save to save the changes. After saving, click the pencil icon next to "Attributes & Claims" and delete the four default claims. Then, click + Add new claim to add five additional claims to the application.
For your interest: Webflow How to Add a Honeypot
Identity Providers
Duo Single Sign-On supports various identity providers, including Entra ID, Google Workspace, and Ping Identity.
To configure Entra ID as an identity provider, follow the steps outlined in the "Configure the Duo Single Sign-On app in Entra ID" section. This involves setting up a new application in Entra ID, assigning users and groups, and configuring the Single Sign-On settings.
Check this out: Google Identity Check Pixel Phones
When using Entra ID, you'll need to provide the Duo Single Sign-On metadata information to Entra ID. This includes the Entity ID, Assertion Consumer Service URL, and other settings.
You can also configure other identity providers, such as Ping Identity, by following the specific instructions for each provider.
Here's a list of some of the identity providers supported by Duo Single Sign-On:
To ensure a smooth integration, it's essential to follow the specific instructions for each identity provider. This will help you set up Duo Single Sign-On correctly and provide a secure authentication experience for your users.
Security and Access
To ensure secure access to your applications, you need to grant access to the Duo users you want to use them. This step is crucial before inviting or requiring them to log in with Duo.
If you're setting up Duo Single Sign-On, you'll also need to complete Duo two-factor authentication when prompted, which will then redirect you back to the service provider application to complete the login process.
You can also log into service provider applications using Duo Central, our cloud-hosted portal, which allows users to access all their applications in one spot.
Security
Security is a top priority for any organization, and implementing a robust authentication system is crucial to protect sensitive information.
Duo Authentication provides an extra layer of security by requiring users to complete two-factor authentication before accessing an application.
This adds an additional step to the login process, making it much harder for unauthorized users to gain access.
By using Duo Authentication, organizations can significantly reduce the risk of security breaches.
You can also use Duo Central, a cloud-hosted portal, to access all of your applications in one spot.
This makes it easier for users to manage their applications and reduces the complexity of the login process.
Duo Single Sign-On allows users to authenticate once and access multiple applications, eliminating the need to remember multiple usernames and passwords.
This streamlines the login process and improves user experience.
By following these best practices, organizations can significantly improve their security posture and protect sensitive information.
Worth a look: Protect Your Posts Twitter
User Access Granting
Granting user access is a crucial step before inviting or requiring users to log in with Duo.
Make sure to grant access to the Duo users you want to use this application before they can log in.
If you haven't already granted user access, do it before proceeding with the login process.
Granting access ensures a smooth experience for both you and the users you're inviting or requiring to log in.
Worth a look: Whatsapp Web Log Out from All Devices
Enable Remembered Devices
Enabling Remembered Devices can greatly reduce the number of two-factor prompts you receive when switching between applications.
To minimize additional Duo two-factor prompts, apply a shared "Remembered Devices" policy to your SAML applications.
This policy allows your devices to be remembered across different applications, making it easier to switch between them without being prompted for two-factor authentication repeatedly.
Duo Single Sign-On SAML applications and Okta can benefit from this policy, reducing the number of two-factor prompts you receive when switching between them.
Recommended read: Why Is a Vpn Important When Working Remotely
Advanced Settings
When configuring Duo Security SSO, you'll need to set up a working authentication source before creating the Okta application in Duo.
To start, configure Single Sign-On in Okta, which involves creating an authentication source.
Before setting up SAML 2.0 settings, ensure you have a working authentication source.
On the SAML 2.0 settings page, you'll need to enter the following information:
- Assertion consumer service URL: Enter the SAML 2.0 post URL of your SOE site (https://[your_site].stackenterprise.co/auth/saml2/post).
- Single sign-on service URL: Copy the Single Sign-On URL value from Duo Security and paste it here.
- Issuer: Copy the Entity ID value from Duo Security and paste it here.
- Audience restriction: Enter any value (we suggest StackOverflowEnterprise). You'll enter this into Duo Security in a later step.
- Use Subject/NameID as user identifier: Leave this option checked.
In the SAML Response section of the page, set the following values, but unfortunately, the article doesn't specify what those values are.
Authentication and Authorization
To use Duo Single Sign-On, you need to configure your authentication source, which can be an Active Directory (AD) domain or forest, or a SAML Identity Provider. You can choose from various authentication sources, including Entra ID (Azure AD), Google Workspace, and others.
To set up SAML 2.0, you'll need to enter specific information, such as the Assertion consumer service URL, Single sign-on service URL, Issuer, and Audience restriction. These settings can be found on the SAML 2.0 settings page.
Here are some common SAML 2.0 settings:
Modify Sources
Modifying authentication sources is a crucial part of managing your Duo Single Sign-On setup. You can do this by clicking on the name of the authentication source you'd like to modify on the Single Sign-On page.
To enable or disable an authentication source, click the Edit button next to the "Status" field. If the authentication source is enabled, you can click Disable Source to disable it. Only authentication sources not being used by routing rules can be disabled.
You can also delete a disabled authentication source by clicking Delete Source. This is useful if you no longer need a particular authentication source.
Here are some specific authentication sources you can modify:
- ManageEngine AD360
- Red Hat Keycloak
Each authentication source has its own page where you can make changes. The status of the authentication source will be displayed at the top of the page, and you can use this information to determine whether it's enabled or disabled.
OAuth 2.0 Client Credentials
OAuth 2.0 Client Credentials is a way for applications to access protected resources on behalf of a user. This process involves the OAuth relying party making a call to Duo Single Sign-On with its client secret requesting access with specific scopes.
The OAuth relying party makes a call to Duo Single Sign-On with its client secret requesting access with specific scopes. Duo Single Sign-On validates the OAuth relying party is allowed to use requested scopes and then generates an access token and returns it to the OAuth relying party.
The OAuth relying party makes a request to the Resource Server and includes the access token. This is the key to accessing the protected resource. The access token is then validated by the Resource Server by making a call to Duo Single Sign-On with its client secret and the access token.
Once the access token has been validated, the Resource Server responds, allowing the OAuth relying party to do actions based on the scopes specified in the access token. This is a crucial step in the OAuth 2.0 Client Credentials flow.
Here's a step-by-step breakdown of the OAuth 2.0 Client Credentials flow:
- OAuth relying party makes a call to Duo Single Sign-On with its client secret requesting access with specific scopes.
- Duo Single Sign-On validates the OAuth relying party is allowed to use requested scopes and then generates an access token and returns it to the OAuth relying party.
- OAuth relying party makes a request to Resource Server and includes the access token.
- Resource Server makes a call to Duo Single Sign-On with its client secret and the access token to validate the token.
- Once the access token has been validated, Resource Server responds, allowing the OAuth relying party to do actions based on the scopes specified in the access token.
Workflow and Configuration
The workflow of Duo Security SSO is quite straightforward. A remote user initiates a remote access VPN connection request to the threat defense device, which redirects their browser to Duo SSO with an SAML request message.
The user's browser then gets redirected to Duo SSO, where they are prompted to authenticate using Duo two-factor authentication. This is a crucial step, as it adds an extra layer of security to the authentication process.
Here's a step-by-step breakdown of the workflow:
To configure Duo Security SSO, you'll need to complete a series of prerequisites, including configuring a fully functional remote access VPN connection and creating a Duo administrator account.
Featured Images: pexels.com

