<?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 ASA based portal authentication? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-based-portal-authentication/m-p/4134755#M1072906</link>
    <description>&lt;P&gt;Can the ASA can authenticate portal access on the firewall (non-firepower)?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ASA would have to intercept a https/http connection request to the public IP of the portal and shunt the request to an authentication service before allowing the traffic.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In other words, publish an internal and/or DMZ based website with one-to-one NAT to a public IP on the outside interface. The outside/dmz rules control what is allowed. Then have access authenticated by an artifact other than the webserver itself such as a radius server, Okta, or DUO.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I did not think this was supported.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 12 Aug 2020 18:02:05 GMT</pubDate>
    <dc:creator>lcaruso</dc:creator>
    <dc:date>2020-08-12T18:02:05Z</dc:date>
    <item>
      <title>ASA based portal authentication?</title>
      <link>https://community.cisco.com/t5/network-security/asa-based-portal-authentication/m-p/4134755#M1072906</link>
      <description>&lt;P&gt;Can the ASA can authenticate portal access on the firewall (non-firepower)?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ASA would have to intercept a https/http connection request to the public IP of the portal and shunt the request to an authentication service before allowing the traffic.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In other words, publish an internal and/or DMZ based website with one-to-one NAT to a public IP on the outside interface. The outside/dmz rules control what is allowed. Then have access authenticated by an artifact other than the webserver itself such as a radius server, Okta, or DUO.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I did not think this was supported.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Aug 2020 18:02:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-based-portal-authentication/m-p/4134755#M1072906</guid>
      <dc:creator>lcaruso</dc:creator>
      <dc:date>2020-08-12T18:02:05Z</dc:date>
    </item>
    <item>
      <title>Re: ASA based portal authentication?</title>
      <link>https://community.cisco.com/t5/network-security/asa-based-portal-authentication/m-p/4134807#M1072917</link>
      <description>&lt;P&gt;You more of looking WAF (web application firewall) - ASA does not alone can not give that feature for you.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;yes with NGFW.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Aug 2020 19:18:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-based-portal-authentication/m-p/4134807#M1072917</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2020-08-12T19:18:38Z</dc:date>
    </item>
  </channel>
</rss>

