Skip to main content

Configuration

Docker deployments use three configuration layers.

LayerLocationPurposeChanged via
Bootstrap.envSettings required before unsealEdit .env, then restart
Public runtime configHSM-stored configRuntime settings that are not secretsKey Manager
Runtime secretsHSM-stored secretsTokens, passwords, and client secretsKey Manager

1. Bootstrap

Use .env only for pre-unseal settings.

Common variables

VariablePurpose
TSB_API_URLTSB API base URL
TSB_ACCESS_TOKENTSB bearer token
TSB_VERIFY_TLSTSB TLS verification
TSB_TIMEOUTTSB request timeout
AUTH_PROVIDERBootstrap authentication mode
APP_SKENC_PATHsk-app.enc path inside the container
SEAL_ENVELOPE_PATHseal.enc path inside the container
SEAL_WRAPPER_KEY_LABELHSM wrapping key label
KMS_AUTO_INITAuto-initialize on first start
*_HTTP_PORTHost port mapping
LOG_LEVELPre-unseal log level
CORS_ALLOWED_ORIGINSPre-unseal CORS allowlist
IMAGE_REGISTRYImage registry
IMAGE_TAGImage tag

On-prem TSB

On-prem deployments also write:

  • TSB_HSM_HOST
  • TSB_HSM_PORT
  • TSB_HSM_USERNAME
  • TSB_HSM_SETUP_PASSWORD
  • TSB_HSM_PROXY_USERNAME
  • TSB_HSM_PROXY_PASSWORD
  • TSB_HSM_ENCRYPTION_PASSWORD

2. Public Runtime Config

Configure these in the Key Manager after unseal:

  • Session and JWT settings
  • Login and MFA settings
  • OAuth provider parameters
  • SMTP and notification settings
  • Syslog settings
  • Audit log settings
  • Module configuration such as KMIP or MCP-backed features

3. Runtime Secrets

warning

Store secret values in the Key Manager, not in .env.

Examples secrets:

  • Rotated TSB_ACCESS_TOKEN
  • OAuth client secrets
  • SMTP password
  • Audit signing password
  • API keys used by enabled modules
Get started withCloudHSM for free.
Other questions?Ask Sales.
Feedback
Need help?