This release adds 3 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+6 more
Affected surfaces
Summary
AI summaryUpdates ✅ Tests, 🐛 Fixes, and 🔒 Hardening across a mixed release.
Full changelog
v1.8.3 — Login gate reliability fixes
Fixes a redirect loop that could leave users stuck on the login page after entering correct credentials when the login gate is enabled, plus hardens session-cookie handling for HTTP/LAN self-hosted deployments.
🐛 Fixes
- Login redirect loop when the login gate is enabled. After signing in with valid credentials the API returned
success, but you were bounced straight back to/login. The frontend proxy verified the session JWT locally, which silently failed whenever the frontend process didn't share the backend'sSYNAPSE_JWT_SECRET(they run as separate processes). Session validation is now delegated to the backend — the single owner of the secret — via/api/auth/status, so a missing or mismatched frontend secret can no longer cause the loop. The local JWT check is kept as a zero-latency fast path when the secret is present, and fail-open on an unreachable backend is preserved. - Session cookie dropped on plain-HTTP / LAN installs. The
synapse_sessioncookie'sSecureflag was tied toNODE_ENV=production, so self-hosted deployments served over plain HTTP couldn't store it — another route into the login loop. It now keys off the actual request protocol and honorsx-forwarded-protobehind a TLS-terminating reverse proxy.
🔒 Hardening
/api/v2/now bypasses the login gate in the frontend proxy, consistent with/api/v1/and the backendInternalTokenMiddleware(versioned APIs authenticate via Bearer API key). No behavior change in practice — defense-in-depth.- The login page runs
router.refresh()after redirecting, so the RSC router cache re-fetches with the freshly-set session cookie present.
✅ Tests
- New
backend/tests/api_v1/test_auth_gate.pycovering/api/auth/statusauthentication reporting: valid token, missing token, malformed token, mismatched-secret token, and login-disabled.
⬆️ Upgrading
This release includes frontend changes, so the frontend must be rebuilt/re-bundled.
- pip:
pip install --upgrade synapse-orch-ai, thensynapse start. - terminal:
synapse upgrade, thensynapse start - From source:
cd frontend && npm run build, thensynapse stop && synapse start.
No settings or data migration required, and existing sessions stay valid.
Full Changelog: https://github.com/synapseorch-ai/synapse-ai/compare/v1.8.2...v1.8.3
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About synapseorch-ai/synapse-ai](https:
All releases →Related context
Related tools
Beta — feedback welcome: [email protected]