docs(deploy): vd03 API-key pepper moved into the service environment (#171)
Record of the 2026-11-12 config-only change on wonder-app-vd03: MxGateway__ApiKeyPepper added to the MxAccessGw AppEnvironmentExtra block (same value, sha256 prefix match), removed from Server\appsettings.json; authenticated round-trip with a pre-change key, ScadaBridge MxGateway link unchanged. Runbook and configuration doc now say where the pepper lives on each wonder box. Claude-Session: https://claude.ai/code/session_01GT67ACmpMR7b9LGRPLijMi
This commit is contained in:
@@ -375,7 +375,8 @@ nssm set MxAccessGw AppEnvironmentExtra ZB_SECRETS_MASTER_KEY=<base64-32-bytes>
|
||||
|
||||
`AppEnvironmentExtra` is the same newline-separated `KEY=VALUE` block that
|
||||
already carries `ASPNETCORE_ENVIRONMENT`, `MxGateway__Worker__ExecutablePath`,
|
||||
and the API-key pepper (see the `wonder-app-vd03`/`windev` deploy notes) —
|
||||
and the API-key pepper (`MxGateway__ApiKeyPepper`; on `wonder-app-vd03` only since
|
||||
2026-11-12, see `docs/deploy/2026-11-12-vd03-pepper-to-service-env.md`) —
|
||||
`nssm set ... AppEnvironmentExtra` **replaces the entire block**, so always
|
||||
`get` first and re-include every existing entry alongside the new key, then
|
||||
restart the service for it to take effect.
|
||||
|
||||
Reference in New Issue
Block a user