@oxyhq/core 2.3.2 → 2.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -729,9 +729,10 @@ export class AuthManager {
729
729
  * Returns the active user on success, or `null` when neither path
730
730
  * restored a session.
731
731
  */
732
- async initialize() {
733
- // 1. Cookie path (preferred).
734
- const cookieResult = await this.restoreFromCookies();
732
+ async initialize(options = {}) {
733
+ // 1. Cookie path (preferred). Forward the optional cold-boot fail-fast
734
+ // timeout so a cross-domain stall cannot hang provider init.
735
+ const cookieResult = await this.restoreFromCookies(options);
735
736
  if (cookieResult.accounts.length > 0) {
736
737
  return this.currentUser;
737
738
  }
@@ -948,7 +949,7 @@ export class AuthManager {
948
949
  * proceed unauthenticated. State is NOT cleared on failure; existing
949
950
  * accounts (if any) remain intact.
950
951
  */
951
- async restoreFromCookies() {
952
+ async restoreFromCookies(options = {}) {
952
953
  // Cross-tab cascade debounce. If we restored within the last
953
954
  // _RESTORE_DEBOUNCE_MS for the currently-active slot, skip the network
954
955
  // round-trip and return the cached registry verbatim. A burst of N
@@ -966,7 +967,9 @@ export class AuthManager {
966
967
  }
967
968
  let snapshot;
968
969
  try {
969
- snapshot = await this.oxyServices.refreshAllSessions();
970
+ // Forward the optional cold-boot fail-fast timeout. Undefined (the warm
971
+ // cross-tab cascade default) preserves the wait-indefinitely behaviour.
972
+ snapshot = await this.oxyServices.refreshAllSessions({ timeout: options.timeout });
970
973
  }
971
974
  catch {
972
975
  return { accounts: [], activeAuthuser: null };
@@ -449,19 +449,42 @@ export function OxyServicesAuthMixin(Base) {
449
449
  * tokens do. Each access token still needs to be planted via
450
450
  * `setTokens(...)` (or per-account in-memory storage) at the consumer.
451
451
  */
452
- async refreshAllSessions() {
452
+ async refreshAllSessions(options = {}) {
453
453
  const url = `${this.getSessionBaseUrl().replace(/\/$/, '')}/auth/refresh-all`;
454
+ // Optional bounded abort (see `RefreshAllOptions.timeout`). A positive
455
+ // timeout arms an `AbortController` that aborts the in-flight request; an
456
+ // abort is treated as "no signed-in accounts on this device" — the same
457
+ // outcome as a 401 — so a cross-domain stall falls through cleanly instead
458
+ // of hanging the cold boot.
459
+ const timeout = typeof options.timeout === 'number' && options.timeout > 0 ? options.timeout : undefined;
460
+ const controller = timeout !== undefined ? new AbortController() : undefined;
461
+ const timeoutId = timeout !== undefined && controller
462
+ ? setTimeout(() => controller.abort(), timeout)
463
+ : undefined;
454
464
  let response;
455
465
  try {
456
466
  response = await fetch(url, {
457
467
  method: 'POST',
458
468
  credentials: 'include',
459
469
  headers: { Accept: 'application/json' },
470
+ signal: controller?.signal,
460
471
  });
461
472
  }
462
473
  catch (error) {
474
+ // A bounded-timeout abort is the "not signed in / cross-domain stall"
475
+ // path, NOT an error. The browser raises a DOMException named
476
+ // 'AbortError' (some runtimes use a generic Error); match on the name so
477
+ // we never throw the timeout into the cold-boot error handler.
478
+ if (error instanceof Error && error.name === 'AbortError') {
479
+ return { accounts: [] };
480
+ }
463
481
  throw this.handleError(error);
464
482
  }
483
+ finally {
484
+ if (timeoutId !== undefined) {
485
+ clearTimeout(timeoutId);
486
+ }
487
+ }
465
488
  if (response.status === 401) {
466
489
  return { accounts: [] };
467
490
  }
@@ -290,6 +290,20 @@ export function OxyServicesFedCMMixin(Base) {
290
290
  // Optional/interactive mediation should only happen when the user clicks "Sign In".
291
291
  let credential = null;
292
292
  const loginHint = this.getStoredLoginHint();
293
+ // Fast-skip: with no stored login hint this browser has never completed a
294
+ // FedCM sign-in for any Oxy account, so silent mediation cannot return a
295
+ // credential — the IdP has nothing to silently re-issue. Doing the full
296
+ // round-trip anyway (mint a nonce via `POST /fedcm/nonce`, then a
297
+ // `navigator.credentials.get` that aborts after `FEDCM_SILENT_TIMEOUT`) is
298
+ // pure latency in the cold-boot critical path. Return `null` immediately so
299
+ // the next cold-boot step (stored-session / iframe / bounce) runs without
300
+ // the wasted nonce mint + abort wait. A genuinely associated browser always
301
+ // has a hint (it is stored only after a real exchange), so this never skips
302
+ // a recoverable session.
303
+ if (!loginHint) {
304
+ debug.log('Silent SSO: No stored login hint — skipping silent mediation (no association on this browser)');
305
+ return null;
306
+ }
293
307
  try {
294
308
  // Server-minted, origin-bound nonce — required for `/fedcm/exchange`
295
309
  // to accept the resulting ID token (anti-replay binding).
@@ -737,12 +751,17 @@ export function OxyServicesFedCMMixin(Base) {
737
751
  _a.DEFAULT_CONFIG_URL = 'https://auth.oxy.so/fedcm.json',
738
752
  _a.FEDCM_TIMEOUT = 15000 // 15 seconds for interactive
739
753
  ,
740
- // Silent mediation runs on page load (e.g. re-signing-in a user whose stored
741
- // session was cleared after a cold-boot token fetch 401'd). The real silent
742
- // round-trip mint nonce navigator.credentials.get /fedcm/exchange was
743
- // measured to take more than 3s for live users, so a 3s budget timed out and
744
- // left them signed out on reload. 10s gives ample margin while staying bounded.
745
- _a.FEDCM_SILENT_TIMEOUT = 10000 // 10 seconds for silent mediation
754
+ // Silent mediation runs on page load as ONE step of the ordered cold-boot
755
+ // sequence (mint nonce navigator.credentials.get /fedcm/exchange). The
756
+ // real round-trip was measured at >3s for live users, so the budget must stay
757
+ // comfortably above 3s. It must ALSO be tight: on a logged-out browser this
758
+ // step never resolves a credential, and every millisecond it spends timing
759
+ // out is pure latency in front of the steps that actually hold the answer
760
+ // (stored-session bearer, the per-apex silent iframe, the /sso bounce). 4s is
761
+ // the floor that preserves the >3s success margin while bounding the dead
762
+ // wait — down from the previous 10s, which alone could account for most of a
763
+ // 20-30s cold-boot stall. Do NOT lower below 4s (it would clip live success).
764
+ _a.FEDCM_SILENT_TIMEOUT = 4000 // 4 seconds for silent mediation
746
765
  ,
747
766
  _a;
748
767
  }
@@ -407,8 +407,24 @@ export function OxyServicesPopupAuthMixin(Base) {
407
407
  cleanup();
408
408
  resolve(session || null);
409
409
  };
410
+ // Fail-fast on a load failure. When the per-apex `/auth/silent` host is
411
+ // unreachable, blocked by CSP `frame-ancestors`/`X-Frame-Options`, or the
412
+ // network drops, the iframe never posts a message — without this handler
413
+ // the silent restore would block for the FULL `timeout` (dead latency in
414
+ // the cold-boot critical path). `onerror`/`onabort` fire on a failed load,
415
+ // so resolve `null` immediately and let the next cold-boot step run. The
416
+ // success path posts a message and is handled above; these only catch the
417
+ // no-message failure modes.
418
+ const failFast = () => {
419
+ cleanup();
420
+ resolve(null);
421
+ };
422
+ iframe.onerror = failFast;
423
+ iframe.onabort = failFast;
410
424
  const cleanup = () => {
411
425
  clearTimeout(timeoutId);
426
+ iframe.onerror = null;
427
+ iframe.onabort = null;
412
428
  window.removeEventListener('message', messageHandler);
413
429
  };
414
430
  window.addEventListener('message', messageHandler);