<?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>article How to avoid password lockouts when serving passwords through AAM in Secrets Management Articles</title>
    <link>https://live.paloaltonetworks.com/t5/secrets-management-articles/how-to-avoid-password-lockouts-when-serving-passwords-through/ta-p/1427192</link>
    <description>Idira AAM provides two out of box methods to assist in preventing password lockouts during change cycles. They are: Dual Accounts and "ChangeNotificationPeriod"&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;

&lt;H3&gt;Steps&lt;/H3&gt;
&lt;BR /&gt;&lt;B&gt;Dual Accounts &lt;/B&gt;uses two service accounts to allow the application to activally use one account while the other is inactive and can be changed by the CPM with no impact to the application. Details on this process can be found on the online documentation portal&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://cyberarkdocu.azurewebsites.net/Product-Doc/OnlineHelp/AIM/Latest/en/Content/CP%20and%20ASCP/cv_Managing-Dual-Accounts.htm?" target="_blank"&gt;https://cyberarkdocu.azurewebsites.net/Product-Doc/OnlineHelp/AIM/Latest/en/Content/CP%20and%20ASCP/cv_Managing-Dual-Accounts.htm?&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;"ChangeNotificationPeriod"&amp;nbsp;&lt;/B&gt;Is a CPM platform setting under "Change Password" section. This setting signals the provider to stop using the local cache until the password is changed.&lt;BR /&gt;&lt;BR /&gt;This setting is configured in conjunction with the providers "CacheRefreshInterval". The change notification period should be set longer then the&amp;nbsp; providers cache refresh interval, long enough for the cache refresh cycle to run and start over with some padding to pickup the change notification&lt;BR /&gt;&lt;BR /&gt;If&lt;BR /&gt;CacheRefreshInterval=1500&lt;BR /&gt;then&lt;BR /&gt;ChangeNotificationPeriod=1680&lt;BR /&gt;&lt;BR /&gt;These values are in seconds. this is following the best practice of providers refereshing their cache every twenty five minutes, this means the change notification period will be twenty eight minutes which is three minutes longs then the cache refresh.</description>
    <pubDate>Thu, 05 Nov 2026 20:14:34 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-11-05T20:14:34Z</dc:date>
    <item>
      <title>How to avoid password lockouts when serving passwords through AAM</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management-articles/how-to-avoid-password-lockouts-when-serving-passwords-through/ta-p/1427192</link>
      <description>Idira AAM provides two out of box methods to assist in preventing password lockouts during change cycles. They are: Dual Accounts and "ChangeNotificationPeriod"&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;

&lt;H3&gt;Steps&lt;/H3&gt;
&lt;BR /&gt;&lt;B&gt;Dual Accounts &lt;/B&gt;uses two service accounts to allow the application to activally use one account while the other is inactive and can be changed by the CPM with no impact to the application. Details on this process can be found on the online documentation portal&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://cyberarkdocu.azurewebsites.net/Product-Doc/OnlineHelp/AIM/Latest/en/Content/CP%20and%20ASCP/cv_Managing-Dual-Accounts.htm?" target="_blank"&gt;https://cyberarkdocu.azurewebsites.net/Product-Doc/OnlineHelp/AIM/Latest/en/Content/CP%20and%20ASCP/cv_Managing-Dual-Accounts.htm?&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;B&gt;"ChangeNotificationPeriod"&amp;nbsp;&lt;/B&gt;Is a CPM platform setting under "Change Password" section. This setting signals the provider to stop using the local cache until the password is changed.&lt;BR /&gt;&lt;BR /&gt;This setting is configured in conjunction with the providers "CacheRefreshInterval". The change notification period should be set longer then the&amp;nbsp; providers cache refresh interval, long enough for the cache refresh cycle to run and start over with some padding to pickup the change notification&lt;BR /&gt;&lt;BR /&gt;If&lt;BR /&gt;CacheRefreshInterval=1500&lt;BR /&gt;then&lt;BR /&gt;ChangeNotificationPeriod=1680&lt;BR /&gt;&lt;BR /&gt;These values are in seconds. this is following the best practice of providers refereshing their cache every twenty five minutes, this means the change notification period will be twenty eight minutes which is three minutes longs then the cache refresh.</description>
      <pubDate>Thu, 05 Nov 2026 20:14:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management-articles/how-to-avoid-password-lockouts-when-serving-passwords-through/ta-p/1427192</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-11-05T20:14:34Z</dc:date>
    </item>
  </channel>
</rss>

