Duo Access Gateway (DAG) adds two-factor authentication, complete with inline self-service enrollment and authentication prompt to popular cloud services like Salesforce and Google Apps using SAML 2.0 federation.
Duo Access Gateway secures access to cloud applications with your users’ existing directory credentials (like Microsoft Active Directory or Google Apps accounts) using the Security Assertion Markup Language (SAML) 2.0 authentication standard. SAML delegates authentication from a service provider to an identity provider, and is used for single sign-on solutions (SSO).
Duo provides SAML connectors for enterprise cloud applications like Google Apps, Amazon Web Services, Box, Salesforce and Microsoft Office 365. Duo Access Gateway also ships with the ability for the customer to provide their own SAML “metadata” and connect to just about any app that supports the 2.0 standard.
Protected cloud applications redirect your users to the Duo Access Gateway server on your network. Your identity provider handles primary authentication, and Duo provides secondary authentication.
The Duo Access Gateway supports local Active Directory (AD) and OpenLDAP directories as identity sources, as well as on-premises or cloud SAML IdPs.
You can also use the Duo Access Gateway with Azure and Google directories or third-party IdPs hosted in the cloud.
Duo Access Gateway is part of the Platform Edition, so you can define policies that enforce unique controls for each individual SSO application. For example, you can require that Salesforce users complete two-factor authentication at every login, but only once every seven days when accessing Google Apps. Duo checks the user, device, and network against an application's policy before allowing access to the application.
Before you start installing Duo Access Gateway, make sure to complete all these requirements decribed below.
Launch Windows PowerShell as an administrator.
Enter the command
import-module servermanager to load the Server Manager PowerShell cmdlets.
Enter this command to install IIS and the additional components required by the Duo Access Gateway installer.
add-windowsfeature Web-Server, Web-Mgmt-Tools, Web-CGI, NET-Framework-Core, Web-Asp-Net45, Web-Scripting-Tools
If you receive an error about missing source for install you may need to mount your Windows Server ISO on your server VM or insert the Windows DVD and rerun the
add-windowsfeature command, appending
-source D:\sources\sxs (replacing D: with the actual drive letter) to the end. See your virtualization vendor's documentation for help mounting the Windows installer ISO on your virtual server.
Reboot the server if prompted.
The Duo Access Gateway installer will also install the Visual C++ Redistributable for Visual Studio 2015 package if not present on your server. The Visual C++ Redistributable for Visual Studio 2015 package is itself dependent on the Windows 10 Universal C Runtime (CRT). Ensure that the Universal C Runtime package is installed on your server before proceeding with DAG installation.
We've tested Duo Access Gateway with PHP x64 non thread safe distribution versions 7.0.12 and greater. Older PHP versions may not be used.
Download the PHP 7.0.15 VC14 x64 Non Thread Safe zip package. You do not need to unzip the file archive, just save the file in a location you can access later during the install.
Purchase an SSL certificate for your server from a commercial certificate authority (CA), using the fully qualified DNS name of your DAG server as the common name (e.g. yourserver.example.com). You may also use a wildcard SSL certificate.
Import that certificate into the machine's Web Server or Personal certificate store and create a binding for HTTPS/443 in IIS using that certificate on the "Default Web Site".
Here are instructions for importing a purchased certificate into IIS from Microsoft as well as some popular commercial CAs:
Using an SSL certificate from your internal enterprise CA is not recommended, as external clients do not trust your CA by default. Your users will receive certificate errors unless they can obtain and install the full certificate chain for certificates issued by your internal CA.
Browse to https://yourserver.example.com. You should see the IIS welcome page, and not receive any certificate warnings.
The DAG installer verifies the prerequisites and exits if any are missing. If your installation fails to complete please review the prerequisites, install any missing items flagged by the DAG installer, and try again.
Download the DAG installer executable from Duo and launch.
If the Microsoft Visual C++ 2015 Redistibutable Package (x64) is not present on your server then the DAG setup wizard prompts you to install it.
You must specify the location of PHP. Use the Browse utility to locate and select the PHP zip file you downloaded earlier and continue with the installation.
If you receive an error stating that the PHP version can not be verified, ensure that you have installed the Windows 10 Universal C Runtime prerequisite package.
If the installer prompts you to change impersonation mode, click Yes.
Should you receive an additional security warning prompt asking if you want to run the unsigned php.exe file, uncheck the Always ask before opening this file option and click Run.
Select the fully-qualified host name from the list. Choose the one that matches the external DNS entry for your DAG server.
If your IIS site binding uses a wildcard certificate then the installer can't determine the hostname. Type in the fully qualified hostname (i.e. yourserver.example.com) in the space provided.
By default the Duo Access Gateway administrative interface can only be accessed from the DAG server's assigned IP addresses. If you need to access the Duo Access Gateway admin console from an IP address not assigned to the DAG server's network interface(s) — such as an external IP address assigned to your DAG server by your public DNS service or a management server on your internal network — enter the additional IP addresses when prompted.
Click Install to complete Duo Access Gateway installation.
Important: Unless you specified additional access IP addresses during installation you can only access the Duo Access Gateway admin portal from the DAG server itself after install completes. Learn how to add additional allowed IPs after installation in our FAQ.
From the DAG server's console, click the Configure icon in the "Duo Access Gateway" application group to log on to https://yourserver.example.com/dag.
You must choose a new admin password at initial log on.
The DAG admin site lists all configuration options along the left.
Additionally, you'll find a link to the DAG documentation page, as well as a System Information link. Click System Information to view details about your Duo Access Gateway server, such as operating system build, fully qualified hostname, and PHP version.
Duo Access Gateway supports the following authentication sources:
In the DAG Admin Console, click Authentication Source. You'll notice that the Source type drop-down under Set Active Source has no options. You'll need to configure and save an authentication source before you can set one as active. Your first configured authentication source is automatically set as your active source.
In the Configure Sources section, select your desired Source type from the drop-down and enter your configuration settings.
|Server||The hostname or IP address of your domain controller. If entering more than one domain controller prefix the DC hostname or IP address with ldap:// and separate the entries with commas, for example
|Port||Enter the port used to communicate with Active Directory. The default port for LDAP and STARTTLS is 389, while the default port for LDAPS is 636. To search the Global Catalog the default port is 3268.|
|Transport type||This determines how the connection between the Duo Access Gateway and the Active Directory server is encrypted. The default, CLEAR, is unencrypted. Select STARTTLS or LDAPS to encrypt LDAP authentication traffic.|
|AD Certificate||To use STARTTLS or LDAPS encryption you’ll need the certificate from your domain controller certificate’s issuing CA. To obtain the PEM formatted version of the AD domain controller certificate’s issuing CA, view the “Certification Path” tab of the DC’s certificate properties and double-click the issuing certificate to view it. Export the issuing CA certificate as a Base-64 encoded X.509 (CER) format. If you have an intermediate CA export all the certs (such as root CA and intermediate CA) in the certification path and combine them into one file using a text editor. Copy the certificate file to the DAG server; then click the Browse button to select the exported certificate.|
|Attributes||Enter the AD user attributes required for SSO login. Many cloud service providers use the mail or sAMAccountname attributes. Check your service provider's SSO documentation for the specific attributes required. If you do not enter any attributes in this field, then Duo retrieves all user attributes. This is not recommended as it may negatively impact performance.|
|Search base||Enter the DN that corresponds to a container or OU in your directory structure containing the user accounts for SSO. You can enter multiple DNs in this field, one per line. Example DNs: CN=Users,dc=acme,dc=corp (searches the built-in Users container), OU=Employees,OU=US,DC=acme,DC=corp (searches within an organizational unit hierarchy), OU=Users,DC=EMEA,DC=acme,DC=corp (searches an OU in a child domain)|
|Search attributes||Enter the AD attributes that match the cloud application SSO username. These attributes must be included in the Attributes list above.|
|Search username||Enter the NTLM formatted username (e.g. DOMAIN\User) of an AD domain account that has permission to bind to Active Directory and perform LDAP queries.|
|Search password||Enter the password for the search username account.|
Save your Active Directory settings. If this is your first configured authentication source, the DAG sets this as your active source and contacts the domain controller using the provided information. If this is not your first configured authentication source you'll need to set this one as the active source using the dropdown under Set Active Source to test connectivity.
If you do not see a "Bind Succeeded" message please double-check your configuration information and verify the DAG server has the necessary connectivity to your domain controllers.
|Server||The comma-separated hostname(s) of your LDAP directory server(s).|
|Port||Enter the port used to communicate with OpenLDAP. The default port for LDAP and STARTTLS is 389, while the default port for LDAPS is 636.|
|Transport type||This determines how the connection between the Duo Access Gateway and the OpenLDAP server is encrypted. The default, CLEAR, is unencrypted. Select STARTTLS or LDAPS to encrypt LDAP authentication traffic.|
|Certificate||To use STARTTLS or LDAPS encryption you’ll need the certificate from your OpenLDAP directory server certificate’s issuing CA. If you have an intermediate CA export all the certs (such as root CA and intermediate CA) in the certification path and combine them into one file using a text editor. Copy the certificate file to the DAG server; then click the Browse button to select the exported certificate.|
|Attributes||Enter the OpenLDAP user attributes required for SSO login. Many cloud service providers use the mail or uid attributes. Check your service provider's SSO documentation for the specific attributes required. If you do not enter any attributes in this field, then Duo retrieves all user attributes. This is not recommended as it may negatively impact performance.|
|Search base||Enter the DN that corresponds to a container or OU in your directory structure containing the user accounts for SSO. You can enter multiple DNs in this field, one per line. Example DNs: ou=Employees,ou=US,dc=acme,dc=corp (searches within an organizational unit hierarchy), dc=acme,dc=corp (searches the entire domain)|
|Search attributes||Enter the LDAP attributes that match the cloud application SSO username. These attributes must be included in the Attributes list above.|
|Search username||Enter the dn of an OpenLDAP service account that has permission to bind to the directory and perform LDAP queries. Example service account DN: uid=ldapuser,ou=SvcAccts,dc=acme,dc=corp|
|Search password||Enter the password for the search username account.|
Save your OpenLDAP settings. If this is your first configured authentication source, the DAG sets this as your active source and contacts the directory server using the provided information. If this is not your first configured authentication source you'll need to set this one as the active source using the dropdown under Set Active Source to test connectivity.
If you do not see a "Bind Succeeded" message please double-check your configuration information and verify the DAG server has the necessary connectivity to your directory.
|Entity ID||The global, unique name for your SAML entity. This is provided by your primary authentication identity provider.|
|Single sign-on URL||The authentication URL for your identity provider.|
|Single logout URL||The logout URL for your identity provider.|
|Certificate||Download the token signing certificate for your identity provider, and then click the Browse button to select the exported certificate.|
|Username Attribute||The DAG uses the NameID SAML attribute as the username default. If you need to use a different username attribute, check the box next to the "Specify an alternate SAML username attribute instead of NameID" option, and type in your username attribute in the space provided.|
Save your SAML IdP settings.
If this is your first configured authentication source, the DAG sets this as your active source. If this is not your first configured authentication source you'll need to set this one as the active source using the dropdown under Set Active Source.
You'll need to ensure that your SAML IdP passes these attributes in its responses to the Duo Access Gateway:
|IdP Attribute||DAG Attribute|
You will also need to provide some information about your Duo Access Gateway server to your SAML IdP provider. You can find this information in the "Metadata" section at the bottom of the SAML IdP authentication source configuration page in the DAG console.
Before you can configure Google OpenID Connect as an authentication source you'll need to create an OAuth project in Google and collect some information to input into the DAG configuration page.
Log in to the Google Developers Console as an administrator for your Google Apps account.
If you do not already have an active project, click the Create Project button to create a new one. Give the new project a name and click Create. The page refreshes after creating your new project. You can also use an existing project.
Click the Enable and manage APIs link on the Dashboard. Once in the API Manager, click Credentials on the left, then click the Create credentials button and select OAuth client ID from the list.
If you created a new project you may need to first click Configure consent screen and enter a Product Name on the "OAuth consent screen" properties page. Click Save to return to the "Create client ID" page.
On the "Create client ID" page select Web application. Enter a descriptive Name for the new web client ID, and then enter the redirect URI for your Duo Access Gateway server (for example, https://yourserver.example.com/dag/module.php/oidc/linkback.php, replacing "yourserver.example.com" with the FQDN of your DAG server). You can find this in the "Metadata" section at the bottom of the Google (OpenID Connect) authentication source configuration page in the DAG console.
After pasting in the information click Create.
Make note of your client ID and client secret values. You'll need to enter these in the DAG admin console.
Return to the Duo Access Gateway admin console and enter the following information for the Google (OpenID Connect) authentication source.
|Domain|Enter your organization's Google Apps domain.|
|Client ID|Enter the Google OAuth web application client ID from the Google Developers Console.|
|Client Secret|Enter the Google OAuth web application client secret from the Google Developers Console.|
Save your Google (OpenID Connect) settings. If this is your first configured authentication source, the DAG sets this as your active source. If this is not your first configured authentication source you'll need to set this one as the active source using the dropdown under Set Active Source.
For more information about Google OpenID Connect and Google's OAuth 2.0 APIs please see Google's OpenID Connect guide.
In order to use the Duo Access Gateway with Azure Active Directory the Azure domain must be synced with an on-premises Active Directory domain so that the "mail" attribute is populated, or the Azure domain users must be provisioned with an Office 365 email address.
Before you can configure Azure OpenID Connect as an authentication source you'll need to create an Azure Active Directory web application in Azure and collect some information to input into the DAG configuration page.
Log in to the Microsoft Azure Administrator console as an Azure AD administrator.
Click Active Directory on the left and then click on the Azure Active Directory domain you want to use with the Duo Access Gateway.
Click APPLICATIONS under the name of your Azure AD domain near the top of the page, and then click the ADD button near the bottom center of the page.
When asked, "What do you want to do?" click Add an application my organization is developing to go to the next page.
Enter a descriptive name for the application and set the "Type" to WEB APPLICATION AND/OR WEB API. Click the arrow in the lower right to continue.
Enter the redirect URI for your Duo Access Gateway server (for example, https://yourserver.example.com/dag/module.php/oidc/linkback.php, replacing "yourserver.example.com" with the FQDN of your DAG server) as both the SIGN-ON URL and APP ID URI. You can find this in the "Metadata" section at the bottom of the Microsoft Azure (OpenID Connect) authentication source configuration page in the DAG console.
After pasting in the information click the check icon to complete new app creation.
Click on your newly created Azure AD application (the new application's information may be displayed to you automatically after creation). Click CONFIGURE under the name of your new application near the top of the page.
Scroll down the application configuration page to the keys section. Under "keys" click the Select duration drop-down and choose your desired duration. This creates a new key, but the key value is hidden until you save your changes. Click SAVE near the bottom center of the page.
The new key value is shown after you save. This is your only chance to view the key value! Be sure to copy it now; you'll need to enter it into the DAG admin console.
Scroll up slightly to view your CLIENT ID. You'll need to enter that into the DAG admin console as well.
The final piece of information you'll need is your Azure tenant ID. While the tenant ID isn't directly viewable in the Azure AD console, you can extract it from the URL of your Azure AD directory management console.
For example, if the URL shown in your browser when you are viewing your Azure AD directory in the portal is:
Your tenant ID would be the portion of the URL between "Directory/" and "/directoryQuickStart" — 01ab012c-0ab1-1ba0-a012-123456abcd01
Return to the Duo Access Gateway admin console and enter the following information for the Azure (OpenID Connect) authentication source.
|Domain||Enter your Azure organization's email domain.|
|Tenant ID||Enter the tenant ID of your Azure Active Directory (extracted from the Azure AD management console URL).|
|Client ID||Enter the CLIENT ID for the Azure application you created for the Duo Access Gateway.|
|Key||Enter the key value from the Azure application you created for the Duo Access Gateway.|
Save your Microsoft Azure (OpenID Connect) settings. If this is your first configured authentication source, the DAG sets this as your active source. If this is not your first configured authentication source you'll need to set this one as the active source using the dropdown under Set Active Source.
For more information about Microsoft Azure apps please see the MSDN Developer Network.
The fail mode determines whether to permit or deny user logons if the Duo Access Gateway is unable to contact Duo’s service. If the fail mode is safe, users who successfully pass primary authentication may access the cloud application without completing two-factor authentication. If the fail mode is secure then all user authentication attempts are rejected.
Session binding has two options, IP address binding and User agent binding.
Enabling the IP address binding option associates an authenticated Duo Access Gateway session to the client's IP address. Once users authenticate to a Duo protected cloud service they are not prompted again for primary authentication until the session lifetime is reached or the client's IP address changes. Users do not need to reauthenticate when their client IP changes if this setting remains disabled.
The User agent binding option associates an authenticated Duo Access Gateway session to the client browser's reported user agent (the information that identifies the browser type and version to web servers). By default, users need to reauthenticate if their reported browser information changes. Disable this option if you do not want users to reauthenticate to the Duo Access Gateway if their browser User-Agent changes after initial authentication.
The Session duration setting defines the maximum lifetime of a user's SSO session.
The Duo Access Gateway end-user logon page displays the Organization Name you enter here within the text of the primary authentication prompt.
Enable the Verbose logging option when troubleshooting DAG issues.
Set a new administrator password. We require a strong password that uses a mix of uppercase and lowercase letters, numbers, and special characters.
Important: When you create your cloud application in Duo you download a configuration file. This file contains information that uniquely identifies this application to Duo. Secure this file as you would any other sensitive or password information. Don't share it with unauthorized individuals or email it to anyone under any circumstances!
Limit unauthorized access to the cloud application configuration file by using a console browser session to download the file directly to the Access Gateway Server.
Duo has pre-configured SAML configurations for many popular cloud applications, like Salesforce, Google Apps, and Amazon Web Services.
We've mapped the most common authentication source attributes as follows:
|Duo Attribute||Active Directory||OpenLDAP||SAML IdP||Azure|
|First name attribute||givenName||gn||givenName||given_name||givenName|
|Last name attribute||sn||sn||sn||family_name||surname|
If your configured authentication source uses a different attribute than these mapped defaults, you'll have the opportunity to change it when creating the service provider application in Duo.
To provision one of the Duo supported service providers:
Log in to the Duo Admin Panel and click Applications on the left navigation tab. Then click Protect an Application.
Choose your cloud service from the list of applications. DAG supported cloud apps prefix the name with "SAML - ", such as "SAML - Salesforce" or "SAML - Zendesk". Click the Protect this Application link underneath your cloud service application's name.
Some Duo SAML applications require you to input additional information from your service provider to complete the application's configuration. Refer to the instructions for your cloud service for more information about the specific information required. Additionally, if your authentication source isn't using the Duo default attributes you can customize the attribute mapping.
When all required information for the service provider is entered (or if you made no changes), click the Save Configuration button.
Saving the service provider configuration creates a configuration file that you will import to the Duo Access Gateway. Click the Download your configuration file link to download JSON file to the DAG server.
You can also create a generic SAML Service Provider application in Duo, which requires you to input information about your cloud application. You will need to enter the following information supplied by the service provider.
|Service Provider Name||The name of the service provider.|
|Entity ID||The service provider identifier.|
|Assertion Consumer Service||The URL where your service provider receives SAML assertions.|
|NameID format||Format of NameID when sent to the service provider.|
|NameID attribute||The authentication source attribute used to identify the user to the service provider. This attribute is sent as the NameID. This is often a user's e-mail address ("mail" or "email").|
|Send attributes||By default the DAG sends only the NameID IdP attribute to a service provider. Change this option to "All" if your service provider requires additional attributes included in the SAML response.|
|Sign response||Leave this option enabled if the DAG needs to sign the SAML response to the service provider. Uncheck the box if the response should not be signed.|
|Sign assertion||Leave this option enabled if the DAG needs to sign the SAML assertion to the service provider. Uncheck the box if the assertion should not be signed.|
|Map attributes||If your service provider requires specific names for the attributes sent by the DAG identity provider, you can map the authentication source attributes to the required names here. Enter the attribute name from your authentication source on the left, and the new attribute name on the right. Consult your service provider's documentation for the required attribute names.|
|Create attributes||If your service provider requires that the DAG identity provider sends an attribute with a specific value, you can define that here. Enter the new attribute name on the left, and the static attribute value on the right. Consult your service provider's documentation for the required attribute names.|
Here's an example generic SAML Service Provider configuration
After entering the service provider information click the Save Configuration button and download the configuration file.
If your service provider requires IdP-initiated logins using SSO, the login URL is composed of the URL to your DAG logon page plus the entity id of the service to which you are authenticating, e.g. https://yourserver.example.com/dag/saml2/idp/SSOService.php?spentityid=Your_SP_Entity_ID.
From the DAG server's console, click the Configure icon in the "Duo Access Gateway" application group to log on to https://yourserver.example.com/dag. Log in with the administrator password and click Applications.
Click the Choose File button in the "Add Application" section of the page and locate the SAML application JSON file you downloaded from the Duo Admin Panel earlier. Click the Upload button after selecting the JSON configuration file.
The new SAML application is added.
You'll need to make some changes in your cloud application to add Duo Access Gateway authentication. Refer to our service provider configuration guides.
If you're adding Duo protection to another cloud application using the our generic SAML Service Provider application, check with the service provider for SSO instructions. You'll need to provide some information about Duo Access Gateway to that service provider, like URL information, a metadata file, a certificate file, or a certificate thumbprint. You can find this information in the "Metadata" section at the bottom of the DAG console's "Applications" page.
Streamline user access to your apps by enabling the DAG Launcher. The Launcher provides a portal from which users can access your Duo Access Gateway protected service provider applications with just a click.
To use the DAG Launcher, you'll need to create a specific application in the Admin Panel, just like you do for a service provider, and then use that information to configure the Launcher application in the DAG console.
Log in to the Duo Admin Panel and click Applications on the left navigation tab. Then click Protect an Application.
Choose Duo Access Gateway Launcher from the list of applications. Click Protect this Application to get your integration key, secret key, and API hostname. (See Getting Started for help.)
From the DAG server's console, click the Configure icon in the "Duo Access Gateway" application group to log on to https://yourserver.example.com/dag. Log in with the administrator password and click Launcher.
Enter the integration key, secret key, and API hostname from the Duo Access Gateway Launcher application you created earlier and click Save Setting.
You can optionally change Text of the the "Need help?" or the URL destination so that it points to a web page of your choosing instead of the Duo end user documentation. If you customize the help link, be sure to click Save Settings.
Give your users the launcher link mentioned at the top of the page.
When your users access the DAG launcher they'll first log in with their primary credentials, and then complete Duo two-factor authentication. After that users see a list of all SAML applications you've configured for use with the DAG.
By default, users perform Duo authentication when logging into the DAG launcher, and again when launching any SAML applications using the shortcuts in the DAG launcher. You can eliminate the second prompt for Duo authentication by assigning a Trusted Devices policy to the Duo Access Gateway Launcher application and to your SAML applications which has the trust-application option enabled. With this policy, your users will not need to authenticate to Duo again when accessing an app that shares the same policy. See the Trusted Devices policy documentation for details.
You can also restrict which application links display for a given user in the launcher. When creating your SAML service provider application in the Duo Admin Panel, populate the Permitted groups field with the Duo groups that contain the users you want to access that application. When a user who is not a member of the specified group(s) logs in to the launcher, the applications which have group restrictions are not shown. See the Using Groups documentation for more information and detailed instructions.
To verify your setup, log on to your configured cloud service provider. You'll be redirected to the Duo Access Gateway login page.
Enter your primary username and password. The Duo authentication prompt appears after successful primary authentication.
Approving the Duo authentication request completes login to the cloud application.
To upgrade the Duo Access Gateway, simply download the new version installer and run it on your deployed DAG server. The upgrade install automatically preserves your current DAG configuration.
If you are upgrading the Duo Access Gateway to version 1.3.1 from an earlier version you'll also need to update PHP to 7.0.12 or later. Download PHP as instructed for DAG installation, and when running the DAG 1.3.1 installer browse to the downloaded ZIP file. The DAG installer will take care of upgrading the PHP version you were using with the previous DAG version, and then continue upgrading Duo Access Gateway to 1.3.1.
If you are upgrading from DAG 1.1 and you plan on changing your authentication source from Active Directory to something different, you'll need to re-download the JSON configuration files for all your existing service provider applications from the Duo Admin Panel and upload the new JSON files into the Duo Access Gateway after the upgrade.
You won't be able to switch the authentication source to anything other than Active Directory until you import the new JSON files. You'll also receive an error if you do switch authentication sources and then try to upload a legacy JSON file that does not support your new authentication source.
If you will continue using Active Directory as your authentication source there is no need to update the service provider JSON files.
After deploying Duo Access Gateway in your environment you may later wish to upgrade the PHP version used by DAG. You can accomplish this with our standalone PHP updater tool. See the DAG FAQ for details.
Duo Access Gateway records the following events at C:\inetpub\wwwroot\dag\log\dag.log:
To enable debug output to the existing dag.log file, navigate to Settings in the DAG admin console. Scroll down to the "General" section and check the box next to Debugging. Click Save Changes when done.
We recommend deploying a second Duo Access Gateway server with the same configured SAML applications to serve as a standby replacement for the primary DAG server.
Deploy your standby DAG server, making sure to give it the same host name or CNAME alias as your primary DAG server, as the hostname entered during the DAG install cannot be changed later. Use the same IIS SSL certificate on both the primary and standby servers.
Copy the configured settings file C:\inetpub\wwwroot\dag\config\config.json from the primary DAG server to the DAG standby.
Copy the authentication source configuration .json file(s) in C:\inetpub\wwwroot\dag\config\authsources from the primary DAG server to the DAG standby.
Copy all .pem and .crt certificate files in C:\inetpub\wwwroot\dag\cert from the primary DAG server to the standby. There may be an ldap subfolder; copy this as well.
Copy the saml20-idp-hosted.json and saml20-idp-remote.json files in C:\inetpub\wwwroot\dag\metadata (if they exist) from the primary DAG server to the DAG standby.
Copy the imported service provider application JSON files in C:\inetpub\wwwroot\dag\metadata\saml20-sp-remote from the primary DAG server to the DAG standby.
If your primary DAG server is unavailable, you can activate your standby server to process user authentications.
You can also configure a load balancer in front of two identically configured DAG servers for active/active or active/passive high availability. In this scenario we recommend 8 hour persistence to match the lifetime of the Duo session cookie. Consult your load balancer solution documentation for guidance.
AD username format for DAG primary logon must be entered as sAMAccountName ("username") or email/userPrincipalName ("firstname.lastname@example.org"). NTLM logon ("DOMAIN\username") is not supported at this time.
SP user provisioning is not supported at this time.
Authentication sources other than Active Directory do not provide group membership information to the Duo Access Gateway. Therefore, these authentication sources cannot be used with service providers that verify group membership to provide access, such as Amazon Web Services or Meraki.
Need some help? Take a look at the Duo Access Gateway Frequently Asked Questions (FAQ) page or try searching our Knowledge Base articles or Community discussions. For further assistance, contact Support.