fix(auth): logout lands on this SPA's origin home, not Bunyip's login #81
No reviewers
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
psa-systems/mokosh-apps!81
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/logout-lands-on-mokosh-home"
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?
PR #82 wired the UserMenu's Logout to bunyip-api
GET /v1/auth/logout?url=<x>with the hub login as theurltarget, so users were redirected to bunyip-web/loginafter signing out. The companion bunyip change (fix/logout-honors-final-url, PR pending) replaces the old "bounce through /login" semantics with a direct 302 tourl. With that landed, the same logout button now needs to pointurlat the SPA's own origin root so the user ends up on the mokosh public landing page, signed out, instead of on the Bunyip login form.Resolves the
urlat click time fromwindow.location.originso the same build works against any deployment hostname (msp.a8n.systems, msp.psa.systems, self-hosted): no hardcoded host, no env coupling. Falls back tocfg.hub_url("/")when the browser origin is somehow unavailable (server-side render path, mostly unreachable inwebbuilds).Depends on the bunyip change shipping first; with the old bunyip behaviour the SPA would now redirect to
/login?redirect=https://msp.<tld>/, which is a worse failure mode than the previous "lands on bunyip /login" outcome. Merge order: bunyip first, then this.