<?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 Cisco ACS 5.3.0.40 and tacacs authentication against AD accounts in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-acs-5-3-0-40-and-tacacs-authentication-against-ad-accounts/m-p/2218425#M131637</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; brilliant, thanks for the response, we will try the patch.&lt;/P&gt;&lt;P&gt;thanks again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 30 May 2013 10:44:00 GMT</pubDate>
    <dc:creator>humphres1</dc:creator>
    <dc:date>2013-05-30T10:44:00Z</dc:date>
    <item>
      <title>Cisco ACS 5.3.0.40 and tacacs authentication against AD accounts</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-acs-5-3-0-40-and-tacacs-authentication-against-ad-accounts/m-p/2218423#M131604</link>
      <description>&lt;P&gt;We have successfully deployed a new ACS 5.3 which we use to do tacacs authentication against switches using an AD identity store. This all works fine. What we have found however is that when we type the incorrect password for an AD account (once), this immediately locks out the account on AD despite having a policy of three failed attempts before lockout (configured AD end). We are thinking the ACS is sending multiple authentication requests to AD for a single tacacs login request at the switch end if authentication fails and thereby reaching the three attempts very quickly if the password is incorrect. Ideally we only want the ACS to try once per request.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have searched everywhere for a configurable item on the ACS for how it deals with a failed password authentication request but can only find an advanced option under the identity section of the service policy we use for tacacs, but this is set to Reject if authentication fails - nothing to define how many times to try.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can anyone explain if this is the default action the ACS takes when trying to authenticate against AD identity store (multiple attempts if auth fails) or if this can be configured only to try once per request?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks for any insight regarding this&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 03:28:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-acs-5-3-0-40-and-tacacs-authentication-against-ad-accounts/m-p/2218423#M131604</guid>
      <dc:creator>humphres1</dc:creator>
      <dc:date>2019-03-11T03:28:58Z</dc:date>
    </item>
    <item>
      <title>Cisco ACS 5.3.0.40 and tacacs authentication against AD accounts</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-acs-5-3-0-40-and-tacacs-authentication-against-ad-accounts/m-p/2218424#M131618</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please ensure that have latest patch for ACS 5.3 installed. There are some fixes related to active directory that I think are relevant to this specific case. Latest patch is&amp;nbsp; 5.3.0.40.9&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think relevant CDETS is &lt;A href="https://www.cisco.com/cisco/psn/bssprt/bss?searchType=bstbugidsearch&amp;amp;page=bstBugDetail&amp;amp;BugID=CSCtz03211" target="_blank"&gt;CSCtz03211&lt;/A&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ACS 5.3 sends multiple authentication attempts to Active Directory&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In any case there were seevral important Active Dierctory related fixes included in patches for 5.3 and these are recommended for operation with Active Directory&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 May 2013 10:38:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-acs-5-3-0-40-and-tacacs-authentication-against-ad-accounts/m-p/2218424#M131618</guid>
      <dc:creator>jrabinow</dc:creator>
      <dc:date>2013-05-30T10:38:24Z</dc:date>
    </item>
    <item>
      <title>Cisco ACS 5.3.0.40 and tacacs authentication against AD accounts</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-acs-5-3-0-40-and-tacacs-authentication-against-ad-accounts/m-p/2218425#M131637</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; brilliant, thanks for the response, we will try the patch.&lt;/P&gt;&lt;P&gt;thanks again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 May 2013 10:44:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-acs-5-3-0-40-and-tacacs-authentication-against-ad-accounts/m-p/2218425#M131637</guid>
      <dc:creator>humphres1</dc:creator>
      <dc:date>2013-05-30T10:44:00Z</dc:date>
    </item>
  </channel>
</rss>

