<?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: multiple aaa authentication statements in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/multiple-aaa-authentication-statements/m-p/541763#M426905</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, that is correct.  Logging in via the console will use the default method list for authentication.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The reason why it would be helpful to have both would be to have different authentication servers/methods to authentication your users based on what services they're trying to log into.  You could have had "aaa authentication login default local" so that users who console in (or use an alternate line) would simply login with a local username/password rather than going to tacacs+.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If we were to use your configuration that you have listed, the reason why we would have both the "default" and the "TACACS" method lists would be to reference different servers as the fallback method used for each list. In other words, if the tacacs+ server were unreachable for some odd reason, then lines using the default list (in your case, the console line) would fall back and use the local database for authentication.  For lines using the TACACS method list (in your case, the 5 vty lines), the fallback method would be to use the enable password.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry if this sounds like rambling.  Hope it helps.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sincerely,&lt;/P&gt;&lt;P&gt;Annie&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 10 Jul 2006 23:22:34 GMT</pubDate>
    <dc:creator>annnguy</dc:creator>
    <dc:date>2006-07-10T23:22:34Z</dc:date>
    <item>
      <title>multiple aaa authentication statements</title>
      <link>https://community.cisco.com/t5/network-access-control/multiple-aaa-authentication-statements/m-p/541762#M426904</link>
      <description>&lt;P&gt;aaa authentication login default group tacacs+ local&lt;/P&gt;&lt;P&gt;aaa authentication login TACACS group tacacs+ enable&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;line vty 0 4&lt;/P&gt;&lt;P&gt;login authentication TACACS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Base on the above configuration, I would assume if a user is telnet using one of the 5 vty lines then he/she is authenticated by "TACACS" method.  But if a user is console in then he/she is authenticated by "default" method.  Right?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a reason why someone would have both methods "default" and "TACACS" on the router at the same time?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thx &lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 21:39:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/multiple-aaa-authentication-statements/m-p/541762#M426904</guid>
      <dc:creator>situwayne</dc:creator>
      <dc:date>2019-03-10T21:39:22Z</dc:date>
    </item>
    <item>
      <title>Re: multiple aaa authentication statements</title>
      <link>https://community.cisco.com/t5/network-access-control/multiple-aaa-authentication-statements/m-p/541763#M426905</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, that is correct.  Logging in via the console will use the default method list for authentication.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The reason why it would be helpful to have both would be to have different authentication servers/methods to authentication your users based on what services they're trying to log into.  You could have had "aaa authentication login default local" so that users who console in (or use an alternate line) would simply login with a local username/password rather than going to tacacs+.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If we were to use your configuration that you have listed, the reason why we would have both the "default" and the "TACACS" method lists would be to reference different servers as the fallback method used for each list. In other words, if the tacacs+ server were unreachable for some odd reason, then lines using the default list (in your case, the console line) would fall back and use the local database for authentication.  For lines using the TACACS method list (in your case, the 5 vty lines), the fallback method would be to use the enable password.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry if this sounds like rambling.  Hope it helps.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sincerely,&lt;/P&gt;&lt;P&gt;Annie&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Jul 2006 23:22:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/multiple-aaa-authentication-statements/m-p/541763#M426905</guid>
      <dc:creator>annnguy</dc:creator>
      <dc:date>2006-07-10T23:22:34Z</dc:date>
    </item>
    <item>
      <title>Re: multiple aaa authentication statements</title>
      <link>https://community.cisco.com/t5/network-access-control/multiple-aaa-authentication-statements/m-p/541764#M426906</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Annie,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you so much for the clarification.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Jul 2006 15:04:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/multiple-aaa-authentication-statements/m-p/541764#M426906</guid>
      <dc:creator>situwayne</dc:creator>
      <dc:date>2006-07-11T15:04:21Z</dc:date>
    </item>
  </channel>
</rss>

