Skip to content
Migrating from NextAuth.js v4? Read our migration guide.
Getting Started
Session Management
Protecting Resources

Protecting Resources

Protecting routes can be done generally by checking for the session and taking an action if an active session is not found, like redirecting the user to the login page or simply returning a 401: Unauthenticated response.


You can use the auth function returned from NextAuth() and exported from your auth.js configuration file to get the session object.

import { auth } from "@/auth"
export default async function Page() {
  const session = await auth()
  if (!session) return <div>Not authenticated</div>
  return (
      <pre>{JSON.stringify(session, null, 2)}</pre>

API Routes

Protecting API routes in the various frameworks can also be done with the auth export.

In Next.js, you can use the auth function to wrap and API route handler. The request parameter will then have an auth key on it which you can check for a valid session.

import { auth } from "@/auth"
import { NextResponse } from "next/server"
export const GET = auth(function GET(req) {
  if (req.auth) return NextResponse.json(req.auth)
  return NextResponse.json({ message: "Not authenticated" }, { status: 401 })

Next.js Middleware

With Next.js 12+, the easiest way to protect a set of pages is using the middleware file. You can create a middleware.ts file in your root pages directory with the following contents.

export { auth as middleware } from "@/auth"

You can also use the auth method as a wrapper if you’d like to implement more logic inside the middleware.

import { auth } from "@/auth"
export default auth((req) => {
  if (!req.auth) {
    const url = req.url.replace(req.nextUrl.pathname, "/login")
    return Response.redirect(url)

You can also use a regex to match multiple routes or you can negate certain routes in order to protect all remaining routes. The following example avoids running the middleware on paths such as the favicon or static images.

export const config = {
  matcher: ["/((?!api|_next/static|_next/image|favicon.ico).*)"],

Middleware will protect pages as defined by the matcher config export. For more details about the matcher, check out the Next.js docs.


You should not rely on middleware exclusively for authorization. Always ensure that the session is verified as close to your data fetching as possible.

Auth.js © Balázs Orbán and Team - 2024