<?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: Prevent Active Directory account lockout in Cisco ISE in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5111630#M589516</link>
    <description>Now I am following, still though the real fix here is to use certificate or SAML. What is the use/case for simple username/password? How are you performing MFA?&lt;BR /&gt;</description>
    <pubDate>Tue, 21 May 2024 07:06:29 GMT</pubDate>
    <dc:creator>ahollifield</dc:creator>
    <dc:date>2024-05-21T07:06:29Z</dc:date>
    <item>
      <title>Prevent Active Directory account lockout in Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5111036#M589501</link>
      <description>&lt;P&gt;Hello, community!&lt;/P&gt;&lt;P&gt;I am using&amp;nbsp;&lt;SPAN&gt;Enable Failed Authentication Protection&amp;nbsp;for radius ravpn in ISE to p&lt;/SPAN&gt;&lt;SPAN&gt;revent Active Directory User Lockout. The maximum password less than the maximum bad password attempts configured as the value of the badPwdCount attribute in the Active Directory and for Authentication Policy use the specific Active Directory join point (not scope mode) but it doesn't work correctly.&amp;nbsp;&amp;nbsp;User gets locked out even when the lockout prevention for Active Directory is enabled.&amp;nbsp;&lt;BR /&gt;I cannot understand what the reason could be. What needs to be configured or checked for a solution?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2024 13:04:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5111036#M589501</guid>
      <dc:creator>fira</dc:creator>
      <dc:date>2024-05-20T13:04:05Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent Active Directory account lockout in Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5111384#M589505</link>
      <description>&lt;P&gt;Use certificate or SAML auth instead.&amp;nbsp; How are you enabling MFA on your RAVPN solution?&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2024 17:59:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5111384#M589505</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2024-05-20T17:59:26Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent Active Directory account lockout in Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5111570#M589512</link>
      <description>&lt;P&gt;Thanks for answer,&amp;nbsp;&lt;SPAN class=""&gt;&lt;A href="https://community.cisco.com/t5/user/viewprofilepage/user-id/199513" target="_self"&gt;&lt;SPAN class=""&gt;ahollifield&lt;/SPAN&gt;&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV class=""&gt;I found the reason in nas-port-type radius attribute but&amp;nbsp;I could not find information how can override this attribute using cisco asa or maybe cisco ISE?&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Tue, 21 May 2024 03:33:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5111570#M589512</guid>
      <dc:creator>fira</dc:creator>
      <dc:date>2024-05-21T03:33:09Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent Active Directory account lockout in Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5111596#M589514</link>
      <description>The reason? Override what?&lt;BR /&gt;</description>
      <pubDate>Tue, 21 May 2024 06:08:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5111596#M589514</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2024-05-21T06:08:29Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent Active Directory account lockout in Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5111611#M589515</link>
      <description>&lt;P&gt;The reason why&amp;nbsp;&lt;SPAN&gt;Prevent Active Directory account lockout&amp;nbsp;didn't work.&amp;nbsp;Currently&amp;nbsp;NAS-Port-Type value in access-request from cisco asa = virtual and&amp;nbsp;Prevent Active Directory account lockout feature in ISE doesn't work with NAS-Port-Type=virtual so i have question is it possible to override value NAS-Port-Type attribute using asa or maybe cisco ISE?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 21 May 2024 06:24:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5111611#M589515</guid>
      <dc:creator>fira</dc:creator>
      <dc:date>2024-05-21T06:24:57Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent Active Directory account lockout in Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5111630#M589516</link>
      <description>Now I am following, still though the real fix here is to use certificate or SAML. What is the use/case for simple username/password? How are you performing MFA?&lt;BR /&gt;</description>
      <pubDate>Tue, 21 May 2024 07:06:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5111630#M589516</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2024-05-21T07:06:29Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent Active Directory account lockout in Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5111730#M589518</link>
      <description>&lt;P&gt;"&lt;SPAN&gt;What is the use/case for simple username/password?" - what does it mean&lt;/SPAN&gt;&lt;BR /&gt;MFA is used&lt;BR /&gt;&lt;SPAN&gt;Prevent Active Directory account lockout is good solution which&lt;/SPAN&gt;&amp;nbsp;does not affect users&lt;/P&gt;</description>
      <pubDate>Tue, 21 May 2024 09:04:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5111730#M589518</guid>
      <dc:creator>fira</dc:creator>
      <dc:date>2024-05-21T09:04:07Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent Active Directory account lockout in Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5111786#M589521</link>
      <description>How exactly is MFA implemented? Do you have something in between ISE and AD? Do some other way directly on the firewall?&lt;BR /&gt;</description>
      <pubDate>Tue, 21 May 2024 10:07:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5111786#M589521</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2024-05-21T10:07:31Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent Active Directory account lockout in Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5112055#M589528</link>
      <description>&lt;P&gt;AD(first) + OTP scheme&lt;/P&gt;</description>
      <pubDate>Tue, 21 May 2024 13:13:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5112055#M589528</guid>
      <dc:creator>fira</dc:creator>
      <dc:date>2024-05-21T13:13:22Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent Active Directory account lockout in Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5289330#M596266</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/199513"&gt;@ahollifield&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You mean to implementation certificate-based as first authentication on FTD and set expired date? Even external user / non-domain devices&amp;nbsp; try to use this certificate but cannot promised and failed authentication stage? And not lead to be AD account locked out even attacker known AD user? thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 06:53:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5289330#M596266</guid>
      <dc:creator>Da ICS16</dc:creator>
      <dc:date>2025-05-09T06:53:45Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent Active Directory account lockout in Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5291955#M596379</link>
      <description>&lt;P&gt;What exactly are you asking? I'm saying don't rely on AD at all. Use Certificate and redirect to the SAML IDP of your choice.&lt;/P&gt;</description>
      <pubDate>Mon, 19 May 2025 12:57:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/prevent-active-directory-account-lockout-in-cisco-ise/m-p/5291955#M596379</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2025-05-19T12:57:05Z</dc:date>
    </item>
  </channel>
</rss>

