<?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: newbie with auth-proxy in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/newbie-with-auth-proxy/m-p/334603#M429326</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Auth-proxy will authenticate the user only via HTTP, before they can send ANY traffic out.  Going by your description this is not what you want.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lock-and-Key might be more what you want.  See here for details:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fsecur_c/ftrafwl/scflock.htm" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fsecur_c/ftrafwl/scflock.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could define an ACL to the inside interface allowing everything EXCEPT HTTP/HTTPS.  Users doing FTP can just go straight out as normal then.  Then define dynamic entries to this ACL that allow all traffic.  For anyone to go out with HTTP/HTTPS they'd have to telnet to the router first, put in their login credentials, then they can browse out.  Something like the following should work for you:&lt;/P&gt;&lt;P&gt;&lt;B&gt;&lt;/B&gt;&lt;/P&gt;&lt;P&gt;interface ethernet0&lt;/P&gt;&lt;P&gt; description Inside interface&lt;/P&gt;&lt;P&gt; ip address 10.1.1.1 255.255.255.0&lt;/P&gt;&lt;P&gt; ip access-group 101 in&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list 101 deny tcp 10.1.1.0 0.0.0.255 any eq 80&lt;/P&gt;&lt;P&gt;access-list 101 deny tcp 10.1.1.0 0.0.0.255 any eq 443&lt;/P&gt;&lt;P&gt;access-list 101 permit ip 10.1.1.0 0.0.0.255 any&lt;/P&gt;&lt;P&gt;access-list 101 dynamic mytestlist timeout 120 permit ip any any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;line vty 0 4&lt;/P&gt;&lt;P&gt;login local&lt;/P&gt;&lt;P&gt;autocommand access-enable host timeout 5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It takes a bit of user education in that they will have to be told how to use this (first telnet to the router at 10.1.1.1, login, then you can use HTTP traffic outbound), but should give you what you want. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 13 Apr 2005 05:10:07 GMT</pubDate>
    <dc:creator>gfullage</dc:creator>
    <dc:date>2005-04-13T05:10:07Z</dc:date>
    <item>
      <title>newbie with auth-proxy</title>
      <link>https://community.cisco.com/t5/network-access-control/newbie-with-auth-proxy/m-p/334602#M429325</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I need to allow and deny some user to go to the Internet, but I want to allow/deny only for http traffic.&lt;/P&gt;&lt;P&gt;For exemple I dont want any user to have to authenticate if they want to use ftp.&lt;/P&gt;&lt;P&gt;Is it possible with the auth-proxy? if yes any configuration exemple?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the exemple I saw, the user had to authenticate to then allow his computer to send any packet to the Internet. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers Gael&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 21:06:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/newbie-with-auth-proxy/m-p/334602#M429325</guid>
      <dc:creator>gael.clavadetscher</dc:creator>
      <dc:date>2019-03-10T21:06:30Z</dc:date>
    </item>
    <item>
      <title>Re: newbie with auth-proxy</title>
      <link>https://community.cisco.com/t5/network-access-control/newbie-with-auth-proxy/m-p/334603#M429326</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Auth-proxy will authenticate the user only via HTTP, before they can send ANY traffic out.  Going by your description this is not what you want.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lock-and-Key might be more what you want.  See here for details:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fsecur_c/ftrafwl/scflock.htm" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fsecur_c/ftrafwl/scflock.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could define an ACL to the inside interface allowing everything EXCEPT HTTP/HTTPS.  Users doing FTP can just go straight out as normal then.  Then define dynamic entries to this ACL that allow all traffic.  For anyone to go out with HTTP/HTTPS they'd have to telnet to the router first, put in their login credentials, then they can browse out.  Something like the following should work for you:&lt;/P&gt;&lt;P&gt;&lt;B&gt;&lt;/B&gt;&lt;/P&gt;&lt;P&gt;interface ethernet0&lt;/P&gt;&lt;P&gt; description Inside interface&lt;/P&gt;&lt;P&gt; ip address 10.1.1.1 255.255.255.0&lt;/P&gt;&lt;P&gt; ip access-group 101 in&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list 101 deny tcp 10.1.1.0 0.0.0.255 any eq 80&lt;/P&gt;&lt;P&gt;access-list 101 deny tcp 10.1.1.0 0.0.0.255 any eq 443&lt;/P&gt;&lt;P&gt;access-list 101 permit ip 10.1.1.0 0.0.0.255 any&lt;/P&gt;&lt;P&gt;access-list 101 dynamic mytestlist timeout 120 permit ip any any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;line vty 0 4&lt;/P&gt;&lt;P&gt;login local&lt;/P&gt;&lt;P&gt;autocommand access-enable host timeout 5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It takes a bit of user education in that they will have to be told how to use this (first telnet to the router at 10.1.1.1, login, then you can use HTTP traffic outbound), but should give you what you want. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Apr 2005 05:10:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/newbie-with-auth-proxy/m-p/334603#M429326</guid>
      <dc:creator>gfullage</dc:creator>
      <dc:date>2005-04-13T05:10:07Z</dc:date>
    </item>
  </channel>
</rss>

