# Server-custody template. Do not place JWTs, passphrases or private-key data here. # R3 multi-vault mode: set this one root route and keep every profile in a # separate private env file described by passbolt-profile-registry.example.json. # When set, every bound principal must resolve through the registry. PASSBOLT_PROFILE_REGISTRY_FILE= # Legacy/default single-vault mode remains compatible when the registry path is empty. PASSBOLT_BASE_URL=https://passbolt.example PASSBOLT_SERVICE_USER_ID= PASSBOLT_SERVICE_USERNAME= PASSBOLT_USER_FINGERPRINT=<40-hex-service-key-fingerprint> PASSBOLT_SERVER_FINGERPRINT=<40-hex-pinned-server-fingerprint> PASSBOLT_METADATA_FINGERPRINTS= # All paths are server/container paths. Token-state and sealed directories must # be writable by uid 10001; primary GPG custody and sink registry remain read-only. PASSBOLT_TOKEN_STATE_FILE=/run/state/passbolt/tokens.json PASSBOLT_GPG_HOME=/run/secrets/passbolt/gnupg PASSBOLT_PASSPHRASE_FILE=/run/secrets/passbolt/passphrase PASSBOLT_SEALED_REF_DIR=/run/secrets/passbolt/sealed PASSBOLT_SINK_CONFIG_FILE=/run/secrets/passbolt/sinks.json # Optional exact resource-host>target-host relations, comma-separated. PASSBOLT_DOMAIN_ALLOWLIST=