Skip navigation

Duo Security is now a part of Cisco

About Cisco

Documentation

Duo Protection for Cisco ASA SSO with AnyConnect

Duo offers a variety of methods for adding two-factor authentication and flexible security policies to Cisco ASA SSO logins, complete with inline self-service enrollment and Duo Prompt.

Cisco ASA SSO requires ASA version of 9.7.1.24, 9.8.2.28, 9.9.2.1 or higher of each release, and AnyConnect 4.6 or later. Add Duo protection to earlier ASA versions with our SSL VPN or RADIUS configurations.

Overview

As business applications move from on-premises to cloud hosted solutions, users experience password fatigue due to disparate logons for different applications. Single sign-on (SSO) technologies seek to unify identities across systems and reduce the number of different credentials a user has to remember or input to gain access to resources.

While SSO is convenient for users, it presents new security challenges. If a user's primary password is compromised, attackers may be able to gain access to multiple resources. In addition, as sensitive information makes its way to cloud-hosted services it is even more important to secure access by implementing two-factor authentication.

Duo Access Gateway

Duo Access Gateway (DAG), our on-premises SSO product, layers Duo's strong authentication and flexible policy engine on top of Cisco ASA logins using the Security Assertion Markup Language (SAML) 2.0 authentication standard. Duo Access Gateway authenticates your users using existing on-premises or cloud-based directory credentials and prompts for two-factor authentication before permitting access to Cisco ASA.

Duo Access Gateway is included in the Duo Beyond, Duo Access, and Duo MFA plans, which also include the ability to 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 Cisco ASA. Duo checks the user, device, and network against an application's policy before allowing access to the application.

Deploy Duo Access Gateway

  1. Install Duo Access Gateway on a server in your DMZ. Follow our instructions for deploying the server, configuring DAG settings, and adding your primary authentication source.

  2. Add the attribute from the table below that corresponds to the Duo Mail attribute in the "Attributes" field when configuring your Active Directory or OpenLDAP authentication source in the DAG admin console. For example, if Active Directory is your authentication source, enter mail in the "Attributes" field.

    Duo Attribute Active Directory OpenLDAP
    Mail attribute mail mail

    If your organization uses another directory attribute than the one listed here enter that attribute name instead. If you've already configured the attributes list for another cloud service provider, append the additional attribute not already present to the list, separated by a comma.

  3. After completing the initial DAG configuration steps, click Applications on the left side of the Duo Access Gateway admin console.

  4. Scroll down the Applications page to the Metadata section. This is the information you need to provide to your Cisco ASA when configuring SSO. Click the Download Certificate link to obtain the token signing certificate (the downloaded file is named "dag.crt").

    DAG Metadata Information

Configure Cisco ASA SSO

Add the Duo Access Gateway to Cisco ASA as a new single sign-on provider. The Cisco ASA can be configured through the Cisco Adaptive Security Device Manager (ASDM) or the command-line interface (CLI).

Cisco Adaptive Security Device Manager (ASDM)

Upload Duo Access Gateway Certificate

  1. Connect to your Cisco ASA through your ASDM and log in as an administrative user.

  2. Click on the Configuration button at the top of the screen.

  3. Click Device Management in the bottom left-hand side of the screen.

  4. In the navigation bar on the left side expand Certificate Management and then click CA Certificates

  5. On the “CA Certificates” page click Add. A new window will pop-up.

  6. On the “Install Certificate” page type Duo_Access_Gateway into the “Trustpoint Name* field.

  7. While the “Install from a file” option is selected click Browse…. A new window will pop-up.

  8. Navigate to the location where you saved your dag.crt that you downloaded earlier and select it.

  9. Click Install Certificate. You’ll see a pop-up that says “Certificate installed Successfully”. Click OK.

    Cisco ASA ASDM Install Certificate

  10. Click Save at the top of the screen.

Configure AnyConnect Connection Profile

  1. While logged into the Cisco ASDM click Remote Access VPN at the bottom of the screen.

  2. On the left-hand navigation expand Network (Client) Access and click on AnyConnect Connection Profiles.

  3. Under “Connection Profiles” click select the Tunnel Group you'd like to protect with SSO. A new window will pop-up.

  4. Make sure the Tunnel Group has an Alias set.

  5. Under “Authentication” click the drop-down next to “Method” and select SAML.

  6. Under “SAML Identity Provider” click Manage… next to “SAML Server**. A new window will pop-up.

  7. On the “Configure SSO Servers SAML” screen click Add. A new window will pop-up.

  8. On the “Add SSO Server” page copy the Entity ID from the Duo Access Gateway admin console metadata display and paste it into the Cisco ASA IDP Entity ID field.

    Example: https://yourserver.example.com/dag/saml2/idp/metadata.php

  9. Next to Sign In URL select https from the drop-down. Copy the SSO URL from the Duo Access Gateway admin console metadata display and paste it into the Cisco ASA Sign In URL field. Remove the https:// from the pasted URL.

    Example: yourserver.example.com/dag/saml2/idp/SSOService.php

  10. Next to Sign Out URL select https from the drop-down. Copy the Logout URL from the Duo Access Gateway admin console metadata display and paste it into the Cisco ASA Sign Out URL field. Remove the https:// from the pasted URL.

    Example: yourserver.example.com/dag/saml2/idp/SingleLogoutService.php

  11. Next to Base URL select https from the drop-down. Enter the publicly resolvable hostname of your Cisco ASA into the field.

    Example: vpn.example.com

  12. Select Duo_Access_Gateway from the drop-down next to Identity Provider Certificate.

  13. Select Duo_Access_Gateway from the drop-down next to Service Provider Certificate.

  14. Leave the Request Signature sent to None.

  15. Type 300 into the Request Timeout field.

  16. Leave all other options at their default setting.

  17. Click OK to be returned to the “Configure SSO Servers SAML” page.

    Cisco ASA SSO Identity Provider Setup

  18. Click OK to be returned to the “Add AnyConnect Connection Profile” page.

  19. Make sure the Entity ID of the SSO Server you just configured is selected in the drop-down next to SAML Server.

  20. Continue filling out the page and click OK.

  21. Hit Apply and then click Save.

Learn more about Cisco ASA SSO at Cisco Support.

Command Line Interface (CLI)

Upload Trustpoint Certificate

  1. SSH into your ASA and access the config terminal.

    login as: asaadmin
    asaadmin@ciscoasa's password:
    Type help or '?' for a list of available commands.
    ciscoasa> enable
    Password: ********
    ciscoasa# configure terminal
    ciscoasa(config)#
    
  2. Enter the following to begin uploading the Duo Access Gateway metadata certificate:

    ciscoasa(config)#crypto ca trustpoint Duo_Access_Gateway
    ciscoasa(config-ca-trustpoint)#
    
  3. Enter the commands below. When prompted open the dag.crt file in a text editor (like Notepad), and copy the entire contents of the file (including the -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- lines). Paste the certificate text into your terminal. Type quit on its own line and then hit return.

    ciscoasa(config-ca-trustpoint)# enrollment terminal
    ciscoasa(config-ca-trustpoint)# crypto ca authenticate Duo_Access_Gateway
    Enter the base 64 encoded CA certificate. End with the word "quit" on a line by itself
        -----BEGIN CERTIFICATE-----
    MIIDYTCCAkmgAwIBAgIBADANBgkqhkiG9w0BAQsFADBLMQswCQYDVQQGEwJVUzEL
    MAkGA1UECAwCTUkxEjAQBgNVBAcMCUFubiBBcmJvcjEbMBkGA1UECgwSRHVvIFNl
    Y3VyaXR5LCBJbmMuMB4XDTE4MDUyNDIzMzczMVoXDTI4MDUyMTIzMzczMVowSzEL
    MAkGA1UEBhMCVVMxCzAJBgNVBAgMAk1JMRIwEAYDVQQHDAlBbm4gQXJib3IxGzAZ
    BgNVBAoMEkR1byBTZWN1cml0eSwgSW5jLjCCASIwDQYJKoZIhvcNAQEBBQADggEP
    ADCCAQoCggEBAMs1bsVnXNq0WA7lIdygzQ2BI3ArOcqE8DdUZgV9QARXhTds976B
    u8JI4ZaFNOHQyDdWadwzX1gH1qO9n+BtAUSAcUsmM5HhHuLn4Zu8+xpBfOxM/R9N
    s3yQSbTL3JEESsQFi7IDb3x75xkxi5x7/trUAUrCOW3thwux/Tby3ycKZVOdF7pN
    QXXgfglYtpERo5wi162c2FLkFJ6Lxg0GdnlC7WqdkAOvpA+/q+MYG2QTqZkL+2F6
    a1vuza2ouUHm55PF1HZwfl8UCGygg45UFd+OVgZt1U47TwQHxy9n6PVyD8S++DMD
    pelkQHlriWaf18LPwy8vnmYVkyHOCXi4PVsCAwEAAaNQME4wHQYDVR0OBBYEFJZb
    I5+FfPjHQSmJuxCTp0TFMwHIMB8GA1UdIwQYMBaAFJZbI5+FfPjHQSmJuxCTp0TF
    MwHIMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEBAFvoonmxaEGzNN7a
    ddKIwVK9bdEkZrJiYCFmwlhrkEq+Xxmzr2ntu0zZVbWNQ/mdJSzhQ5ZFS4N9DHSS
    9oe5xDqRFRSEsPj0mT/MmJI9kFq7h8B32zYVZlcwy+GSC7wLOo4sIa2RfS3PxWeD
    ES5YpTda6E9M8nq6wLKrt/RUUDHAq5aieBaPtqmbSb+xNHq0k/15+Q4BFO1iqkr9
    ZMmbkErX4FYmRWfubYn+nBVLHjjXk81UxVhlsj+zP4OkLJyINTjs89LPshfknEts
    Dc80Fs1oUQ6JVnaWpsPm0QduevMNWjtA5nLm0x7PBjpSo/SsbDInK81BSkVLpzuj
    7c8OuOM=
    -----END CERTIFICATE-----
    quit
    
  4. You will be asked to accept the certificate. Type yes.

    INFO: Certificate has the following attributes:
    Fingerprint:     ca20076b b1daa7f8 76d535c6 8e404ccd
    Do you accept this certificate? [yes/no]: yes
    
    Trustpoint CA certificate accepted.
    
    % Certificate successfully imported
    ciscoasa(config)#
    

Add Duo Access Gateway as an SSO Server

  1. Enter config-webvpn and then copy the Entity ID from the Duo Access Gateway admin console metadata display and paste it into the server like the exmaple below.

    Example: https://yourserver.example.com/dag/saml2/idp/metadata.php

    ciscoasa(config)# webvpn
    ciscoasa(config-webvpn)# saml idp https://yourserver.example.com/dag/saml2/idp/metadata.php
    ciscoasa(config-webvpnsaml-idp)#
    
  2. Copy the SSO URL from the Duo Access Gateway admin console metadata display and enter it as the url sign-in.

    Example: https://yourserver.example.com/dag/saml2/idp/SSOService.php

    ciscoasa(config-webvpnsaml-idp)# url sign-in https://yourserver.example.com/dag/saml2/idp/SSOService.php
    
  3. Copy the Logout URL from the Duo Access Gateway admin console metadata display and enter it as the url sign-out.

    Example: https://yourserver.example.com/dag/saml2/idp/SingleLogoutService.php

    ciscoasa(config-webvpnsaml-idp)# url sign-out https://yourserver.example.com/dag/saml2/idp/SingleLogoutService.php
    
  4. Configure the Base URL of your Cisco ASA.

    Example: vpn.example.com.

    ciscoasa(config-webvpn-saml-idp)# base-url https://vpn.example.com
    
  5. Set the trustpoint certificate you uploaded earlier for the SSO server.

    ciscoasa(config-webvpn-saml-idp)# trustpoint idp Duo_Access_Gateway
    ciscoasa(config-webvpn-saml-idp)# trustpoint sp Duo_Access_Gateway
    ciscoasa(config-webvpn-saml-idp)#
    
  6. Set the timeout for when a pending SSO login is no longer valid. We recommend setting it to 300 seconds.

    ciscoasa(config-webvpn-saml-idp)# timeout assertion 300
    
  7. Set Force Re-Authentication to false.

    ciscoasa(config-webvpn-saml-idp)# no force re-authentication
    
  8. Exit saml-idp mode and verify that your configuration looks like the example below.

    ciscoasa(config-webvpn-saml-idp)# exit
    ciscoasa(config-webvpn)# show webvpn saml idp
    saml idp https://yourserver.example.com/dag/saml2/idp/metadata.php
    url sign-in https://yourserver.example.com/dag/saml2/idp/SSOService.php
    url sign-out https://yourserver.example.com/dag/saml2/idp/SingleLogoutService.php
    base-url https://vpn.example.com
    trustpoint idp Duo_Access_Gateway
    trustpoint sp Duo_Access_Gateway
    no signature
    no force re-authentication
    timeout assertion 300
    ciscoasa(config-webvpn)#
    

Set Tunnel Group to use SSO

Now that you've added the Duo Access Gateway as an SSO server in Cisco ASA you need to set a tunnel group to use the Duo Access Gateway for authentication.

  1. Create a tunnel group that will be used for SSO by using the commands below.

    • Replace "cloud-idp-dag" with the name of the tunnel group you'd like to use.
    • Replace "cloud_idp" with the alias name you'd like to use.
    • Replace https://yourserver.example.com/dag/saml2/idp/metadata.php with your Duo Access Gateway's Entity ID.
    ciscoasa(config) webvpn
    ciscoasa(config-webvpn)# tunnel-group-list enable
    ciscoasa(config-webvpn)# tunnel-group cloud-idp-dag type remote-access
    ciscoasa(config)# tunnel-group cloud-idp-dag webvpn-attributes
    ciscoasa(config-tunnel-webvpn)# authentication saml
    ciscoasa(config-tunnel-webvpn)# group-alias cloud_idp enable
    ciscoasa(config-tunnel-webvpn)# saml identity-provider https://yourserver.example.com/dag/saml2/idp/metadata.php
    
  2. Continue configuring your new tunnel group with any additional settings.

Learn more about Cisco ASA SSO at Cisco Support.

Create the Cisco ASA Application in Duo

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

  2. Click Protect an Application, locate SAML - Cisco ASA in the applications list, and click Protect this Application. See Getting Started for help.

  3. Enter the base URL of your Cisco ASA that you entered above as the Base URL. For example, if your Cisco ASA base URL is https://vpn.example.com then enter vpn.example.com.

  4. Enter the tunnel group of your Cisco ASA that you entered above as the Tunnel Group. The tunnel group name is case-sensitive and must match. For example, if your tunnel group is cloud-idp-dag then enter cloud-idp-dag.

  5. Cisco ASA uses the Mail attribute when authenticating. We've mapped Mail attribute to DAG supported authentication source attributes as follows:

    Duo Attribute Active Directory OpenLDAP SAML IdP Google Azure
    Mail attribute mail mail mail email mail

    If you are using a non-standard email attribute for your authentication source, check the Custom attributes box and enter the name of the attribute you wish to use instead.

  6. Click Save Configuration to generate a downloadable configuration file.

    Duo Cisco ASA Application Settings

  7. You can adjust additional settings for your new SAML application at this time — like changing the application's name from the default value, enabling self-service, or assigning a group policy — or come back and change the application's policies and settings after you finish SSO setup. If you do update any settings, click the Save Changes button when done.

  8. Click the Download your configuration file link to obtain the Cisco ASA application settings (as a JSON file).

    Important: 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!

Add the Cisco ASA Application to Duo Access Gateway

  1. Return to the Applications page of the DAG admin console session.

  2. Click the Choose File button in the "Add Application" section of the page and locate the Cisco ASA SAML application JSON file you downloaded from the Duo Admin Panel earlier. Click the Upload button after selecting the JSON configuration file.

  3. The Cisco ASA SAML application is added.

    Cisco ASA Application Added

Verify SSO

If your organization enabled the Duo Access Gateway Launcher, log into the Launcher page using the link provided by your administrator. Click Cisco ASA from the dashboard to access the application.

You can also log into your Cisco ASA using your organization’s login page e.g. https://vpn.example.com. Select the tunnel group and click Login. This redirects to the Duo Access Gateway login page. Enter your primary directory logon information, approve Duo two-factor authentication, and get redirected back to the Cisco ASA site after authenticating.

DAG Login and Authentication Prompt

Cisco AnyConnect mobile or desktop apps require version 4.6 or higher. Select your tunnel group from your AnyConnect client and click Login. You will be redirected to authenticate to Duo Access Gateway.

Congratulations! Your Cisco ASA users now authenticate using Duo Access Gateway.

Microsoft AD FS

Microsoft's Active Directory Federation Services (AD FS) is a popular choice for SSO because it easily integrates with the AD identity store many organizations already have deployed. Duo's support for cloud applications and SSO drops in to an existing AD FS installation to provide secondary authentication after a user passes primary authentication (successful Active Directory logon).

If you don't already have AD federation running the first step is to install and configure Microsoft AD FS in your organization. Deployment Guides for AD FS versions 2.1, and 3.0/4.0 are available from Microsoft.

Once your AD FS services are up and running, the second step is to configure the SSO partnership between your AD FS service and the external cloud resource, in this case Cisco ASA. Learn more about configuring Cisco ASA SSO with AD FS at the Cisco Support site.

After you have successfully configured and tested AD FS SSO login to Cisco ASA using your AD domain credentials, you can then install the Duo AD FS integration. AD FS protection is included with Duo's paid plans.

With the Duo integration for AD FS installed, users pass primary authentication to the AD FS service as usual. Once primary authentication succeeds, users are forwarded to the Duo service for secondary authentication. After approving logon using one of Duo's authentication methods, the user is fully logged in to Cisco ASA.

Other Identity Partners

Using a third-party SSO provider for cloud application access? Duo partners with leading cloud SSO providers like Okta and OneLogin to secure access with our strong and flexible authentication platform.

You can also use Duo two-factor authentication with CAS and Shibboleth on-premises IdPs.

Troubleshooting

Need some help? Try searching our Knowledge Base articles or Community discussions. For further assistance, contact Support.

Ready to Get Started?

Sign Up Free