Caching

Imagine that there are 1,000 servers, each of which holds an application that needs a password from the Bravura Privilege vault 1,000 times per second. In total, then, the Bravura Privilege web service would have to provide 1,000,000 passwords per second. This would require a lot of resources and create a single point of failure for the entire infrastructure.

To reduce the workload on the Bravura Privilege service, improve the performance of applications that require credentials from the vault and provide for resiliency in the event that Bravura Privilege is unreachable, credentials fetched from the vault are cached locally, in the creds.ini file.

For large credential files, if the file has previously been downloaded, and it has not been modified based on a file content hash check, the Bravura Privilege service will not attempt to contact the instance to download the file again. If the file does not exist, or does exist but has been modified (fails the hash check), the file will be downloaded again.