<?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: If ACS server down no local authentication in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/if-acs-server-down-no-local-authentication/m-p/963384#M401542</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jason&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe that I have been bitten by this issue before myself. I believe that if you look carefully when you attempt to login and the TACACS servers are not available, that the error message that you get is authorization failure where we would generally expect to see authentication failure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe that the issue is in your configuration of aaa authorization. You currently have this configured:&lt;/P&gt;&lt;P&gt;aaa authorization exec default group tacacs+ local &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest that you change it to this:&lt;/P&gt;&lt;P&gt;aaa authorization exec default group tacacs+ if-authenticated&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Give it a try and let us know if it works better.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 22 Jun 2008 14:26:10 GMT</pubDate>
    <dc:creator>Richard Burts</dc:creator>
    <dc:date>2008-06-22T14:26:10Z</dc:date>
    <item>
      <title>If ACS server down no local authentication</title>
      <link>https://community.cisco.com/t5/network-access-control/if-acs-server-down-no-local-authentication/m-p/963382#M401540</link>
      <description>&lt;P&gt;noticed when my two tacacs servers are unreachable I can not login withlocal username, after the tacacs-server timeout (5 sec each) shouldn't it lookat local username admin? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(changed hostnames/keys for security) &lt;/P&gt;&lt;P&gt;username adminprivilege 15 secret 5 &amp;lt;removed&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;old&lt;/P&gt;&lt;P&gt;aaa new-model&lt;/P&gt;&lt;P&gt;aaa authentication login default group tacacs+ local&lt;/P&gt;&lt;P&gt;aaa authorization exec default group tacacs+ local&lt;/P&gt;&lt;P&gt;aaa accounting exec default start-stop group tacacs+&lt;/P&gt;&lt;P&gt;aaa accounting commands 15 default start-stop group tacacs+&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;tacacs-server host 10.10.0.10 key 7096F5C090B16291319&lt;/P&gt;&lt;P&gt;tacacs-server host 10.10.0.56 key 7096F5C090B16291319&lt;/P&gt;&lt;P&gt;tacacs-server directed-request&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 22:54:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/if-acs-server-down-no-local-authentication/m-p/963382#M401540</guid>
      <dc:creator>Jason Aarons</dc:creator>
      <dc:date>2019-03-10T22:54:26Z</dc:date>
    </item>
    <item>
      <title>Re: If ACS server down no local authentication</title>
      <link>https://community.cisco.com/t5/network-access-control/if-acs-server-down-no-local-authentication/m-p/963383#M401541</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) username adminprivilege 15 secret 5 &lt;REMOVED&gt;&lt;/REMOVED&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;username admin privilege 15 secret 5 &lt;REMOVED&gt;&lt;/REMOVED&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) Make sure both AAA servers are unreachable, a good way is the 'test aaa' command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3) Check the following debugs, and if possible post here:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;debug aaa authentication&lt;/P&gt;&lt;P&gt;debuga aa authorization&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you logging via console or VTY?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jun 2008 04:24:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/if-acs-server-down-no-local-authentication/m-p/963383#M401541</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-06-16T04:24:49Z</dc:date>
    </item>
    <item>
      <title>Re: If ACS server down no local authentication</title>
      <link>https://community.cisco.com/t5/network-access-control/if-acs-server-down-no-local-authentication/m-p/963384#M401542</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jason&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe that I have been bitten by this issue before myself. I believe that if you look carefully when you attempt to login and the TACACS servers are not available, that the error message that you get is authorization failure where we would generally expect to see authentication failure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe that the issue is in your configuration of aaa authorization. You currently have this configured:&lt;/P&gt;&lt;P&gt;aaa authorization exec default group tacacs+ local &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest that you change it to this:&lt;/P&gt;&lt;P&gt;aaa authorization exec default group tacacs+ if-authenticated&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Give it a try and let us know if it works better.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 22 Jun 2008 14:26:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/if-acs-server-down-no-local-authentication/m-p/963384#M401542</guid>
      <dc:creator>Richard Burts</dc:creator>
      <dc:date>2008-06-22T14:26:10Z</dc:date>
    </item>
  </channel>
</rss>

