Introduction
- Cisco Anyconnect Azure Mfa
- Azure Anyconnect Training
- Cisco Anyconnect Saml Azure Ad
- Cisco Anyconnect Azure Ad Mfa
- Anyconnect Azure Mfa Nps
This document provides a configuration example of Security Assertion Markup Language (SAML) Authentication on FTD managed over FMC. The configuration allow Anyconnect users to establish a VPN session authenticating with a SAML Identity Service Provider.
Prerequisites
Azure VPN Gateway. View All 6 Integrations. Claim Cisco AnyConnect and update features and information. This is a setup by step instructions on how to create your Win32 App for Cisco AnyConnect Secure Mobility Client v4.9.040403 + SBL.Instructions:1. Mar 15, 2021 Approach 2: YubiKey TOTP with Cisco AnyConnect and Azure AD via SAML This approach is based on the capabilities in Cisco ASA and the AnyConnect client to leverage Azure AD’s SAML SSO functionality. In this approach Azure AD acts as a SAML Identity Provided (IdP) and the Cisco ASA server acts as a Service Provider (SP) which validates the SAML.
Requirements
Cisco recommends that you have knowledge of these topics:
- Knowledge of Anyconnect configuration on FMC
- Knowledge of SAML and metatada.xml values
Components Used
The information in this document is based on these software and hardware versions:
- Firepower Threat Defense (FTD) version 6.7.0
- Firepower Management Center (FMC) version 6.7.0
- ADFS from AD Server with SAML 2.0
Note: If possible, use a NTP server to synchronize time between the FTD and IdP. Otherwise, make sure the time is manually synchronized between them.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Background Information
Some of the current limitations for SAML are:
- SAML on either ASA or FTD is supported for Authentication only, for authorization you can use an external AAA server with protocols such Radius or LDAP
- Having SAML authentication attributes available in DAP evaluation (similar to RADIUS attributes sent in RADIUS auth response from AAA server) is not supported
- ASA supports SAML enabled tunnel-group on DAP policy. However, you cannot check the username attribute while using SAML authentication, because the username attribute is masked by the SAML Identity provider
- More limitations or SAML are described in the below link. These limitations apply to ASA and FTD: 'Guidelines and Limitations for SAML 2.0 '
Note: All the SAML configuration that needs to be implemented on the FTD, can be found on the metadata.xml file provided by your IdP.
Configuration
This section describes how to configure Anyconnect with SAML authentication on FTD
Get the SAML IdP parameters
The below image shows a SAML IdP metadata.xml file. From the output, you can get all values needed in order to configure the Anyconnect profile using SAML:
Configuration on the FTD via FMC
Step 1. Install and enroll the IdP certificate on the FMC. Navigate to Devices > Certificates
Step 2. Click Add. Select the FTD where you want to enroll this certificate. Under Cert Enrollment, click on the + sign
In the Add Cert Enrollment section, use any name as label for the IdP cert. Make sure you click on Manual. Check the CA Only and Skip Check for CA flag fields, Then, paste the base64 format IdP CA cert. Finally, click on Save and then on Add
Step 3. Configure the SAML server settings. Navigate to Objects > Object Management > AAA Servers > Single Sign-on Server. Then, select Add Single Sing-on Server
Step 4. Based on the metadata.xml file already provided by your IdP, configure the SAML values on the New Single Sign-on Server
Cisco Anyconnect Azure Mfa
Step 5. Configure the Connection Profile that uses this authentication method. Navigate to Devices > Remote Access and then edit your existing VPN Remote Access configuration
Step 6. Click on the + sign and add another Connection Profile
Step 7. Create the new Connection Profile and add the proper VPN local pool or DHCP Server
Step 8. Now, select the AAA tab. Under the Authentication Method option, select SAML. Under the the Authentication Server option, select the SAML object created on Step 4
Step 9. Finally, create a group-alias to map the connections to this Connection Profile. This is the tag that users can see on the Anyconnect Software drop-down menu. Once this is configured, select OK and save the complete SAML Authentication VPN configuration
Step 10. Navigate to Deploy > Deployment and select the proper FTD in order to apply the SAML Authentication VPN changes
Step 11. Now, provide the FTD's metadata.xml file to the IdP so they add the FTD as a trusted devic. On the FTD CLI, run the command: 'show saml metadata SAML_TG ' where SAML_TG is the name of our Connection Profile created on Step 7.
As seen in the below bracket, this is the expected output from the command mentioned above:
Once the metadata.xml from the FTD is provided to the IdP and they add it as a trusted device, test under the VPN connection can be done.
Verify
Verify if the VPN Anyconnect connection was established using SAML as authentication method with the commands seen below:
Troubleshoot
Some verification commands on the FTD CLI can be used to troubleshoot SAML and Remote Access VPN connection as seen in the bracket:
Note: You can troubleshoot DART from the Anyconnect's user PC as well
-->In this tutorial, you'll learn how to integrate Cisco AnyConnect with Azure Active Directory (Azure AD). When you integrate Cisco AnyConnect with Azure AD, you can:
Azure Anyconnect Training
- Control in Azure AD who has access to Cisco AnyConnect.
- Enable your users to be automatically signed-in to Cisco AnyConnect with their Azure AD accounts.
- Manage your accounts in one central location - the Azure portal.
Prerequisites
To get started, you need the following items:
Cisco Anyconnect Saml Azure Ad
- An Azure AD subscription. If you don't have a subscription, you can get a free account.
- Cisco AnyConnect single sign-on (SSO) enabled subscription.
Scenario description
In this tutorial, you configure and test Azure AD SSO in a test environment.
- Cisco AnyConnect supports IDP initiated SSO
Adding Cisco AnyConnect from the gallery
To configure the integration of Cisco AnyConnect into Azure AD, you need to add Cisco AnyConnect from the gallery to your list of managed SaaS apps.
- Sign in to the Azure portal using either a work or school account, or a personal Microsoft account.
- On the left navigation pane, select the Azure Active Directory service.
- Navigate to Enterprise Applications and then select All Applications.
- To add new application, select New application.
- In the Add from the gallery section, type Cisco AnyConnect in the search box.
- Select Cisco AnyConnect from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
Configure and test Azure AD SSO for Cisco AnyConnect
Configure and test Azure AD SSO with Cisco AnyConnect using a test user called B.Simon. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in Cisco AnyConnect.
To configure and test Azure AD SSO with Cisco AnyConnect, perform the following steps:
- Configure Azure AD SSO - to enable your users to use this feature.
- Create an Azure AD test user - to test Azure AD single sign-on with B.Simon.
- Assign the Azure AD test user - to enable B.Simon to use Azure AD single sign-on.
- Configure Cisco AnyConnect SSO - to configure the single sign-on settings on application side.
- Create Cisco AnyConnect test user - to have a counterpart of B.Simon in Cisco AnyConnect that is linked to the Azure AD representation of user.
- Test SSO - to verify whether the configuration works.
Configure Azure AD SSO
Follow these steps to enable Azure AD SSO in the Azure portal.
In the Azure portal, on the Cisco AnyConnect application integration page, find the Manage section and select single sign-on.
On the Select a single sign-on method page, select SAML.
On the Set up single sign-on with SAML page, click the edit/pen icon for Basic SAML Configuration to edit the settings.
On the Set up single sign-on with SAML page, enter the values for the following fields:
a. In the Identifier text box, type a URL using the following pattern:
< YOUR CISCO ANYCONNECT VPN VALUE >
b. In the Reply URL text box, type a URL using the following pattern:
< YOUR CISCO ANYCONNECT VPN VALUE >
Note
These values are not real. Update these values with the actual Identifier and Reply URL. Contact Cisco AnyConnect Client support team to get these values. You can also refer to the patterns shown in the Basic SAML Configuration section in the Azure portal.
On the Set up single sign-on with SAML page, in the SAML Signing Certificate section, find Certificate (Base64) and select Download to download the certificate file and save it on your computer.
On the Set up Cisco AnyConnect section, copy the appropriate URL(s) based on your requirement.
Note
Cisco Anyconnect Azure Ad Mfa
If you would like to on board multiple TGTs of the server then you need to add multiple instance of the Cisco AnyConnect application from the gallery. Also you can choose to upload your own certificate in Azure AD for all these application instances. That way you can have same certificate for the applications but you can configure different Identifier and Reply URL for every application.
Create an Azure AD test user
In this section, you'll create a test user in the Azure portal called B.Simon.
- From the left pane in the Azure portal, select Azure Active Directory, select Users, and then select All users.
- Select New user at the top of the screen.
- In the User properties, follow these steps:
- In the Name field, enter
B.Simon
. - In the User name field, enter the username@companydomain.extension. For example,
B.Simon@contoso.com
. - Select the Show password check box, and then write down the value that's displayed in the Password box.
- Click Create.
- In the Name field, enter
Assign the Azure AD test user
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to Cisco AnyConnect.
- In the Azure portal, select Enterprise Applications, and then select All applications.
- In the applications list, select Cisco AnyConnect.
- In the app's overview page, find the Manage section and select Users and groups.
- Select Add user, then select Users and groups in the Add Assignment dialog.
- In the Users and groups dialog, select B.Simon from the Users list, then click the Select button at the bottom of the screen.
- If you are expecting a role to be assigned to the users, you can select it from the Select a role dropdown. If no role has been set up for this app, you see 'Default Access' role selected.
- In the Add Assignment dialog, click the Assign button.
Configure Cisco AnyConnect SSO
You are going to do this on the CLI first, you might come back through and do an ASDM walk-through at another time.
Connect to your VPN Appliance, you are going to be using an ASA running 9.8 code train, and your VPN clients will be 4.6+.
First you will create a Trustpoint and import our SAML cert.
The following commands will provision your SAML IdP.
Now you can apply SAML Authentication to a VPN Tunnel Configuration.
Note
There is a feature with the SAML IdP configuration - If you make changes to the IdP config you need to remove the saml identity-provider config from your Tunnel Group and re-apply it for the changes to become effective.
Create Cisco AnyConnect test user
In this section, you create a user called Britta Simon in Cisco AnyConnect. Work with Cisco AnyConnect support team to add the users in the Cisco AnyConnect platform. Users must be created and activated before you use single sign-on.
Test SSO
In this section, you test your Azure AD single sign-on configuration with following options.
- Click on Test this application in Azure portal and you should be automatically signed in to the Cisco AnyConnect for which you set up the SSO
- You can use Microsoft Access Panel. When you click the Cisco AnyConnect tile in the Access Panel, you should be automatically signed in to the Cisco AnyConnect for which you set up the SSO. For more information about the Access Panel, see Introduction to the Access Panel.
Next Steps
Anyconnect Azure Mfa Nps
Once you configure Cisco AnyConnect you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. Learn how to enforce session control with Microsoft Cloud App Security.