feat(auth): finish Turnstile coverage across every auth entry point

Turnstile protected sign-in, sign-up and password-reset, but three gaps
remained:

- updatePassword had no verification and its page had no widget, so the
  final step of the reset flow was unprotected. The reset token is now
  carried through the failure redirect so a failed challenge doesn't
  strand the user on a form whose emailed link can't be replayed.

- /api/auth/[...all] exposed better-auth's handler directly, accepting
  unlimited credential guesses and email sends with no bot protection --
  a full bypass of the page-level checks. Credential-bearing POSTs now
  require a verified token. The gate lives in the route handler, so the
  server actions (which call auth.api.* in-process) are unaffected. GET
  is untouched for OAuth callbacks and verify-email links, and
  /sign-in/social stays open since it only redirects to the provider.

- Turnstile tokens expire after ~5 minutes and the widget never reset,
  so a form left open submitted a stale token and failed with "complete
  the verification challenge" despite the challenge visibly passing.

Verified with Cloudflare's test keys: all four auth forms block an
invalid token, pass a valid one through to real auth logic, and the API
gate returns 403 without a token and 401 with one.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Leon Serfaty
2026-09-05 16:26:16 -04:00
co-authored by Claude Opus 5
parent 595a5e3e04
commit 8f90347659
4 changed files with 103 additions and 2 deletions
+12 -1
View File
@@ -131,15 +131,26 @@ export async function signOut() {
export async function updatePassword(formData: FormData) {
const password = formData.get("password") as string
const token = formData.get("token") as string
const captchaToken = formData.get("cf-turnstile-response") as string | null
if (!token) {
redirect(`/update-password?error=${encodeURIComponent("Reset link is invalid or expired.")}`)
}
const h = await headers()
// Same bot protection as the other credential forms. The reset token is
// carried through so a failed challenge doesn't strand the user on a form
// whose link can't be replayed.
if (!(await verifyTurnstile(captchaToken, h.get("x-forwarded-for")))) {
redirect(
`/update-password?error=${encodeURIComponent(CAPTCHA_ERROR)}&token=${encodeURIComponent(token)}`
)
}
try {
await auth.api.resetPassword({
body: { newPassword: password, token },
headers: await headers(),
headers: h,
})
} catch (e) {
const msg = e instanceof APIError ? e.message : "Could not update password"