How to control force cache refresh when the cache stored password and vault password is not synced?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How to control force cache refresh when the cache stored password and vault password is not synced?

We are using Credential Provider - Persistent cache with CacheRefreshInterval = 1500 sec. 

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?

1 accepted solution

Accepted Solutions

L1 Bithead

CacheRefreshInterval parameter is the frequency in seconds that the Credential Provider cache is refreshed by the background process.

 

Credential Provider docs contain the following best practice:

This value has an impact on the ChangeNotificationPeriod parameter value defined in the Central Policy Manager, and on the LocalCacheLifespan parameter value defined in Application Server Credential Provider.

We recommend using the following values for these parameters:

  • CacheRefreshInterval= 1500 seconds
  • ChangeNotificationPeriod = 3001 seconds (calculated from (CacheRefreshInterval* 2) + 1). That is, there will be at least 2 refresh cycles before the password is released.
  • LocalCacheLifeSpan = ((CacheRefreshInterval/ 2) - 1) = 749 seconds, that is, the Application Server Credential Provider 2nd-level cache will refresh twice as frequently as the Credential Provider cache.

 

which mean, by adding ChangeNotificationPeriod parameter the CP will connect to the vault once it will recognize the password had expired.

This is only if the password was changed by the CPM, it won't retrieve a new password if the password was changed manually.

 

View solution in original post

3 REPLIES 3

L1 Bithead

CacheRefreshInterval parameter is the frequency in seconds that the Credential Provider cache is refreshed by the background process.

 

Credential Provider docs contain the following best practice:

This value has an impact on the ChangeNotificationPeriod parameter value defined in the Central Policy Manager, and on the LocalCacheLifespan parameter value defined in Application Server Credential Provider.

We recommend using the following values for these parameters:

  • CacheRefreshInterval= 1500 seconds
  • ChangeNotificationPeriod = 3001 seconds (calculated from (CacheRefreshInterval* 2) + 1). That is, there will be at least 2 refresh cycles before the password is released.
  • LocalCacheLifeSpan = ((CacheRefreshInterval/ 2) - 1) = 749 seconds, that is, the Application Server Credential Provider 2nd-level cache will refresh twice as frequently as the Credential Provider cache.

 

which mean, by adding ChangeNotificationPeriod parameter the CP will connect to the vault once it will recognize the password had expired.

This is only if the password was changed by the CPM, it won't retrieve a new password if the password was changed manually.

 

Thanks for explaining. I would like to clarify one thing again.

 

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?

 

Credential Provider or cache didn't have any intelligent control to do force cache refresh if authentication is failing in application side?

 

 

yes, this is Credential Provider's behavior.

you understood it correctly.

  • 1 accepted solution
  • 1136 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!