TypeScript 上没有 NextAuth 的 Google OAuth 2.0:PKCE、状态、随机数和安全下一步
我们正在构建什么
在没有 NextAuth 的情况下通过 Google 登录:Next.js 15 中的两个路由处理程序,使用 PKCE 的授权代码。 Start 将 state、nonce 和 code_verifier 放入 httpOnly cookie 中;回调检查 state,将 code 更改为令牌,检查 id_token 并生成安全的 next。
通用模块
// lib/oauth/google.ts
import { createHash, randomBytes, timingSafeEqual } from "node:crypto";
import { createRemoteJWKSet, jwtVerify } from "jose";
export const AUTH_URL = "https://accounts.google.com/o/oauth2/v2/auth";
export const TOKEN_URL = "https://oauth2.googleapis.com/token";
const JWKS = createRemoteJWKSet(new URL("https://www.googleapis.com/oauth2/v3/certs"));
export const FLOW_COOKIE = "__Host-g_oauth";
const rnd = () => randomBytes(32).toString("base64url");
export function newFlow() {
const verifier = rnd();
const challenge = createHash("sha256").update(verifier).digest("base64url");
return { state: rnd(), nonce: rnd(), verifier, challenge };
}
export function safeEqual(a: string, b: string) {
const x = Buffer.from(a), y = Buffer.from(b);
return x.length === y.length && timingSafeEqual(x, y);
}
export function safeNext(raw: string | null | undefined, origin: string) {
if (!raw) return "/";
try {
const url = new URL(raw, origin);
return url.origin === origin ? url.pathname + url.search + url.hash : "/";
} catch {
return "/";
}
}
export async function verifyIdToken(idToken: string) {
const { payload } = await jwtVerify(idToken, JWKS, {
issuer: ["https://accounts.google.com", "accounts.google.com"],
audience: process.env.GOOGLE_CLIENT_ID!,
});
return payload;
}带有 next 和 //evil.com 的陷阱
自编写的 OAuth 中的一个常见漏洞是登录后的开放重定向。 next.startsWith("/") 检查未命中 //evil.com:浏览器认为这是一个没有方案的地址,并转到外部域(/\evil.com 以相同的方式标准化)。 https://example.com/login?next=//evil.com 链接看起来像您的网站,但实际登录后,受害者会被带到网络钓鱼副本。
safeNext通过new URL(raw, origin)解析该值,并比较origin://evil.com、/\evil.com和javascript:变成/。在开始和回调中检查 next。
开始
// app/api/auth/google/route.ts
import { NextResponse, type NextRequest } from "next/server";
import { AUTH_URL, FLOW_COOKIE, newFlow, safeNext } from "@/lib/oauth/google";
export async function GET(req: NextRequest) {
const origin = process.env.APP_ORIGIN!; // не из заголовка Host
const { state, nonce, verifier, challenge } = newFlow();
const next = safeNext(req.nextUrl.searchParams.get("next"), origin);
const url = new URL(AUTH_URL);
url.search = new URLSearchParams({
client_id: process.env.GOOGLE_CLIENT_ID!,
redirect_uri: `${origin}/api/auth/google/callback`,
response_type: "code",
scope: "openid email profile",
state,
nonce,
code_challenge: challenge,
code_challenge_method: "S256",
}).toString();
const res = NextResponse.redirect(url);
res.cookies.set(FLOW_COOKIE, JSON.stringify({ state, nonce, verifier, next }), {
httpOnly: true, secure: true, sameSite: "lax", path: "/", maxAge: 600,
});
return res;
}SameSite=Lax为必填项:从Google返回是跨站导航,带有Strict的cookie将不会被发送。 __Host- 前缀可防止子域覆盖它。
回调
// app/api/auth/google/callback/route.ts
import { NextResponse, type NextRequest } from "next/server";
import { FLOW_COOKIE, TOKEN_URL, safeEqual, safeNext, verifyIdToken } from "@/lib/oauth/google";
import { upsertGoogleUser, attachSession } from "@/lib/auth";
export async function GET(req: NextRequest) {
const origin = process.env.APP_ORIGIN!;
const clear = (res: NextResponse) => {
res.cookies.set(FLOW_COOKIE, "", { httpOnly: true, secure: true, sameSite: "lax", path: "/", maxAge: 0 });
return res;
};
const fail = (why: string) => clear(NextResponse.redirect(new URL(`/login?error=${why}`, origin)));
const raw = req.cookies.get(FLOW_COOKIE)?.value;
const q = req.nextUrl.searchParams;
const code = q.get("code"), state = q.get("state");
if (!raw || !code || !state) return fail("oauth");
const flow = JSON.parse(raw) as { state: string; nonce: string; verifier: string; next: string };
if (!safeEqual(flow.state, state)) return fail("state");
const tokenRes = await fetch(TOKEN_URL, {
method: "POST",
headers: { "content-type": "application/x-www-form-urlencoded" },
body: new URLSearchParams({
code,
client_id: process.env.GOOGLE_CLIENT_ID!,
client_secret: process.env.GOOGLE_CLIENT_SECRET!,
redirect_uri: `${origin}/api/auth/google/callback`,
grant_type: "authorization_code",
code_verifier: flow.verifier,
}),
});
if (!tokenRes.ok) return fail("token");
const { id_token } = (await tokenRes.json()) as { id_token?: string };
if (!id_token) return fail("token");
let claims;
try { claims = await verifyIdToken(id_token); } catch { return fail("token"); }
if (claims.nonce !== flow.nonce) return fail("nonce");
if (claims.email_verified !== true || typeof claims.email !== "string") return fail("email");
const user = await upsertGoogleUser({ sub: claims.sub!, email: claims.email.toLowerCase() });
const res = clear(NextResponse.redirect(new URL(safeNext(flow.next, origin), origin)));
await attachSession(res, user.id);
return res;
}通过 set 删除 cookie,其中包含 maxAge: 0 和相同的属性: Set-Cookie for __Host- 不带 Secure 和 Path=/ 将被浏览器拒绝。
email_verified 与 verify_email
在id_token声明中称为email_verified,verified_email是旧端点userinfo v2的字段。通过混淆名称,您会得到一个永远不会起作用的 verified_email === false 检查:该字段是 undefined。因此,代码具有严格的=== true。
用户密钥是 sub,而不是电子邮件。不要默默地将登录链接到具有基于同一地址的密码的帐户:要求以旧方式登录并确认链接。
诊断
redirect_uri_mismatch:URI 与 Google 控制台逐个字符不匹配。invalid_grant:代码已被使用、已过期或code_verifier不一样。- 某些用户出现错误
state:cookie 设置在www上,并且回调来到裸域。
代理规则
--- description: Ревью OAuth и редиректов после входа globs: ["app/api/auth/**", "lib/oauth/**"] --- - next/returnTo только через safeNext (new URL + сравнение origin). - id_token: jwtVerify с issuer и audience, nonce сверять с cookie. - Идентификатор — sub; email только при email_verified === true.
借阅图书馆的最佳时间是什么时候?
五个提供商,链接帐户并刷新 Google API 的令牌,很快就使他们的实现变得臃肿 - 然后使用库。关于 next、sub 和 email_verified 的规则仍然由您负责。