<?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 Authorization in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/tacacs-authorization/m-p/4834418#M1100384</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1507222"&gt;@proxymaster&lt;/a&gt; you can reboot the router, the configuration will revert to the previously saved version without the new TACACS server.&lt;/P&gt;
&lt;P&gt;Or perhaps you could define a null route to ZZ.ZZ.ZZ.ZZ on the upstream switch/router, so the router you cannot login to is unable to communicate with the new TACACS server and therefore you should be able to login using a local user account.&lt;/P&gt;</description>
    <pubDate>Fri, 12 May 2023 15:05:41 GMT</pubDate>
    <dc:creator>Rob Ingram</dc:creator>
    <dc:date>2023-05-12T15:05:41Z</dc:date>
    <item>
      <title>TACACS Authorization</title>
      <link>https://community.cisco.com/t5/network-security/tacacs-authorization/m-p/4834412#M1100383</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I need to migrate an old Cisco Secure ACS to a new TACACSGUI.&lt;BR /&gt;Old ACS run on two servers (XX.XX.XX.XX and&amp;nbsp;YY.YY.YY.YY), while the new server is ZZ.ZZ.ZZ.ZZ.&lt;/P&gt;&lt;P&gt;This was the previous configuration:&lt;/P&gt;&lt;P&gt;aaa group server tacacs+ TACACS-GROUP-SERVER&lt;BR /&gt;&amp;nbsp; &amp;nbsp;server XX.XX.XX.XX&lt;BR /&gt;&amp;nbsp; &amp;nbsp;server YY.YY.YY.YY&lt;/P&gt;&lt;P&gt;tacacs-server key 7 ENCRYPTED_KEY&lt;BR /&gt;tacacs-server host XX.XX.XX.XX&lt;BR /&gt;tacacs-server host YY.YY.YY.YY&lt;BR /&gt;&lt;BR /&gt;aaa authentication login default group TACACS-GROUP-SERVER local&lt;BR /&gt;aaa authentication login console group TACACS-GROUP-SERVER local&lt;BR /&gt;aaa authorization exec default group TACACS-GROUP-SERVER local&lt;BR /&gt;aaa authorization commands all default group TACACS-GROUP-SERVER local&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then I&amp;nbsp;made a rookie mistake.&lt;/P&gt;&lt;P&gt;I added the new server to the aaa group and removed the old ones, but I did not added the command line &lt;STRONG&gt;tacacs-server host ZZ.ZZ.ZZ.ZZ&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;aaa group server tacacs+ TACACS-GROUP-NAME&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;server ZZ.ZZ.ZZ.ZZ&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A moment later I lost connection and I'm locked out of the router.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now, using local router accounts I'm able to get into EXEC mode, but I'm not authorized to do a &lt;STRONG&gt;configure terminal&lt;/STRONG&gt;. It returns this error:&lt;BR /&gt;% Authorization denied for command 'configure terminal'.&lt;/P&gt;&lt;P&gt;I tried to change the "Shell Command Authorization Set" and other User Setup configurations on old ACS server, but it doesn't seem to make a difference.&lt;/P&gt;&lt;P&gt;I'm able to authenticate on old ACS server (even show logs on old ACS GUI) through the command&amp;nbsp;&lt;STRONG&gt;test aaa group tacacs+ USERNAME PASSWORD&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;Using old ACS/new TACASGUI registered accounts, I can't even login. None of the three servers register any log of authentication or authorization attempts.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Any suggestions on how to bypass TACACS to be able to&amp;nbsp;&lt;STRONG&gt;configure terminal&amp;nbsp;&lt;/STRONG&gt;again?&lt;/P&gt;</description>
      <pubDate>Fri, 12 May 2023 14:58:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tacacs-authorization/m-p/4834412#M1100383</guid>
      <dc:creator>proxymaster</dc:creator>
      <dc:date>2023-05-12T14:58:10Z</dc:date>
    </item>
    <item>
      <title>Re: TACACS Authorization</title>
      <link>https://community.cisco.com/t5/network-security/tacacs-authorization/m-p/4834418#M1100384</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1507222"&gt;@proxymaster&lt;/a&gt; you can reboot the router, the configuration will revert to the previously saved version without the new TACACS server.&lt;/P&gt;
&lt;P&gt;Or perhaps you could define a null route to ZZ.ZZ.ZZ.ZZ on the upstream switch/router, so the router you cannot login to is unable to communicate with the new TACACS server and therefore you should be able to login using a local user account.&lt;/P&gt;</description>
      <pubDate>Fri, 12 May 2023 15:05:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tacacs-authorization/m-p/4834418#M1100384</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2023-05-12T15:05:41Z</dc:date>
    </item>
    <item>
      <title>Re: TACACS Authorization</title>
      <link>https://community.cisco.com/t5/network-security/tacacs-authorization/m-p/4834426#M1100386</link>
      <description>&lt;P&gt;Hi Rob, thanks for the quick response!&lt;BR /&gt;&lt;BR /&gt;I think that rebooting the device will be a last resort option for me.&lt;BR /&gt;&lt;BR /&gt;So, if no TACACS server is available the local authentication/authorization is taken by default?&lt;/P&gt;</description>
      <pubDate>Fri, 12 May 2023 15:22:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tacacs-authorization/m-p/4834426#M1100386</guid>
      <dc:creator>proxymaster</dc:creator>
      <dc:date>2023-05-12T15:22:00Z</dc:date>
    </item>
    <item>
      <title>Re: TACACS Authorization</title>
      <link>https://community.cisco.com/t5/network-security/tacacs-authorization/m-p/4834449#M1100388</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1507222"&gt;@proxymaster&lt;/a&gt; yes it should fail back to local authentication if TACACS is unavailable.&lt;/P&gt;</description>
      <pubDate>Fri, 12 May 2023 15:42:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tacacs-authorization/m-p/4834449#M1100388</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2023-05-12T15:42:54Z</dc:date>
    </item>
  </channel>
</rss>

