auth-overload — Next.js example

This wrapper reads data from the wrapped site via the BFF data-proxy. There is no sign-in here — public endpoints work as-is, and token-gated ones use your own the wrapped site session (BYOT), harvested by the companion extension or pasted once. The token is vaulted in BFF memory only and never reaches the browser.

Public (no token)

Load players Load sample group

Your data (needs your the wrapped site token) ○ not connected

Easiest: install the companion extension (tools/auth-overload-connector), add the wrapped site in its popup, and sign into the site — it auto-harvests your session and this flips to connected on its own, no paste. Or paste your the wrapped site token (for sport5: open the site → DevTools → Application → Local Storage → copy the loginToken value). Either way it is vaulted in BFF memory only and dies when the session idles / the browser closes. On Connect the BFF probes a token-gated endpoint and only reports connected if the site accepts it — so a wrong/expired token is rejected instead of silently "connecting".

Connect