<?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: IOS Access Point Bombards TACACS+ Server with Requests  in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/ios-access-point-bombards-tacacs-server-with-requests/m-p/329632#M13334</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We experienced similar problems. We were instructed to use local authentication at the current time. Something about HTTP requiring authentication for each part of the page that accesses data. The configuration line is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip http authentication local&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The single connection did not help. We were also advised that if we required ACS HTTP authentication to use RADIUS because it scaled better than TACACS and would not be as impacted as TACACS. If neither of these are an option, another workaround is to, disable logging "passed authentications". We tested this and it prevented our ACS server from pegging the cpu, memory and I/O write queues. We opted for local authentication because the lack of "passed authentication" logs impacted our troubleshooting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good Luck&lt;/P&gt;&lt;P&gt;Gerry&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 20 Feb 2005 10:44:38 GMT</pubDate>
    <dc:creator>gwcrook</dc:creator>
    <dc:date>2005-02-20T10:44:38Z</dc:date>
    <item>
      <title>IOS Access Point Bombards TACACS+ Server with Requests</title>
      <link>https://community.cisco.com/t5/wireless/ios-access-point-bombards-tacacs-server-with-requests/m-p/329631#M13333</link>
      <description>&lt;P&gt;Problem: When using the web GUI to manage an IOS access point such as the AP350, AP1100, or AP1200, and when using TACACS+ to authenticate the HTTP accesses, the access point will send numerous authentication requests to the TACACS+ server for each web page accessed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Workaround given by cisco was to use single-connection tacacs server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question:&lt;/P&gt;&lt;P&gt;How to implement this command? Is it as below &lt;/P&gt;&lt;P&gt;"tacacs-server host x.x.x.x single-connection port 49 key test".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've tried using this command but still getting numerous authentication request.&lt;/P&gt;&lt;P&gt;Any help?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Ganesh&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 17:28:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ios-access-point-bombards-tacacs-server-with-requests/m-p/329631#M13333</guid>
      <dc:creator>ganeshp</dc:creator>
      <dc:date>2021-07-04T17:28:20Z</dc:date>
    </item>
    <item>
      <title>Re: IOS Access Point Bombards TACACS+ Server with Requests</title>
      <link>https://community.cisco.com/t5/wireless/ios-access-point-bombards-tacacs-server-with-requests/m-p/329632#M13334</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We experienced similar problems. We were instructed to use local authentication at the current time. Something about HTTP requiring authentication for each part of the page that accesses data. The configuration line is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip http authentication local&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The single connection did not help. We were also advised that if we required ACS HTTP authentication to use RADIUS because it scaled better than TACACS and would not be as impacted as TACACS. If neither of these are an option, another workaround is to, disable logging "passed authentications". We tested this and it prevented our ACS server from pegging the cpu, memory and I/O write queues. We opted for local authentication because the lack of "passed authentication" logs impacted our troubleshooting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good Luck&lt;/P&gt;&lt;P&gt;Gerry&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 Feb 2005 10:44:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ios-access-point-bombards-tacacs-server-with-requests/m-p/329632#M13334</guid>
      <dc:creator>gwcrook</dc:creator>
      <dc:date>2005-02-20T10:44:38Z</dc:date>
    </item>
  </channel>
</rss>

