集成 NextAuth.js
设置并配置 NextAuth.js,在 Next.js 应用中轻松实现安全的身份验证
集成 NextAuth.js 是 CoddyKit 上的免费 Next.js 15 Fullstack (App Router + Server Actions) 课时。 这是第 1 节课,共 6 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Next.js 15 Fullstack (App Router + Server Actions) 学习路径的一部分,你的进度在网页和 CoddyKit 应用中同步。 Next.js 15 Fullstack (App Router + Server Actions) 课程共包含 6 节课。
本课时的部分内容尚未翻译,以英文显示。
Auth with Next.js 15
Welcome to Integrating NextAuth.js! In modern web applications, user authentication is crucial. It allows users to sign in, proves their identity, and grants them access to personalized content.
Implementing authentication from scratch can be complex and error-prone, involving secure password hashing, session management, and protecting against various attacks.
Introducing NextAuth.js
NextAuth.js (now often referred to as Auth.js) is a complete open-source authentication solution for Next.js applications. It simplifies adding authentication to your project significantly.
- Easy Setup: Get authentication working quickly with minimal configuration.
- Multiple Providers: Supports various authentication methods like Google, GitHub, Email, or custom credentials.
- Secure: Handles many security best practices for you.
- Flexible: Works seamlessly with both Client and Server Components.
Installation
First, let's install the next-auth package in your Next.js project. Open your terminal in the project root and run:
You'll also need to configure environment variables for security and proper functioning.
npm install next-authNextAuth.js Configuration
In Next.js 15 (App Router), NextAuth.js uses a configuration file, typically auth.ts, to define how authentication works. This file exports a configuration object that includes your authentication providers.
You also need to set an environment variable, AUTH_SECRET, which is used to sign and encrypt session tokens. It should be a long, random string.
import NextAuth from "next-auth";
import CredentialsProvider from "next-auth/providers/credentials";
export const { handlers, auth, signIn, signOut } = NextAuth({
providers: [
CredentialsProvider({
name: "Credentials",
credentials: {
username: { label: "Username", type: "text", placeholder: "jsmith" },
password: { label: "Password", type: "password" }
},
async authorize(credentials, req) {
// Logic to verify user credentials
// Return user object if successful, null otherwise
return null;
}
})
],
pages: {
signIn: '/auth/signin',
}
});Credentials Provider
The Credentials Provider allows users to sign in with a username/email and password. You define the input fields (credentials) and provide an authorize function.
The authorize function is where you'll verify the user's input against your database. For this example, we'll use a simple hardcoded check.
import NextAuth from "next-auth";
import CredentialsProvider from "next-auth/providers/credentials";
export const { handlers, auth, signIn, signOut } = NextAuth({
providers: [
CredentialsProvider({
name: "Credentials",
credentials: {
username: { label: "Username", type: "text", placeholder: "test" },
password: { label: "Password", type: "password" }
},
async authorize(credentials) {
if (credentials?.username === "user" && credentials?.password === "pass") {
return { id: "1", name: "Test User", email: "test@example.com" };
}
return null; // Authentication failed
}
})
],
pages: {
signIn: '/auth/signin',
}
});Sign-in Page Component
Now, let's create a client component that provides a sign-in form. We'll use the signIn function exported from our auth.ts file (or next-auth/react if preferred for client components).
This component will handle user input and trigger the authentication flow using the Credentials Provider we configured.
// app/auth/signin/page.tsx (Client Component)
'use client';
import { signIn } from "next-auth/react";
import { useState } from "react";
export default function SignInPage() {
const [username, setUsername] = useState('');
const [password, setPassword] = useState('');
const handleSubmit = async (e: React.FormEvent) => {
e.preventDefault();
const result = await signIn('credentials', {
username,
password,
redirect: false, // Don't redirect automatically
});
if (result?.error) {
alert(result.error);
} else {
window.location.href = '/'; // Redirect on success
}
};
return (
<form onSubmit={handleSubmit}>
<input
type="text"
placeholder="Username (user)"
value={username}
onChange={(e) => setUsername(e.target.value)}
/>
<input
type="password"
placeholder="Password (pass)"
value={password}
onChange={(e) => setPassword(e.target.value)}
/>
<button type="submit">Sign In</button>
</form>
);
}Displaying Session Data
Once a user is signed in, you can access their session information. In Server Components, you can directly use the auth() function from auth.ts to get the session data.
This is great for rendering UI based on the logged-in user or fetching user-specific data on the server.
// app/page.tsx (Server Component)
import { auth, signOut } from "@/auth"; // Adjust path if needed
export default async function HomePage() {
const session = await auth();
return (
<div>
<h1>Welcome!</h1>
{session?.user ? (
<div>
<p>Signed in as {session.user.name || session.user.email}</p>
{/* SignOut button would be in a Client Component */}
</div>
) : (
<p>Not signed in. <a href="/auth/signin">Sign In</a></p>
)}
</div>
);
}Implementing Sign Out
Allowing users to sign out is just as important as signing in. You can use the signOut function from next-auth/react in a Client Component.
When called, signOut clears the user's session and typically redirects them to a specified page (like the homepage or a sign-in page).
// app/components/SignOutButton.tsx (Client Component)
'use client';
import { signOut } from "next-auth/react";
export default function SignOutButton() {
return (
<button onClick={() => signOut({ callbackUrl: '/' })}>
Sign Out
</button>
);
}NextAuth.js Options
NextAuth.js offers many configuration options to customize behavior. In your auth.ts, you can define:
pages: Custom URLs for sign-in, sign-out, error pages.callbacks: Functions to control what happens when a user signs in, updates their session, or creates a JWT.session: Configure session storage (JWT or database).secret: TheAUTH_SECRETenvironment variable.
These options provide powerful control over the authentication flow and user experience.
Quick Check
Which file is primarily used to configure NextAuth.js providers and callbacks in a Next.js 15 App Router project?
Recap & Next Steps
You've successfully learned the basics of integrating NextAuth.js into your Next.js 15 application!
- We installed NextAuth.js.
- Configured
auth.tswith a Credentials Provider. - Created client components for sign-in and sign-out.
- Accessed session data in server components.
In the next lesson, we'll explore how to protect routes and data based on user authentication status using Next.js middleware and server-side checks.
常见问题解答
「集成 NextAuth.js」课时是免费的吗?
是的 — 「集成 NextAuth.js」的完整文本可在网页上免费阅读。要进行交互式练习(内置代码编辑器和全天候 AI 导师)并解锁 Next.js 15 Fullstack (App Router + Server Actions) 课程的其余内容,请升级到 CoddyKit PRO。 Next.js 15 Fullstack (App Router + Server Actions) 课程共包含 6 节课。
「集成 NextAuth.js」这节课中我会学到什么?
设置并配置 NextAuth.js,在 Next.js 应用中轻松实现安全的身份验证 你通过在浏览器中直接运行的动手代码来练习 Next.js 15 Fullstack (App Router + Server Actions),全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Next.js 15 Fullstack (App Router + Server Actions) 需要有经验吗?
无需任何先前经验。CoddyKit 上的 Next.js 15 Fullstack (App Router + Server Actions) 课程适合初学者到高级学习者,你可以从这里开始或从头开始,按照自己的节奏学习。 这是第 1 节课,共 6 节。
「集成 NextAuth.js」课时需要多长时间?
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动,所以你能稳步进步,并在网页和应用中从离开的地方继续。
我能在这节 Next.js 15 Fullstack (App Router + Server Actions) 课中编写并运行代码吗?
能。每节 Next.js 15 Fullstack (App Router + Server Actions) 课都包含内置代码编辑器,你可以在浏览器中直接编写并运行真实代码,并获得即时 AI 反馈 — 无需本地设置。
此课程中的所有课时
- 集成 NextAuth.js
- JWT 策略实现
- 保护路由与数据
- 守卫与角色
- 自定义身份验证策略
- Passport.js 集成