Auth middleware completely disabled — zero auth protection #17

Closed
opened 2026-05-09 00:32:18 +00:00 by Mark · 1 comment
Owner

middleware.ts always uses noOpHandler, bypassing Clerk auth. All routes unprotected.

middleware.ts always uses noOpHandler, bypassing Clerk auth. All routes unprotected.
Mark 2026-07-31 07:48:22 +00:00
Author
Owner

Overseer closeout (phase: Implement, state: stuck → resolved): the fix for this issue was already implemented and committed as e78d00d ("fix: enforce Clerk auth in middleware unconditionally (refs #17)"), which is an ancestor of HEAD and present on origin/main. Verified in the current tree: src/middleware.ts has no NO_AUTH short-circuit and always invokes clerkMiddlewareHandler with auth().protect() on /app/* routes; src/middleware.test.ts has 5 passing tests (incl. no-short-circuit with NO_AUTH=true); npm run typecheck exits 0; npm run lint exits 0 (only pre-existing warnings in unrelated files). The implement phase correctly concluded no new commit was needed; the runner flagged stuck on idle. Closing as done.

Overseer closeout (phase: Implement, state: stuck → resolved): the fix for this issue was already implemented and committed as `e78d00d` ("fix: enforce Clerk auth in middleware unconditionally (refs #17)"), which is an ancestor of HEAD and present on origin/main. Verified in the current tree: src/middleware.ts has no NO_AUTH short-circuit and always invokes clerkMiddlewareHandler with auth().protect() on /app/* routes; src/middleware.test.ts has 5 passing tests (incl. no-short-circuit with NO_AUTH=true); npm run typecheck exits 0; npm run lint exits 0 (only pre-existing warnings in unrelated files). The implement phase correctly concluded no new commit was needed; the runner flagged stuck on idle. Closing as done.
Sign in to join this conversation.
No description provided.