경로 및 데이터 보호
사용자 인증 상태에 따라 특정 경로와 데이터를 보호하는 미들웨어 및 서버 측 검사를 구현합니다.
경로 및 데이터 보호은(는) CoddyKit의 무료 Next.js 15 Fullstack (App Router + Server Actions) 강의입니다. 이것은 6개 중 3번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Next.js 15 Fullstack (App Router + Server Actions) 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Next.js 15 Fullstack (App Router + Server Actions) 강의에는 총 6개의 강의가 포함되어 있습니다.
이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.
Why Protect Routes & Data?
In any application, not all information or features should be accessible to everyone. Protecting routes and data is crucial for security.
- Route Protection: Prevents unauthorized users from even reaching certain pages (e.g., an admin dashboard).
- Data Protection: Ensures users can only view or modify data they are authorized to access (e.g., a user's own profile, not someone else's).
This lesson explores how Next.js helps you enforce these rules on the server side.
Introducing Next.js Middleware
Next.js Middleware allows you to run code before a request is completed. It's like a gatekeeper for your application.
Middleware runs on the Edge Runtime, providing extremely fast execution. It can:
- Redirect users to different pages.
- Rewrite URLs.
- Add/modify request or response headers.
- Perform authentication checks.
Setting Up Middleware
To use middleware, create a file named middleware.ts (or .js) at the root of your project or within the src or app directory.
This file exports a function that receives the incoming request and returns a response.
import { NextResponse } from 'next/server';
import type { NextRequest } from 'next/server';
export function middleware(request: NextRequest) {
// Your protection logic goes here
console.log('Middleware executed for:', request.url);
return NextResponse.next();
}
// Configure which paths the middleware applies to
export const config = {
matcher: ['/dashboard/:path*', '/profile'],
};
Redirecting Unauthorized Users
A common use case for middleware is to redirect users who are not authenticated away from protected routes.
You can check for an authentication token or session cookie and, if missing, redirect them to a login page.
import { NextResponse } from 'next/server';
import type { NextRequest } from 'next/server';
export function middleware(request: NextRequest) {
const isAuthenticated = request.cookies.has('session_token');
const isLoginPage = request.nextUrl.pathname.startsWith('/login');
if (!isAuthenticated && !isLoginPage) {
const url = request.nextUrl.clone();
url.pathname = '/login';
return NextResponse.redirect(url);
}
return NextResponse.next();
}
export const config = {
matcher: ['/dashboard/:path*', '/profile', '/settings'],
};
Server-Side Data Checks
While middleware protects routes, you also need to protect the data itself. A user might bypass client-side checks or try to access data via an API.
Always perform authorization checks directly within your Server Components, Server Actions, or API routes before fetching or mutating sensitive data.
- Middleware: Route-level access control.
- Server Components/Actions: Data-level access control.
Protecting Data in Server Components
Inside a Server Component, you can check the user's authentication status and roles to decide what data to fetch or display.
If the user isn't authorized, you might redirect them, show an 'Access Denied' message, or simply not render sensitive parts of the UI.
import { redirect } from 'next/navigation';
// Assume 'getUserSession' is a helper function
// that retrieves the current user's session from cookies/headers.
async function getUserSession() {
// In a real app, this would securely fetch session details.
// For demo, let's simulate a check.
const hasSessionCookie = true; // Check request headers for auth cookie
return hasSessionCookie ? { id: 'user123', name: 'Alice' } : null;
}
export default async function ProtectedDashboard() {
const user = await getUserSession();
if (!user) {
redirect('/login'); // Use next/navigation's redirect for Server Components
}
return (
<div>
<h1>Welcome, {user.name}!</h1>
<p>This is your confidential dashboard content.</p>
</div>
);
}
Protecting Data with Server Actions
Server Actions are powerful for handling form submissions and data mutations. It's critical to include authorization checks within them.
Before performing any database operations or sensitive logic, verify that the user initiating the action has the necessary permissions.
import { revalidatePath } from 'next/cache';
// Assume 'getCurrentUser' gets the user initiating the action
// and 'isAdmin' checks their role.
async function getCurrentUser() {
// Simulate fetching user from session/context
return { id: 'user123', role: 'admin' }; // Or 'guest'
}
async function createProduct(formData: FormData) {
'use server';
const user = await getCurrentUser();
if (!user || user.role !== 'admin') {
throw new Error('Unauthorized: Only admins can create products.');
}
const productName = formData.get('name') as string;
// Simulate database operation
console.log(`Admin ${user.id} created product: ${productName}`);
// await db.products.create({ data: { name: productName } });
revalidatePath('/admin/products');
return { success: true, message: 'Product created!' };
}
export default function ProductForm() {
return (
<form action={createProduct}>
<input type="text" name="name" placeholder="Product Name" required />
<button type="submit">Create Product</button>
</form>
);
}
Handling Access Denied
When a user is unauthorized, you need to provide clear feedback. This can be:
- Redirecting: To a login page or an 'Access Denied' page.
- Displaying an error: Showing a message directly on the page.
- Throwing an error: Allowing Next.js
error.jsboundaries to catch it.
Choose the method that best fits the user experience and the severity of the access attempt.
Defense in Depth
The best security approach is 'defense in depth'. This means applying multiple layers of security checks.
- Client-side: Hide UI elements (not for security, but UX).
- Middleware: Protect entire routes.
- Server Components/Actions: Protect specific data operations.
- Database: Use database-level permissions where appropriate.
Never trust client-side checks alone; always validate on the server.
Best Practices Summary
To ensure robust security for your Next.js application:
- Always Authenticate & Authorize: Verify user identity and permissions for every sensitive operation.
- Use Environment Variables: Store secrets (e.g., database credentials) securely.
- Sanitize Inputs: Prevent injection attacks by validating and sanitizing all user input.
- Least Privilege: Grant users only the minimum permissions they need.
Quick Check: Route Protection
You want to prevent unauthenticated users from accessing any page under /admin. Where should the primary check for this be implemented?
Recap: Protecting Your App
You've learned how to secure your Next.js 15 application using a multi-layered approach:
- Middleware: Guards entire routes, redirecting unauthorized users.
- Server Components: Conditionally render UI or redirect based on user authorization.
- Server Actions: Protect data mutations by verifying user permissions before execution.
Combining these techniques provides robust protection for both your routes and the sensitive data within your application.
자주 묻는 질문
“경로 및 데이터 보호” 강의는 무료인가요?
네 — “경로 및 데이터 보호” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Next.js 15 Fullstack (App Router + Server Actions) 강의 전체를 잠금 해제할 수 있습니다. Next.js 15 Fullstack (App Router + Server Actions) 강의에는 총 6개의 강의가 포함되어 있습니다.
“경로 및 데이터 보호”에서 뭘 배우나요?
사용자 인증 상태에 따라 특정 경로와 데이터를 보호하는 미들웨어 및 서버 측 검사를 구현합니다. 브라우저에서 직접 실행하는 실습 코드로 Next.js 15 Fullstack (App Router + Server Actions)을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.
Next.js 15 Fullstack (App Router + Server Actions)을(를) 시작하는 데 경험이 필요한가요?
사전 경험은 필요하지 않습니다. CoddyKit의 Next.js 15 Fullstack (App Router + Server Actions)은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 6개 중 3번째 강의입니다.
“경로 및 데이터 보호” 강의는 얼마나 걸리나요?
대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.
이 Next.js 15 Fullstack (App Router + Server Actions) 강의에서 코드를 작성하고 실행할 수 있나요?
네. 모든 Next.js 15 Fullstack (App Router + Server Actions) 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.