Admin UI: Cockpit URL column renders bare hostname, should append /hero_cockpit/web/ #19

Open
opened 2026-05-28 05:22:02 +00:00 by mik-tf · 0 comments
Owner

The VMs table on the deployer admin UI's user-detail page renders the per-tester URL as https://{tester}.gent01.qa.grid.tf (bare hostname). Clicking it lands on hero_proxy's own service-discovery dashboard, NOT on cockpit, which is confusing for both operator and tester (looks like nothing is installed). The actual cockpit entry point is https://{tester}.gent01.qa.grid.tf/hero_cockpit/web/, which 302s anonymous traffic through Forge SSO and lands the tester on the cockpit dashboard. Proposal: in the admin UI's user_detail Askama template, change the column's anchor href and displayed text from {{ vm.webgateway_url }} to {{ vm.webgateway_url }}/hero_cockpit/web/. Same fix applies to the post-Provision success alert's Cockpit URL link. The Hero Proxy service-discovery page that the bare URL lands on today is also a separate UX gap (information disclosure on a publicly served URL), but the immediate fix is just the path-suffix on the displayed link. Surfaced live on the s172d operator walk by a tester clicking the URL and seeing the Hero Proxy services table instead of the cockpit they expected.

The VMs table on the deployer admin UI's user-detail page renders the per-tester URL as `https://{tester}.gent01.qa.grid.tf` (bare hostname). Clicking it lands on hero_proxy's own service-discovery dashboard, NOT on cockpit, which is confusing for both operator and tester (looks like nothing is installed). The actual cockpit entry point is `https://{tester}.gent01.qa.grid.tf/hero_cockpit/web/`, which 302s anonymous traffic through Forge SSO and lands the tester on the cockpit dashboard. Proposal: in the admin UI's user_detail Askama template, change the column's anchor href and displayed text from `{{ vm.webgateway_url }}` to `{{ vm.webgateway_url }}/hero_cockpit/web/`. Same fix applies to the post-Provision success alert's Cockpit URL link. The Hero Proxy service-discovery page that the bare URL lands on today is also a separate UX gap (information disclosure on a publicly served URL), but the immediate fix is just the path-suffix on the displayed link. Surfaced live on the s172d operator walk by a tester clicking the URL and seeing the Hero Proxy services table instead of the cockpit they expected.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/hero_os_tfgrid_deployer#19
No description provided.