Secret Synchronization
Keep Britive Secrets Vault as the single source of truth for credential lifecycle while downstream stores stay in sync. On checkout, the Britive Access Broker runs a script that writes the current secret value to an external store — AWS Secrets Manager, Azure Key Vault, HashiCorp Vault, or GCP Secret Manager — so applications that can’t integrate with Britive directly still read the latest Britive-managed value from their native store.
In This Section
- Getting Started
Configure the Britive Access Broker to push Britive-managed secret values to AWS Secrets Manager, Azure Key Vault, HashiCorp Vault, or GCP Secret Manager on checkout.
Last updated on