Admin dashboard shows OS username instead of SSO user in navbar #12
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
The deployer admin pages render the navbar top-right with the deployer process's OS username (label "driver" on the admin VM) instead of the SSO-authenticated user from the X-Hero-User proxy header.
Lives at
crates/hero_tfgrid_deployer_admin/src/routes.rs:50-54:This reads the process env (the systemd / hero_proc user the daemon runs as) rather than the per-request SSO identity that hero_proxy injects on the X-Hero-User header. Should consume the request header so an admin signed in as
mik-tfseesmik-tfin the navbar, notdriver.Acceptance: navbar shows the SSO username after a Forge-OAuth-gated request, falls back to "unknown" for unauthenticated requests (which would have been bounced at the proxy anyway).
Fixed by squash-merge
c649d76ondevelopment.display_username()now readsX-Hero-User(D-31) and falls back to OS env only when the header is absent. Pre-merge gate (fmt + clippy-D warnings+ workspace release build + 26+2 tests) clean. Live verification queued for s170 redeploy on VM0069.