<?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 Password change policy issues in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/password-change-policy-issues/m-p/5206675#M592369</link>
    <description>&lt;P&gt;Hello, we recently forced users to do a password change in AD, and because we use ISE/Radius to authenticate them to the wireless, it has caused quite a few people to get locked out because their mobile devices have the old credentials cached. I am looking for suggestions on how to tackle this so if we do go to a strict password policy period, we dont get slammed with help desk calls for locked out accounts. Currently we ask the end user to forget the network and reconnect using the new password. Its easy enough for a handful but when its applied to 10k students, it might get ugly.&lt;/P&gt;&lt;P&gt;Our system is 4 Cisco 9800-40 WLC's and 6 ISE nodes spanned across 4 sites.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 10 Oct 2024 17:44:41 GMT</pubDate>
    <dc:creator>WayneWeezy</dc:creator>
    <dc:date>2024-10-10T17:44:41Z</dc:date>
    <item>
      <title>Password change policy issues</title>
      <link>https://community.cisco.com/t5/network-access-control/password-change-policy-issues/m-p/5206675#M592369</link>
      <description>&lt;P&gt;Hello, we recently forced users to do a password change in AD, and because we use ISE/Radius to authenticate them to the wireless, it has caused quite a few people to get locked out because their mobile devices have the old credentials cached. I am looking for suggestions on how to tackle this so if we do go to a strict password policy period, we dont get slammed with help desk calls for locked out accounts. Currently we ask the end user to forget the network and reconnect using the new password. Its easy enough for a handful but when its applied to 10k students, it might get ugly.&lt;/P&gt;&lt;P&gt;Our system is 4 Cisco 9800-40 WLC's and 6 ISE nodes spanned across 4 sites.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2024 17:44:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/password-change-policy-issues/m-p/5206675#M592369</guid>
      <dc:creator>WayneWeezy</dc:creator>
      <dc:date>2024-10-10T17:44:41Z</dc:date>
    </item>
    <item>
      <title>Re: Password change policy issues</title>
      <link>https://community.cisco.com/t5/network-access-control/password-change-policy-issues/m-p/5206742#M592377</link>
      <description>&lt;P&gt;May be you need to contact Wintel and Server Team, they should have tool where the user locked (if any one saved the password- that is not best practice as per security policies) - then they can release the user account based on the information.&lt;/P&gt;
&lt;P&gt;I am sure helpdesk should have tool to release, this is nothing to do with WLC or ISE.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2024 20:15:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/password-change-policy-issues/m-p/5206742#M592377</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2024-10-10T20:15:06Z</dc:date>
    </item>
  </channel>
</rss>

