<?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 VPN with Alias on FTD in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/vpn-with-alias-on-ftd/m-p/5289253#M1120966</link>
    <description>&lt;P&gt;Currently we have an ASA and use Secure Client 5.1.8.105 and two profiles using Alia that authenticate via 2FA. To get the correct profile, split tunnel or full tunnel a use tacks the alias on to the URL and then connects, authenticates full 2FA and gets the appropriate profile and goes to work.&lt;/P&gt;&lt;P&gt;Trying to replicate this on an FTD using same versions of client, and 7.4.2 gold star, it fails when trying to add the alias with a No valid certificates available for authentication being logged before disconnect.&lt;/P&gt;&lt;P&gt;To block hackers and spammers, DefaultGroup is setup for DefaultWEbVPN and is sent to AAA in the sky, IOW a dead server. To avoid being hacked on our active profiles, the drop down is disabled on login.&amp;nbsp; Its the exact same setup as the ASA which works fine.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I attempted to access this page since I managed via CDO, It's description states&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;Aliases —Provide an alternate name or URL for the connection profile. Remote Access &lt;STRONG&gt;VPN&lt;/STRONG&gt; administrators can enable or disable the &lt;STRONG&gt;Alias&lt;/STRONG&gt; names and &lt;STRONG&gt;Alias&lt;/STRONG&gt; URLs. &lt;STRONG&gt;VPN&lt;/STRONG&gt; users can choose an &lt;STRONG&gt;Alias&lt;/STRONG&gt; name when they connect to the &lt;STRONG&gt;FTD&lt;/STRONG&gt; device remote access &lt;STRONG&gt;VPN&lt;/STRONG&gt; using the AnyConnect &lt;STRONG&gt;VPN&lt;/STRONG&gt; client. Step 4: Click Save.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;but the URL is &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;A href="https://edge.us.cdo.cisco.com/content/docs/t_configure_multiple_connection_profiles.html#!c-migrating-palo-alto-networks-firewall-to-multicloud-defense-with-the-firewall-migration-tool-in-cisco-defense-orchestrator.html" target="_blank" rel="noopener"&gt;https://edge.us.cdo.cisco.com/content/docs/t_configure_multiple_connection_profiles.html#!c-migrating-palo-alto-networks-firewall-to-multicloud-defense-with-the-firewall-migration-tool-in-cisco-defense-orchestrator.html&lt;/A&gt; and it directs to a Migration document for Palo Alto.&amp;nbsp; Cisco&amp;nbsp; web techs must be drunk.&lt;/P&gt;&lt;P&gt;It looked like what I need is the doc prior to redirection, but its doesn't stay up long enough to understand what it says. Where can I find the documentation to configure teh Secure Connect to work as it does on my ASA by adding the alias to the URL&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://vpn.domain.com/mfa" target="_blank" rel="noopener"&gt;https://vpn.domain.com/mfa&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 08 May 2025 21:31:49 GMT</pubDate>
    <dc:creator>tahscolony</dc:creator>
    <dc:date>2025-05-08T21:31:49Z</dc:date>
    <item>
      <title>VPN with Alias on FTD</title>
      <link>https://community.cisco.com/t5/network-security/vpn-with-alias-on-ftd/m-p/5289253#M1120966</link>
      <description>&lt;P&gt;Currently we have an ASA and use Secure Client 5.1.8.105 and two profiles using Alia that authenticate via 2FA. To get the correct profile, split tunnel or full tunnel a use tacks the alias on to the URL and then connects, authenticates full 2FA and gets the appropriate profile and goes to work.&lt;/P&gt;&lt;P&gt;Trying to replicate this on an FTD using same versions of client, and 7.4.2 gold star, it fails when trying to add the alias with a No valid certificates available for authentication being logged before disconnect.&lt;/P&gt;&lt;P&gt;To block hackers and spammers, DefaultGroup is setup for DefaultWEbVPN and is sent to AAA in the sky, IOW a dead server. To avoid being hacked on our active profiles, the drop down is disabled on login.&amp;nbsp; Its the exact same setup as the ASA which works fine.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I attempted to access this page since I managed via CDO, It's description states&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;Aliases —Provide an alternate name or URL for the connection profile. Remote Access &lt;STRONG&gt;VPN&lt;/STRONG&gt; administrators can enable or disable the &lt;STRONG&gt;Alias&lt;/STRONG&gt; names and &lt;STRONG&gt;Alias&lt;/STRONG&gt; URLs. &lt;STRONG&gt;VPN&lt;/STRONG&gt; users can choose an &lt;STRONG&gt;Alias&lt;/STRONG&gt; name when they connect to the &lt;STRONG&gt;FTD&lt;/STRONG&gt; device remote access &lt;STRONG&gt;VPN&lt;/STRONG&gt; using the AnyConnect &lt;STRONG&gt;VPN&lt;/STRONG&gt; client. Step 4: Click Save.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;but the URL is &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;A href="https://edge.us.cdo.cisco.com/content/docs/t_configure_multiple_connection_profiles.html#!c-migrating-palo-alto-networks-firewall-to-multicloud-defense-with-the-firewall-migration-tool-in-cisco-defense-orchestrator.html" target="_blank" rel="noopener"&gt;https://edge.us.cdo.cisco.com/content/docs/t_configure_multiple_connection_profiles.html#!c-migrating-palo-alto-networks-firewall-to-multicloud-defense-with-the-firewall-migration-tool-in-cisco-defense-orchestrator.html&lt;/A&gt; and it directs to a Migration document for Palo Alto.&amp;nbsp; Cisco&amp;nbsp; web techs must be drunk.&lt;/P&gt;&lt;P&gt;It looked like what I need is the doc prior to redirection, but its doesn't stay up long enough to understand what it says. Where can I find the documentation to configure teh Secure Connect to work as it does on my ASA by adding the alias to the URL&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://vpn.domain.com/mfa" target="_blank" rel="noopener"&gt;https://vpn.domain.com/mfa&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 08 May 2025 21:31:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-with-alias-on-ftd/m-p/5289253#M1120966</guid>
      <dc:creator>tahscolony</dc:creator>
      <dc:date>2025-05-08T21:31:49Z</dc:date>
    </item>
    <item>
      <title>Re: VPN with Alias on FTD</title>
      <link>https://community.cisco.com/t5/network-security/vpn-with-alias-on-ftd/m-p/5289935#M1120993</link>
      <description>&lt;P&gt;You can reference the documentation for this feature in the on-prem FMC guide as this feature works the same from either management location.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/secure-firewall/management-center/device-config/770/management-center-device-config-77/vpn-remote-access.html#task_pvz_m35_5gb" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/secure-firewall/management-center/device-config/770/management-center-device-config-77/vpn-remote-access.html#task_pvz_m35_5gb&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 12 May 2025 12:51:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-with-alias-on-ftd/m-p/5289935#M1120993</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2025-05-12T12:51:26Z</dc:date>
    </item>
    <item>
      <title>Re: VPN with Alias on FTD</title>
      <link>https://community.cisco.com/t5/network-security/vpn-with-alias-on-ftd/m-p/5289949#M1120994</link>
      <description>&lt;P&gt;I figured it out, fat fingered the URL.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Time for new glasses.&lt;/P&gt;</description>
      <pubDate>Mon, 12 May 2025 13:18:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-with-alias-on-ftd/m-p/5289949#M1120994</guid>
      <dc:creator>tahscolony</dc:creator>
      <dc:date>2025-05-12T13:18:59Z</dc:date>
    </item>
  </channel>
</rss>

