@the-portland-company/shell 0.36.1 → 0.36.3

package/dist/app-chrome.cjs

@@ -2688,6 +2688,7 @@ function watchLogout(onLogout, options = {}) {
   return cleanup;
 }
 var CORE_APP = "vrm";
+var DEFAULT_SIGN_OUT_URL = "/auth/signout";
 var POLITOGY_APPS = {
   vrm: { title: "Politogy VRM", origin: "https://app.politogyvrm.com", storagePrefix: "vrm" },
   contacts: { title: "Contacts", origin: "https://contacts.politogyvrm.com", storagePrefix: "contacts" },
@@ -2715,6 +2716,7 @@ function PolitogyAppFrame({
   linkComponent,
   session,
   onSignOut,
+  signOutUrl = DEFAULT_SIGN_OUT_URL,
   buildMeta,
   data,
   children
@@ -2742,6 +2744,7 @@ function PolitogyAppFrame({
           linkComponent,
           session,
           onSignOut,
+          signOutUrl,
           buildMeta,
           data,
           children
@@ -2757,6 +2760,7 @@ function FrameBody({
   linkComponent,
   session,
   onSignOut,
+  signOutUrl,
   buildMeta,
   data,
   children
@@ -2770,20 +2774,32 @@ function FrameBody({
     signingOutRef.current = true;
     broadcastLogout();
     signOutRef.current();
-  }, []);
+    window.location.assign(signOutUrl);
+  }, [signOutUrl]);
   react.useEffect(
     () => (
-      // A tab that learns of a sign-out elsewhere ends its OWN session properly
-      // (clear cookie, RP-initiated logout at the IdP) rather than merely
-      // navigating away — otherwise its session cookie would outlive the
-      // sign-out and a later visit would silently resume it. No re-broadcast:
-      // the signal that woke us is already on record for everyone.
+      // A tab that learns of a sign-out elsewhere ends its own session for
+      // real, by navigating to the same sign-out route.
+      //
+      // Measured against production before this landed: calling the app's
+      // handler did nothing at all. Apps wire it as
+      // `onSignOut={() => { void signOutAction(); }}` — a server action invoked
+      // outside a transition, so the `redirect()` inside it can never be
+      // applied by the client and the tab just sits there. Building cross-tab
+      // logout on that path made the whole feature a no-op.
+      //
+      // A hard navigation cannot fail that way, and it hands the decision to
+      // the authority rather than guessing: the app's middleware sees a session
+      // whose auth_time predates `politogy_logout_at`, treats it as revoked,
+      // and redirects to Politogy ID. Server-side truth decides; the client
+      // only forces the request. No re-broadcast — the signal that woke us is
+      // already on record for every tab.
       watchLogout(() => {
         if (signingOutRef.current) return;
-        signOutRef.current();
+        window.location.assign(signOutUrl);
       })
     ),
-    []
+    [signOutUrl]
   );
   const core = app === CORE_APP ? data?.core : void 0;
   const identity = useChromeIdentity({ userName: session.userName, email: session.email });