Files
harmony/fleet/harmony-fleet-auth
Sylvain Tremblay 4ff7dcc9dd Merge fleet device-secret-access (JWT-bearer OpenBao auth) into master
Consolidates the #319 (docs/ADR-025) + #316 (auth next-url redirect) +
#332 (JWT-bearer OpenBao auth, entity-by-policy device secret access)
stack onto current master.

Conflict resolutions:
- harmony_zitadel_auth config: keep master's typed ConfigClient approach
  (OperatorCookieKey + ZitadelAuthConfig via Config derive); drop the
  branch's superseded config_from_env/cookie_key_from_env/*_ENV path.
  Operator already loads via ConfigClient on master.
- harmony_zitadel_auth/lib.rs: master's config exports + branch's
  jwt_bearer exports (MachineKeyFile, ZitadelJwtBearer).
- fleet-auth/lib.rs: keep master's OPERATOR_CREDENTIALS_ENV_VAR export.
- operator/main.rs: keep master's in-process spawn_dashboard + branch's
  openbao secret-access wiring and extended run() signature; drop the
  removed device_status task.
- dev.sh: master's HARMONY_CONFIG_* typed env vars.

#316's next-url-redirect feature (login.rs valid_next/RawAuthCallbackQuery)
is preserved unchanged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-11 13:21:20 -04:00
..
2026-06-02 12:46:42 -04:00
2026-06-02 12:46:42 -04:00