CacheRefreshInterval not working as expected?

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

CacheRefreshInterval not working as expected?

L4 Transporter

We have a shell script fetching credentials from vault via AIM CP. The script is scheduled to run every 15 minutes. What we are observing is, that the AppProviderUser(Prov_HostName) fetches password from the vault and not from cache whenever the script is run i.e. every 15 minutes. Password in the vault is not changed and it's the same. CacheRefreshInterval in main_appprovider.conf.X has been set to 180 minutes. CacheLevel is set to Persistent. Any thoughts? Thank you.

10 REPLIES 10

L7 Applicator

How sure are you that password is fetched from vault and not from cache? I mean how are you verifying if the password was fetched from cache or vault.

And cache refresh interval is in seconds and if you need to refresh every 15 mins then the value has to be set to 900.

L4 Transporter

I can see in "activities" tab from PVWA that AppProviderUser (Prov_HostName) is retrieving the password whenever the script is run. CacheRefreshInterval is set in seconds and much higher as we know the password change frequency. I believe by default "CredentialProvider" is not configured/set to read the credentials from Cache; cache will come into play only if your vault connectivity is broken from CP machine. Not sure how to make this work.

By default the cache type is set to persistent. I have not tried but you could give a try

Change the ip of the vault in the vault.ini file basically disconnecting the connection to the vault (do not refresh cache manually - wait for the automated refresh to happen)and see how it works now

L4 Transporter

OK, the issue here is not to reading from cache when the vault is not reachable. My question is can we make CredentialProvider to read from cache even when the vault is up. I do not want CP to fetch credentials every time from the vault whenever the script is run. Cache type is set to persistent.

L4 Transporter

AIM requests are always done on the cache.

The provider goes to the vault every set amount to make sure the password is correct and fetch the new password if not.

L4 Transporter

In that case "provider" is definitely not working as expected. For every credential request it hits the main vault and not at specific interval as mentioned in CacheRefreshInterval. Have opened a case with CyberArk. Thank you.

L4 Transporter

@Vishwanath Babali​ Did you find a solution to this ? We seem to be facing the same issue currently

L2 Linker

​Hi, Do you have solution? Does Any one find

Nope.

Nope.

  • 967 Views
  • 10 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!