Skip to content
Integrations
Operations
Secret Synchronization

Secret Synchronization

Keep Britive as the single source of truth for credential lifecycle while downstream systems stay in sync. Broker scripts handle both directions:

  • Synchronization — on checkout, the broker writes the current Britive-managed value to an external store, so applications that can’t integrate with Britive directly still read the latest value from their native store.
  • Rotation — on a schedule or on demand, the broker replaces the credential at its source (an AWS Secrets Manager secret, an Active Directory account) and propagates the new value to whatever consumes it.

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.

  • Rotate AWS Secrets Manager Secrets

    Use the Britive Access Broker to rotate a value stored in AWS Secrets Manager on a schedule — either the secret alone, or the account behind it first and the secret second.

  • Rotate Active Directory Accounts

    Use the Britive Access Broker to reset an Active Directory account password over LDAPS on a schedule, and propagate the new value to AWS Secrets Manager or a Windows service.

Last updated on