Skip to content

Mention KEK requirement in production deployment guide #51

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nscuro merged 1 commit into from
May 2, 2026
Merged

Mention KEK requirement in production deployment guide #51

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/guides/administration/deploying-to-production.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,6 +81,13 @@ Manage two classes of secrets separately:
Dependency-Track's runtime secret store. See
[Configuring secret management](configuring-secret-management.md) for the supported backends.

The database secret provider uses envelope encryption: each secret has its own data encryption key (DEK),
and a key encryption key (KEK) protects the DEKs. By default, each instance generates a KEK keyset file
on disk on first startup. All instances in the cluster must share the same KEK, and refuse to start when
they detect a mismatch. Provision a keyset file once and mount it into
every instance, or supply the KEK directly via environment variable. See
[Configuring secret management](configuring-secret-management.md#key-management) for both approaches.

## Configure authentication

Wire Dependency-Track to your identity provider. Local managed users are for evaluation only:
Expand Down