You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 16c0f43
Browse filesBrowse the repository at this point in the historyBrowse files
fix(webapp): seal public token subjects with their own secret
Add PUBLIC_TOKEN_SUBJECT_SECRET, a dedicated key for the encrypted
environment id in public access tokens. When it is unset the webapp
keeps using ENCRYPTION_KEY, so self-hosted instances need no change.
Mono-RevId: 18984b40421bf99ba9a0f7201ea1e89076de1efb
|`MANAGED_WORKER_SECRET`| Yes | — | Managed worker secret. Must be set and match supervisor. Run: `openssl rand -hex 32`|
15
+
|`PUBLIC_TOKEN_SUBJECT_SECRET`| No |`ENCRYPTION_KEY`| Key that encrypts the environment id inside public access tokens. Set it to keep this separate from the secret store key. Run: `openssl rand -hex 32`|
16
+
|`PUBLIC_TOKEN_SEALED_SUBJECT_ENABLED`| No | false | Encrypt the environment id inside newly minted public access tokens. Turn on only once every webapp instance runs a version that can read them. |
15
17
|`ALLOW_INSECURE_DEFAULT_SECRETS`| No | false | Boot even if a secret is still a known-insecure published default. Temporary escape hatch for values you can't safely rotate yet (see [Secrets](/self-hosting/kubernetes#secrets)). |
0 commit comments