feat(harmony_secret): SSO auth hardening — silent refresh, renewal, namespacing #302
Reference in New Issue
Block a user
No description provided.
Delete Branch "pr/harmony-secret-auth"
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?
Summary
Hardens the OpenBao/Zitadel auth path so SSO-authenticated sessions survive
process restarts and overnight gaps without re-triggering the browser device
flow. Internal behavior only — public API is unchanged, so it compiles against
current
master.Changes
OpenBao token) with no device-flow prompt; clearer device-code error surfacing.
renew-selfon the cached OpenBao token so its lease rolls forward to therole's max_ttl instead of expiring at the initial TTL.
(falls back to the printed URL on headless/SSH hosts).
sso_url + client_id(was one shared file that asecond instance would silently overwrite).
LocalFileSecretStorenested per namespace.auth/token/lookup-self(granted by the defaultpolicy) instead of
lookup(needs sudo) — fixes every cached token beingtreated as invalid and forcing a needless re-auth.
HARMONY_SECRETS_URLvar andOidcSession::is_openbao_token_expired.Context
PR 1 of 4 splitting
feat/unified-config-and-secrets. Independent of the otherPRs — merge in any order.
Verification
cargo check --workspace --all-targets --all-features,cargo fmt --check,cargo test -p harmony_secret(11 passing), clippy clean.lgtm, went quickly over it, I'll need to get a better feel once I start using it.