@autobusal/providers 1.2.9 → 1.2.11

package/CHANGELOG.md

@@ -4,6 +4,16 @@ All notable changes to `@autobusal/providers` are documented here. This project
 adheres to [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.2.11] - 2026-07-19
+
+### Fixed
+
+- bff-mode 401 no longer logs the user out when the BFF confirms the session is still valid: the apiClient now rejects the failed request (letting react-query retry) instead of tearing down auth. A single account query 401ing (transient race or a flaky upstream call) previously bounced the user to /login even though they were logged in. Bearer mode unchanged.
+## [1.2.10] - 2026-07-19
+
+### Fixed
+
+- Resilient bff-mode auth: on a 401 the apiClient now confirms the session with the BFF (GET /bff/session) before logging out, and transparently retries the request once if still authenticated. Prevents a transient post-login 401 (an account query racing the login cookie hand-off) from bouncing the user straight back to the login page. Bearer mode is unchanged.
 ## [1.2.9] - 2026-07-19
 
 ### Added

package/Queries/apiClient.ts

@@ -39,11 +39,34 @@ if (!isBffMode) {
 
 apiClient.interceptors.response.use(response => (
   response
-), error => {
+), async (error) => {
   if (error.response) {
-    // if we have a 401, we go to the logout page (if not already there)
+    // if we have a 401, the session is gone, so we go to the logout page.
     if (error.response.status === 401 && window.location.pathname !== '/account/logout') {
+      // bff mode: auth is a server-side httpOnly cookie the BFF manages, so a
+      // single request's 401 does NOT reliably mean "logged out" the way a
+      // bearer 401 does - a query that momentarily races the login/cookie
+      // hand-off (or a flaky upstream call) can 401 while the session is still
+      // valid. A blind logout here drops the user straight back to /login. So
+      // confirm with the BFF: only tear the session down if it agrees we are no
+      // longer authenticated; otherwise just reject and let react-query retry -
+      // the user stays logged in. bearer mode has no such ambiguity (the token
+      // is attached synchronously from localStorage) and logs out immediately.
+      if (isBffMode) {
+        try {
+          const { data } = await apiClient.get('/session');
+
+          if (data?.authenticated) {
+            return Promise.reject(error);
+          }
+        } catch {
+          // /session unreachable - fall through to logout.
+        }
+      }
+
       window.location.href = '/account/logout';
+
+      return Promise.reject(error);
     }
 
     // if the user is not valid

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@autobusal/providers",
-  "version": "1.2.9",
+  "version": "1.2.11",
   "author": "Ferjolt Ozuni",
   "type": "module",
   "main": "index.ts"