v0.31.11

Security

A default self-hosted install is not affected and nothing changes for it. This matters if you run the gateway outside this image, for more than one organization, behind a console that is not in self-hosted mode.

• The gateway no longer trusts identity headers by default. The gateway's identity mode decides how it treats a request that carries the internal key beside a sign-in token. Left unset, it used to keep the organization and member headers the request asserted even when the token did not verify, so behind a console that adds the internal key to any request with a sign-in token, a made-up token could act as any organization. Unset, or set to anything but off or observe, the mode is now enforce: the identity comes from the verified token, and a token that does not verify is refused. The image's entrypoint still sets off, since its console pins the one organization itself. The self-hosting guide says what the default is outside the image.

Checked

On the release candidate, a self-hosted install: the gateway runs with the mode off as before, every console page loads, Claude Code tasks complete with usage, and all plugin checks pass on Claude Code, Codex and Pi. The new default and the refusal of an unverifiable token are pinned by tests.

Reported privately by @mikannse (GHSA-qrr8-m92f-7vfp). Thank you.

docker run -d -p 3000:3000 -v hr-data:/data harnessrouter/harnessrouter:0.31.11

Full Changelog: v0.31.10...v0.31.11