<?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: AAA Authentication at Outside interface for port 1433 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/aaa-authentication-at-outside-interface-for-port-1433/m-p/226484#M985</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You might have to add a "aaa authorization". This will protect your 2.2.2.2 server from anyone who's trying to hit w/ port 1433. User will have to perform an authentication on port http first, then will be authorize to use tcp/1433 thru the PIX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may end up w/ a command like this (sorry I'm old and not using the match ACL command set)&lt;/P&gt;&lt;P&gt;aaa authorization include tcp/1433 outside 2.2.2.2 255.255.255.255 0.0.0.0 0.0.0.0 AuthServer&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also PIX will let user authenticate w/ tcp-port 21(ftp),23(telnet) and 80(http) only. Not sure w/ tcp/443(https).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please refer to this link:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_sw/v_63/cmdref/ab.htm#1056043" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_sw/v_63/cmdref/ab.htm#1056043&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may also use "show uauth" command to diagnose common login session.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 14 Nov 2003 18:50:46 GMT</pubDate>
    <dc:creator>mpalardy</dc:creator>
    <dc:date>2003-11-14T18:50:46Z</dc:date>
    <item>
      <title>AAA Authentication at Outside interface for port 1433</title>
      <link>https://community.cisco.com/t5/network-access-control/aaa-authentication-at-outside-interface-for-port-1433/m-p/226483#M969</link>
      <description>&lt;P&gt;Problem:&lt;/P&gt;&lt;P&gt;Want to let customer authenticate at PIX outside interface and then open up SQL port 1433 to run enterprise manager&lt;/P&gt;&lt;P&gt;Port 1433 not accessable by anyone else unless authenticated&lt;/P&gt;&lt;P&gt;I'm looking for the type of functionallity that the lock and key access lists can do in IOS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Customer will be outside the PIX,  The server in question (2.2.2.2) currently has a functioning static and access-lists that&lt;/P&gt;&lt;P&gt;allow the world to hit a web site hosted on the server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AAA is working for administrative login to the pix console over telnet and SSH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is what I have:real IP addresses removed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list OutsideAuth permit tcp any host 2.2.2.2 eq 1433 &lt;/P&gt;&lt;P&gt;access-list OutsideAuth permit tcp any host 2.2.2.100 eq www &lt;/P&gt;&lt;P&gt;access-list OutsideAuth permit tcp any host 2.2.2.100 eq https&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;aaa-server AuthServer protocol tacacs+ &lt;/P&gt;&lt;P&gt;aaa-server AuthServer (inside) host 1.1.1.1 password timeout 5&lt;/P&gt;&lt;P&gt;aaa authentication secure-http-client&lt;/P&gt;&lt;P&gt;aaa authentication telnet console AuthServer&lt;/P&gt;&lt;P&gt;aaa authentication ssh console AuthServer&lt;/P&gt;&lt;P&gt;aaa authentication match OutsideAuth outside AuthServer&lt;/P&gt;&lt;P&gt;virtual http 2.2.2.100&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My hope is that user could securely HTTP to 2.2.2.100, authenticate and then hit port 1433&lt;/P&gt;&lt;P&gt;If I hit the 2.2.2.100 address i get a web screen with a username and password boxes.  I dont see the &lt;/P&gt;&lt;P&gt;secure Java based authentication screen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Am I on the right track ?  Can this be done?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:08:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/aaa-authentication-at-outside-interface-for-port-1433/m-p/226483#M969</guid>
      <dc:creator>bvanbenschoten</dc:creator>
      <dc:date>2020-02-21T18:08:46Z</dc:date>
    </item>
    <item>
      <title>Re: AAA Authentication at Outside interface for port 1433</title>
      <link>https://community.cisco.com/t5/network-access-control/aaa-authentication-at-outside-interface-for-port-1433/m-p/226484#M985</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You might have to add a "aaa authorization". This will protect your 2.2.2.2 server from anyone who's trying to hit w/ port 1433. User will have to perform an authentication on port http first, then will be authorize to use tcp/1433 thru the PIX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may end up w/ a command like this (sorry I'm old and not using the match ACL command set)&lt;/P&gt;&lt;P&gt;aaa authorization include tcp/1433 outside 2.2.2.2 255.255.255.255 0.0.0.0 0.0.0.0 AuthServer&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also PIX will let user authenticate w/ tcp-port 21(ftp),23(telnet) and 80(http) only. Not sure w/ tcp/443(https).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please refer to this link:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_sw/v_63/cmdref/ab.htm#1056043" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_sw/v_63/cmdref/ab.htm#1056043&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may also use "show uauth" command to diagnose common login session.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Nov 2003 18:50:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/aaa-authentication-at-outside-interface-for-port-1433/m-p/226484#M985</guid>
      <dc:creator>mpalardy</dc:creator>
      <dc:date>2003-11-14T18:50:46Z</dc:date>
    </item>
  </channel>
</rss>

