<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Cisco ASA/Azure Active Directory/SAML - Limitations/Issues in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cisco-asa-azure-active-directory-saml-limitations-issues/m-p/4461873#M1083447</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1244396"&gt;@stevensharamatew&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;It really depends on how you implemented this setup, so please share more details.&lt;/P&gt;&lt;P&gt;If it is plain round-robin DNS, then most likely it is - you could be sending queries from one device, while AAD could resolve it to another one. If you created it via &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa98/configuration/vpn/asa-98-vpn-config/vpn-ha.html#id_61718" target="_self"&gt;VPN load-balancing&lt;/A&gt;, then it will not cause issues, as I already implemented this solution and it works great. You will have to create multiple applications on AAD side, as each VPN GW will have its on FQDN.&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Milos&lt;/P&gt;</description>
    <pubDate>Wed, 08 Sep 2021 17:35:18 GMT</pubDate>
    <dc:creator>Milos_Jovanovic</dc:creator>
    <dc:date>2021-09-08T17:35:18Z</dc:date>
    <item>
      <title>Cisco ASA/Azure Active Directory/SAML - Limitations/Issues</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-azure-active-directory-saml-limitations-issues/m-p/4461854#M1083446</link>
      <description>&lt;P&gt;Working with our VPN team to integrate Cisco ASA with Azure Active Directory/MFA.&amp;nbsp; There is a Azure AD gallery app.&amp;nbsp; That has been installed and enabled for SSO.&amp;nbsp; However, we are experiencing SAML Authentication Request failures.&amp;nbsp; Our VPN team believes this is because we are utilizing VPN/DNS load balancing and SAML authentication is unsupported.&lt;BR /&gt;Is this a true limitation?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Sep 2021 17:05:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-azure-active-directory-saml-limitations-issues/m-p/4461854#M1083446</guid>
      <dc:creator>stevensharamatew</dc:creator>
      <dc:date>2021-09-08T17:05:45Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA/Azure Active Directory/SAML - Limitations/Issues</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-azure-active-directory-saml-limitations-issues/m-p/4461873#M1083447</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1244396"&gt;@stevensharamatew&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;It really depends on how you implemented this setup, so please share more details.&lt;/P&gt;&lt;P&gt;If it is plain round-robin DNS, then most likely it is - you could be sending queries from one device, while AAD could resolve it to another one. If you created it via &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa98/configuration/vpn/asa-98-vpn-config/vpn-ha.html#id_61718" target="_self"&gt;VPN load-balancing&lt;/A&gt;, then it will not cause issues, as I already implemented this solution and it works great. You will have to create multiple applications on AAD side, as each VPN GW will have its on FQDN.&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Milos&lt;/P&gt;</description>
      <pubDate>Wed, 08 Sep 2021 17:35:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-azure-active-directory-saml-limitations-issues/m-p/4461873#M1083447</guid>
      <dc:creator>Milos_Jovanovic</dc:creator>
      <dc:date>2021-09-08T17:35:18Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA/Azure Active Directory/SAML - Limitations/Issues</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-azure-active-directory-saml-limitations-issues/m-p/4461893#M1083452</link>
      <description>&lt;P&gt;With VPN load balancing, the members share a common FQDN. I am pretty sure that's not currently supported when using SAML authentication.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Sep 2021 17:58:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-azure-active-directory-saml-limitations-issues/m-p/4461893#M1083452</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2021-09-08T17:58:00Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA/Azure Active Directory/SAML - Limitations/Issues</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-azure-active-directory-saml-limitations-issues/m-p/4461901#M1083455</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/326046"&gt;@Marvin Rhoads&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Members are sharing common FQDN, but at the same time they must have their own unique FQDNs (which are then used for SAML). I never check if it is officially supported, but I can tell you that it works. I implemented it and we are using it heavilly with one of my customers.&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Milos&lt;/P&gt;</description>
      <pubDate>Wed, 08 Sep 2021 18:09:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-azure-active-directory-saml-limitations-issues/m-p/4461901#M1083455</guid>
      <dc:creator>Milos_Jovanovic</dc:creator>
      <dc:date>2021-09-08T18:09:23Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA/Azure Active Directory/SAML - Limitations/Issues</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-azure-active-directory-saml-limitations-issues/m-p/4461905#M1083457</link>
      <description>&lt;P&gt;Thank you for the responses.&amp;nbsp; Will dig deeper and work with our VPN team.&amp;nbsp; Will provide update.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Sep 2021 18:15:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-azure-active-directory-saml-limitations-issues/m-p/4461905#M1083457</guid>
      <dc:creator>stevensharamatew</dc:creator>
      <dc:date>2021-09-08T18:15:23Z</dc:date>
    </item>
  </channel>
</rss>

