psa-systems/bunyip
8
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions

fix(web): applications-page launcher points at /dashboard, not / #71

Merged
YousifShkara merged 1 commit from fix/applications-launcher-points-at-dashboard into main 2026-06-06 03:43:42 +02:00
Conversation 0 Commits 1 Files changed 1 +9 -1
YousifShkara commented 2026-06-06 03:43:32 +02:00
Owner
Copy link

The /applications page rendered its launcher cards with href=https://{app_url} (bare host, no path), so clicking through to a child app landed users on the public marketing homepage. The /dashboard page's launcher already used /dashboard; the two were inconsistent.

/dashboard is the right target: the child app's AuthGuard sees a protected route, fires the OIDC code flow against the user's existing OP session, and the SSO bridge silently returns them logged in. With / as the target, the user lands on the marketing page and has to click "Sign in" before the bridge can fire.

Aligned the /applications launcher with /dashboard's.

The `/applications` page rendered its launcher cards with `href=https://{app_url}` (bare host, no path), so clicking through to a child app landed users on the public marketing homepage. The `/dashboard` page's launcher already used `/dashboard`; the two were inconsistent. `/dashboard` is the right target: the child app's AuthGuard sees a protected route, fires the OIDC code flow against the user's existing OP session, and the SSO bridge silently returns them logged in. With `/` as the target, the user lands on the marketing page and has to click "Sign in" before the bridge can fire. Aligned the `/applications` launcher with `/dashboard`'s.
fix(web): applications-page launcher points at /dashboard, not /
All checks were successful
Create release / Create release from merged PR (pull_request) Has been skipped
Details
Check / fmt / clippy / build / test (pull_request) Successful in 1m7s
Details
a7c2422e99 
The `/applications` page rendered its launcher cards with `href=https://{app_url}` (bare host, no path), so clicking through to a child app landed users on the public marketing homepage. The `/dashboard` page's launcher already used `/dashboard`; the two were inconsistent.

`/dashboard` is the right target: the child app's AuthGuard sees a protected route, fires the OIDC code flow against the user's existing OP session, and the SSO bridge silently returns them logged in. With `/` as the target, the user lands on the marketing page and has to click "Sign in" before the bridge can fire.

Aligned the `/applications` launcher with `/dashboard`'s.
YousifShkara deleted branch fix/applications-launcher-points-at-dashboard 2026-06-06 03:43:42 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
YousifShkara
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
psa-systems/bunyip!71
No description provided.