Internal API hardening — fail-closed token, session ownership, expiring raster URLs
OrionAI 2.45.0Released 9 November 2026
The multitenancy audit's backend fixes (B1, B2, B5): Core's internal gate now fails closed instead of silently opening when the token env is missing, session reads and provenance are bound to the caller's declared user, and raster tile URLs carry a dedicated secret, an expiry and the owning user instead of a static fallback key.
Changes since 2.44.2.
#Security
- Fail-closed internal gate. When
ORION_INTERNAL_TOKENis unset, Core's internal endpoints now refuse with 503 (misconfigured) instead of silently serving to anyone; a wrong token still gets 403. - Session ownership. Reading a session, its result GeoJSON, updating its status and writing/reading provenance now require the
X-Orion-Userheader to match the row's owner (404 otherwise, the platform's not-yours convention). Provenance rows record their writer; the web app now sends the signed-in user on every Core call. - Expiring raster URLs. Raster COG URLs are signed with a dedicated secret (or the internal token until one is rotated in), bound to the owning user, and expire after an hour — refreshed on every read, so a leaked tile URL stops working instead of living forever. The old static
"orion-dev"fallback secret is gone.
#Notes
- Set
ORION_RASTER_SECRETin the host.envto rotate independently of the shared internal token (fallback:ORION_INTERNAL_TOKEN).