<?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: How to control force cache refresh when the cache stored password and vault password is not synced? in Secrets Management</title>
    <link>https://live.paloaltonetworks.com/t5/secrets-management/how-to-control-force-cache-refresh-when-the-cache-stored/m-p/1308018#M215</link>
    <description>&lt;P&gt;Thanks for explaining. I would like to clarify one thing again.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If without those values or we did manual password changing, the cache will always give out-of-sync password (wrong password) to the application until we fix it manually or the next cache refresh interval? &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Credential Provider or cache didn't have any intelligent control to  do force cache refresh if authentication is failing in application side? &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 18 Dec 2022 12:59:06 GMT</pubDate>
    <dc:creator>thinzartheint_yoon</dc:creator>
    <dc:date>2022-12-18T12:59:06Z</dc:date>
    <item>
      <title>How to control force cache refresh when the cache stored password and vault password is not synced?</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/how-to-control-force-cache-refresh-when-the-cache-stored/m-p/1308016#M213</link>
      <description>&lt;P&gt;We are using Credential Provider - Persistent cache with CacheRefreshInterval = 1500 sec.&amp;nbsp;&lt;/P&gt;&lt;P&gt;What if the cache stored password is not synced anymore with vault password , AND next CacheRefreshInterval has not happened yet , the application authentication will be failed right? At that time, the cache will do force refresh automatically in first failure or in how many failure , cache will do force refresh? Any parameter related with that scenario? &lt;/P&gt;</description>
      <pubDate>Fri, 16 Dec 2022 04:59:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/how-to-control-force-cache-refresh-when-the-cache-stored/m-p/1308016#M213</guid>
      <dc:creator>thinzartheint_yoon</dc:creator>
      <dc:date>2022-12-16T04:59:07Z</dc:date>
    </item>
    <item>
      <title>Re: How to control force cache refresh when the cache stored password and vault password is not synced?</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/how-to-control-force-cache-refresh-when-the-cache-stored/m-p/1308017#M214</link>
      <description>&lt;P&gt;CacheRefreshInterval parameter is the frequency in seconds that the Credential Provider cache is refreshed by the background process.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Credential Provider &lt;A alt="https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-CP/12.6/en/Content/CP%20and%20ASCP/Credential-Provider-Configuration-Files.htm?tocpath=Administration%7CCredential%20Provider%7CCredential%20Provider%20configuration%7C_____1#mainappproviderconfplatformversion" href="https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-CP/12.6/en/Content/CP%20and%20ASCP/Credential-Provider-Configuration-Files.htm?tocpath=Administration%7CCredential%20Provider%7CCredential%20Provider%20configuration%7C_____1#mainappproviderconfplatformversion" target="_blank"&gt;docs&lt;/A&gt; contain the following best practice:&lt;/P&gt;&lt;P&gt;This value has an impact on the&lt;B&gt;&amp;nbsp;ChangeNotificationPeriod&lt;/B&gt;&amp;nbsp;parameter value defined in the Central Policy Manager, and on the&amp;nbsp;&lt;B&gt;LocalCacheLifespan&amp;nbsp;&lt;/B&gt;parameter value defined in&amp;nbsp;Application Server Credential Provider.&lt;/P&gt;&lt;P&gt;We recommend using the following values for these parameters:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;B&gt;CacheRefreshInterval&lt;/B&gt;= 1500 seconds&lt;/LI&gt;&lt;LI&gt;&lt;B&gt;ChangeNotificationPeriod&amp;nbsp;&lt;/B&gt;= 3001 seconds (calculated from (CacheRefreshInterval* 2) + 1). That is, there will be at least 2 refresh cycles before the password is released.&lt;/LI&gt;&lt;LI&gt;&lt;B&gt;LocalCacheLifeSpan&lt;/B&gt;&amp;nbsp;= ((CacheRefreshInterval/ 2) - 1) = 749 seconds, that is, the&amp;nbsp;Application Server Credential Provider&amp;nbsp;2nd-level cache will refresh twice as frequently as the&amp;nbsp;Credential Provider&amp;nbsp;cache.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;which mean, by adding &lt;B&gt;ChangeNotificationPeriod&lt;/B&gt; parameter the CP will connect to the vault once it will recognize the password had expired.&lt;/P&gt;&lt;P&gt;This is only if the password was changed by the CPM, it won't retrieve a new password if the password was changed manually.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 18 Dec 2022 12:54:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/how-to-control-force-cache-refresh-when-the-cache-stored/m-p/1308017#M214</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2022-12-18T12:54:27Z</dc:date>
    </item>
    <item>
      <title>Re: How to control force cache refresh when the cache stored password and vault password is not synced?</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/how-to-control-force-cache-refresh-when-the-cache-stored/m-p/1308018#M215</link>
      <description>&lt;P&gt;Thanks for explaining. I would like to clarify one thing again.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If without those values or we did manual password changing, the cache will always give out-of-sync password (wrong password) to the application until we fix it manually or the next cache refresh interval? &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Credential Provider or cache didn't have any intelligent control to  do force cache refresh if authentication is failing in application side? &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 18 Dec 2022 12:59:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/how-to-control-force-cache-refresh-when-the-cache-stored/m-p/1308018#M215</guid>
      <dc:creator>thinzartheint_yoon</dc:creator>
      <dc:date>2022-12-18T12:59:06Z</dc:date>
    </item>
    <item>
      <title>Re: How to control force cache refresh when the cache stored password and vault password is not synced?</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/how-to-control-force-cache-refresh-when-the-cache-stored/m-p/1308019#M216</link>
      <description>&lt;P&gt;yes, this is Credential Provider's behavior.&lt;/P&gt;&lt;P&gt;you understood it correctly.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Dec 2022 11:46:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/how-to-control-force-cache-refresh-when-the-cache-stored/m-p/1308019#M216</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2022-12-19T11:46:07Z</dc:date>
    </item>
  </channel>
</rss>

