🍪 Xpand StubTex Keeper
Chrome extension that keeps your StubTex session alive and auto-syncs the cookie to Xpand. Install once, forget about it.
Install
- Download the extension files. Right-click each file below → Save link as… into a new folder on your machine (e.g.
~/xpand-stubtex-keeper/):
- Open Chrome →
chrome://extensions
- Top-right toggle: enable Developer mode.
- Click Load unpacked → pick the folder where you saved the files.
- The extension appears in your toolbar. Click it → ⚙️ Settings.
- Paste your Xpand URL (e.g.
https://xpand-production.up.railway.app) and the extension token from Xpand → Admin Panel → 🍪 StubTex Cookie → Generate new token.
- Click Test connection. Should show ✅ Connection OK.
- Click Save. Done.
What it does
- Auto-sync: every time your browser's stubtex cookie changes (login refresh, Azure SSO renewal, etc.), the new cookie is POSTed to Xpand within 3 seconds.
- Keep-alive: every 5 minutes, the extension fires a GET to
stubtex.stubcorp.cloud/sites/intranet/index_new.cfm from your browser. This resets F5's idle timer and keeps the session valid.
- Status panel: click the extension icon to see last sync, last keep-alive, and any errors.
Privacy: the extension only reads cookies for stubcorp.cloud and only sends them to the Xpand URL you configure. Nothing leaves your machine to any third party.
Troubleshooting
- "No cookies for stubcorp.cloud" → you're not logged into StubTex. Log in at
https://stubtex.stubcorp.cloud/ first, then click Sync now in the extension popup.
- "401: invalid token" → regenerate the token in Xpand admin panel and re-paste in the extension's Settings.
- "401: no extension token configured" → admin hasn't generated a token yet. Tell them to click Generate new token in the Xpand admin panel.
- Cookie expires anyway → check the extension popup for last keep-alive status. If it's failing, your stubtex session might be genuinely dead (Azure SSO max session reached) — log back into stubtex in your browser to re-issue.