https://community.cisco.com/t5/network-security/https-inbound-to-pix-using-authorization/m-p/900763#M958635 <P>I have a private web server behind a PIX firewall. Is there a method of having the PIX require inbound authorization (UID and Password, credentials stored on an AAA server or in the local database), prior to allowing a connection to the protected web server ? </P> Wed, 13 Mar 2019 00:51:04 GMT scotthale 2019-03-13T00:51:04Z https://community.cisco.com/t5/network-security/https-inbound-to-pix-using-authorization/m-p/900763#M958635 <P>I have a private web server behind a PIX firewall. Is there a method of having the PIX require inbound authorization (UID and Password, credentials stored on an AAA server or in the local database), prior to allowing a connection to the protected web server ? </P> Wed, 13 Mar 2019 00:51:04 GMT https://community.cisco.com/t5/network-security/https-inbound-to-pix-using-authorization/m-p/900763#M958635 scotthale 2019-03-13T00:51:04Z https://community.cisco.com/t5/network-security/https-inbound-to-pix-using-authorization/m-p/900764#M958636 <HTML><HEAD></HEAD><BODY><P>Sure, this is what authorization proxy is for. The documentation for this is pretty good and does a better job than what I could do here. The documentation is located here for recent versions of the PIX software:</P><P></P><P><A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/security/asa/asa80/configuration/guide/fwaaa.html" target="_blank">http://www.cisco.com/en/US/docs/security/asa/asa80/configuration/guide/fwaaa.html</A></P><P></P><P>Old software used "aaa authentication include". New software has moved to "aaa authentication match".</P><P></P><P>You must define your AAA server prior to the "aaa authentication xxxxxx" command since the aaa command references the AAA server.</P><P></P><P>Hope this helps.</P></BODY></HTML> Fri, 14 Dec 2007 14:07:31 GMT https://community.cisco.com/t5/network-security/https-inbound-to-pix-using-authorization/m-p/900764#M958636 elparis 2007-12-14T14:07:31Z