Need explanation of "Vault Cache Mode" setting for Keeper Integration

From trial and error, my best guess is that this setting controls an option for RDM to keep a local cache of everything in your Keeper vault.

With this option set to Disabled, I am prompted for Keeper authentication on every secret use. Users with a master password can store it in My Account Settings, but SSO users cannot avoid being prompted on every secret use - it does not appear that RDM caches an authorization token for Keeper (it would be great if this was an option).

"Always synchronize" appears to prompt an SSO user for auth once after launching RDM at the first use of a Keeper secret. After that first use, no subsequent auth is required and all vault secrets are accessible from within RDM for the duration of the session. I'm guessing this is because RDM used that first authentication to grab a copy of every secret?

And so I'd guess that "Synchronize once" is essentially the same as "Always synchronize" except that RDM won't prompt for Keeper auth for a fresh re-sync on every launch of RDM. But I haven't bothered to test that yet.

Hoping someone can confirm or correct this assessment. Thanks!

Hello JustinH,

From what I can gather, the option is meant to cache your Keeper vault so as to not have to load the entries contained in Keeper every time in RDM for future uses. This will make it so that only the first use of Keeper after opening RDM has a delay.

I believe "Always Synchronize" will make it so that the cache is refreshed every time Keeper is used, so that new credentials in Keeper can be added to the cache quickly.

"Synchronize once" will cache the entries once after opening Keeper in RDM, and then won't synchronize again until after RDM has been closed and relaunched.

"Disabled" will evidentally make it so that no caching is performed for your Keeper vault in RDM.

Best regards,