<?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: TACACS via an ASA in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/tacacs-via-an-asa/m-p/1108732#M389260</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sure it can (we do it). You just need to translate from outside to inside. Here is an example, assume ACS is 192.168.1.10.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) 192.168.1.10  access-list TACACS tcp 65535 10000&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since the static uses an ACL, here is that part as well-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list TACACS extended permit ip host 192.168.1.10 host [public IP] &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The public IP in our case is the internet router and it requires a static route for the private IP pointing to the firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 30 Dec 2008 13:55:01 GMT</pubDate>
    <dc:creator>Collin Clark</dc:creator>
    <dc:date>2008-12-30T13:55:01Z</dc:date>
    <item>
      <title>TACACS via an ASA</title>
      <link>https://community.cisco.com/t5/network-access-control/tacacs-via-an-asa/m-p/1108731#M389190</link>
      <description>&lt;P&gt;Is it possible for a Cisco device (router or switch) to authenticate to an ACS via an ASA utilizing a Network Address Translation.  If so, what needs to be added to a config for this to take place.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 23:15:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/tacacs-via-an-asa/m-p/1108731#M389190</guid>
      <dc:creator>dphills18</dc:creator>
      <dc:date>2019-03-10T23:15:18Z</dc:date>
    </item>
    <item>
      <title>Re: TACACS via an ASA</title>
      <link>https://community.cisco.com/t5/network-access-control/tacacs-via-an-asa/m-p/1108732#M389260</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sure it can (we do it). You just need to translate from outside to inside. Here is an example, assume ACS is 192.168.1.10.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) 192.168.1.10  access-list TACACS tcp 65535 10000&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since the static uses an ACL, here is that part as well-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list TACACS extended permit ip host 192.168.1.10 host [public IP] &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The public IP in our case is the internet router and it requires a static route for the private IP pointing to the firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Dec 2008 13:55:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/tacacs-via-an-asa/m-p/1108732#M389260</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2008-12-30T13:55:01Z</dc:date>
    </item>
  </channel>
</rss>

