<?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 PIX 501 RADIUS authentication problem in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/pix-501-radius-authentication-problem/m-p/345114#M5909</link>
    <description>&lt;P&gt;I am trying to configure my Pix 501 to authenticate incoming HTTP traffic on port 8081 through RADIUS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought that &lt;/P&gt;&lt;P&gt;aaa authentication include tcp/8081 outside 10.10.1.109 255.255.255.255 0.0.0.0 0.0.0.0 smsradius&lt;/P&gt;&lt;P&gt;should do the trick, but I don't get the prompt.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I change this comamnd to 'inside', it works and inside HTTP requests get challanged. So I assume that my command is correct.&lt;/P&gt;&lt;P&gt;I was wondering if this is because the Pix is trying to authenticate the client using port 80 and not 8081. Port 80 would be blocked by my provider. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How does the challange work, technically? Do I have to configure something else?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is what I see in the log:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Authorization denied from 24.34.193.190/1065 to 10.10.2.2/8081 (not authenticated) on interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 18:11:16 GMT</pubDate>
    <dc:creator>cdonner64</dc:creator>
    <dc:date>2020-02-21T18:11:16Z</dc:date>
    <item>
      <title>PIX 501 RADIUS authentication problem</title>
      <link>https://community.cisco.com/t5/network-access-control/pix-501-radius-authentication-problem/m-p/345114#M5909</link>
      <description>&lt;P&gt;I am trying to configure my Pix 501 to authenticate incoming HTTP traffic on port 8081 through RADIUS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought that &lt;/P&gt;&lt;P&gt;aaa authentication include tcp/8081 outside 10.10.1.109 255.255.255.255 0.0.0.0 0.0.0.0 smsradius&lt;/P&gt;&lt;P&gt;should do the trick, but I don't get the prompt.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I change this comamnd to 'inside', it works and inside HTTP requests get challanged. So I assume that my command is correct.&lt;/P&gt;&lt;P&gt;I was wondering if this is because the Pix is trying to authenticate the client using port 80 and not 8081. Port 80 would be blocked by my provider. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How does the challange work, technically? Do I have to configure something else?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is what I see in the log:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Authorization denied from 24.34.193.190/1065 to 10.10.2.2/8081 (not authenticated) on interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:11:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/pix-501-radius-authentication-problem/m-p/345114#M5909</guid>
      <dc:creator>cdonner64</dc:creator>
      <dc:date>2020-02-21T18:11:16Z</dc:date>
    </item>
    <item>
      <title>Re: PIX 501 RADIUS authentication problem</title>
      <link>https://community.cisco.com/t5/network-access-control/pix-501-radius-authentication-problem/m-p/345115#M5912</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Christian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may find the following document helpful for your situation:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00800941ae.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00800941ae.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if this helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jay&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Sep 2004 10:24:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/pix-501-radius-authentication-problem/m-p/345115#M5912</guid>
      <dc:creator>jmia</dc:creator>
      <dc:date>2004-09-13T10:24:44Z</dc:date>
    </item>
    <item>
      <title>Re: PIX 501 RADIUS authentication problem</title>
      <link>https://community.cisco.com/t5/network-access-control/pix-501-radius-authentication-problem/m-p/345116#M5915</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jay,&lt;/P&gt;&lt;P&gt;Thanks for pointing my to this document which I had already seen. The document does not mention it, but HTTP authentication only works on ports 80 or 8080.&lt;/P&gt;&lt;P&gt;(see &amp;lt;&lt;A class="jive-link-custom" href="http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&amp;amp;CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1dd64254/123#selected_message" target="_blank"&gt;http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&amp;amp;CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1dd64254/123#selected_message&lt;/A&gt;&amp;gt;)&lt;/P&gt;&lt;P&gt;I changed the port to 8080 and it started to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;c.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Sep 2004 11:46:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/pix-501-radius-authentication-problem/m-p/345116#M5915</guid>
      <dc:creator>cdonner64</dc:creator>
      <dc:date>2004-09-13T11:46:30Z</dc:date>
    </item>
  </channel>
</rss>

