trails/apps/journal/app/lib/jwt.server.ts
Ullrich Schäfer b4c64a40e7
fix(journal): single-use JWT enforcement for route callback tokens (#2 Phase B)
After Phase A (#442) moved the journal callback token off the browser,
the token was still replayable on the wire until \`exp\` (7 days). This
PR makes each token strictly single-use.

Changes:

- **\`journal.consumed_jwt_jti\` table** — \`jti TEXT PRIMARY KEY,
  consumed_at TIMESTAMPTZ, expires_at TIMESTAMPTZ\`. Picked up by
  drizzle-kit push on deploy.
- **\`createRouteToken\` now sets a \`jti\` claim** (\`randomUUID()\`).
- **\`verifyRouteToken\` atomically consumes the jti** via
  \`INSERT … ON CONFLICT DO NOTHING RETURNING jti\`. Postgres
  serializes the insert, so exactly one concurrent caller wins; the
  rest see an empty result and throw \`TokenAlreadyConsumedError\`.
  Tokens without a \`jti\` claim (i.e. minted before this PR) are
  also rejected — the right call: any in-flight legacy token sitting
  in a planner session is replayable, and we'd rather fail-loud than
  silently grandfather them in.
- **\`consumed-jti-sweep\` job** — daily 03:45 UTC cron that
  \`DELETE WHERE expires_at < now()\`. Keeps the table tiny; offset
  from the other purge jobs to spread load.
- **e2e replay test** — \`integration.test.ts\` now exercises a
  same-token double-submit and asserts the second returns 401 with
  \`/consumed|already/i\`.

UX implication worth flagging: a user who clicks \"Save\" twice (or whose
network retries a failed POST) sees an error on the second attempt.
They go back to the journal for a fresh \"Edit in Planner\" link.

Full repo: pnpm typecheck / lint / test all green (177 + 31 integration).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-26 00:38:08 +02:00

74 lines
2.3 KiB
TypeScript

import { SignJWT, jwtVerify } from "jose";
import { randomUUID } from "node:crypto";
import { getOrigin, requireSecret } from "./config.server.ts";
import { getDb } from "./db.ts";
import { consumedJwtJti } from "@trails-cool/db/schema/journal";
const JWT_SECRET = new TextEncoder().encode(
requireSecret("JWT_SECRET", "dev-jwt-secret-change-in-production"),
);
const ISSUER = getOrigin();
export async function createRouteToken(routeId: string, permissions: string[] = ["read", "write"]): Promise<string> {
return new SignJWT({ route_id: routeId, permissions })
.setProtectedHeader({ alg: "HS256" })
.setIssuer(ISSUER)
.setExpirationTime("7d")
.setIssuedAt()
.setJti(randomUUID())
.sign(JWT_SECRET);
}
export class TokenAlreadyConsumedError extends Error {
constructor() {
super("Token already consumed");
this.name = "TokenAlreadyConsumedError";
}
}
/**
* Verify a route token AND atomically consume it. Subsequent calls
* with the same token throw `TokenAlreadyConsumedError`.
*
* The consume step is `INSERT … ON CONFLICT DO NOTHING RETURNING jti`.
* Postgres serializes the insert against concurrent attempts, so
* exactly one caller observes the returned row — the rest see an
* empty result and reject.
*
* Tokens minted before this PR (no `jti` claim) are rejected outright,
* which is the right behavior: pre-existing tokens are already in
* planner-session DB rows and would be replayable if accepted. The
* user re-saves by going back to the journal for a fresh token.
*/
export async function verifyRouteToken(token: string): Promise<{ routeId: string; permissions: string[] }> {
const { payload } = await jwtVerify(token, JWT_SECRET, {
issuer: ISSUER,
});
if (typeof payload.jti !== "string" || !payload.jti) {
throw new TokenAlreadyConsumedError();
}
if (typeof payload.exp !== "number") {
throw new TokenAlreadyConsumedError();
}
const db = getDb();
const inserted = await db
.insert(consumedJwtJti)
.values({
jti: payload.jti,
expiresAt: new Date(payload.exp * 1000),
})
.onConflictDoNothing()
.returning({ jti: consumedJwtJti.jti });
if (inserted.length === 0) {
throw new TokenAlreadyConsumedError();
}
return {
routeId: payload.route_id as string,
permissions: payload.permissions as string[],
};
}