chore(secrets): rotated Vaultwarden and Authelia secrets (2026-10-13) #125
Loading…
Reference in a new issue
No description provided.
Delete branch "jfraeys/chore/rotated-secrets-2026-10-13"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Re-applies the secrets rotated on the operator machine on 2026-10-13 onto main's vault (encrypted file only; no values appear here).
Keys changed (names only): VAULTWARDEN_ADMIN_TOKEN, VAULTWARDEN_OIDC_CLIENT_SECRET, AUTHELIA_OIDC_VAULTWARDEN_CLIENT_SECRET, AUTHELIA_OIDC_FORGEJO_CLIENT_SECRET, AUTHELIA_OIDC_GRAFANA_CLIENT_SECRET, AUTHELIA_OIDC_HMAC_SECRET, AUTHELIA_SESSION_SECRET, AUTHELIA_IDENTITY_VALIDATION_RESET_PASSWORD_JWT_SECRET.
Not changed: AUTHELIA_OIDC_PRIVATE_KEY_PEM and CI_EPHEMERAL_ANSIBLE_SSH_KEY keep main's values (#52). The PEM was also rotated locally on a checkout that predated #52; main's is the deployed one, so it wins.
Checked: same 108 keys as main; exactly the 8 above differ; each equals the operator-machine rotation.
Not deployed. Merging does not change any running service. Before deploying: the three OIDC client secrets (Vaultwarden, Forgejo, Grafana) must be deployed together with Authelia or SSO logins to that service break; the session/HMAC change logs everyone out. Use the deploy commands rotate-secret.sh printed per service. Does not touch a staging path, so no staging run starts.
🤖 Generated with Claude Code