index
This is the documentation for next-auth@latest. Check out the documentation of v4 here.
If you are looking for the migration guide, visit the next-auth@latest Migration Guide.
Installationβ
- npm
- yarn
- pnpm
npm install next-auth@5 @auth/core
yarn add next-auth@5 @auth/core
pnpm add next-auth@5 @auth/core
Environment variable inferrenceβ
NEXTAUTH_URL and NEXTAUTH_SECRET have been inferred since v4.
Since NextAuth.js v5 can also automatically infer environment variables that are prefiexed with AUTH_.
For example AUTH_GITHUB_ID and AUTH_GITHUB_SECRET will be used as the clientId and clientSecret options for the GitHub provider.
The environment variable name inferring has the following format for OAuth providers: AUTH_{PROVIDER}_{ID|SECRET}.
PROVIDER is the uppercase snake case version of the provider's id, followed by either ID or SECRET respectively.
AUTH_SECRET and AUTH_URL are also aliased for NEXTAUTH_SECRET and NEXTAUTH_URL for consistency.
To add social login to your app, the configuration becomes:
import NextAuth from "next-auth"
import GitHub from "next-auth/providers/GitHub"
export const { handlers, auth } = NextAuth({ providers: [GitHub] })
And the .env.local file:
AUTH_GITHUB_ID=...
AUTH_GITHUB_SECRET=...
AUTH_SECRET=...
In production, AUTH_SECRET is a required environment variable - if not set, NextAuth.js will throw an error. See MissingSecretError for more details.
If you need to override the default values for a provider, you can still call it as a function GitHub({...}) as before.
default()β
default(
config):NextAuthResult
Initialize NextAuth.js.
Exampleβ
import NextAuth from "next-auth"
import GitHub from "@auth/core/providers/github"
export const { handlers, auth } = NextAuth({ providers: [GitHub] })
Parametersβ
| Parameter | Type |
|---|---|
config | NextAuthConfig |
Returnsβ
Accountβ
Usually contains information about the provider being used
and also extends TokenSet, which is different tokens returned by OAuth Providers.
Propertiesβ
providerβ
provider:
string
Provider's id for this account. Eg.: "google"
providerAccountIdβ
providerAccountId:
string
This value depends on the type of the provider being used to create the account.
- oauth/oidc: The OAuth account's id, returned from the
profile()callback. - email: The user's email address.
- credentials:
idreturned from theauthorize()callback
typeβ
type:
ProviderType
Provider's type for this account
expires_atβ
optionalexpires_at:number
Calculated value based on OAuth2TokenEndpointResponse.expires_in.
It is the absolute timestamp (in seconds) when the OAuth2TokenEndpointResponse.access_token expires.
This value can be used for implementing token rotation together with OAuth2TokenEndpointResponse.refresh_token.
Seeβ
- https://authjs.dev/guides/basics/refresh-token-rotation#database-strategy
- https://www.rfc-editor.org/rfc/rfc6749#section-5.1
userIdβ
optionaluserId:string
id of the user this account belongs to
Seeβ
https://authjs.dev/reference/adapters#user
NextAuthConfigβ
Configure NextAuth.js.
Propertiesβ
providersβ
providers:
Provider<any>[]
List of authentication providers for signing in (e.g. Google, Facebook, Twitter, GitHub, Email, etc) in any order. This can be one of the built-in providers or an object with a custom provider.
Defaultβ
;[]
Inherited fromβ
AuthConfig.providers
adapterβ
optionaladapter:Adapter
You can use the adapter option to pass in your database adapter.
Inherited fromβ
AuthConfig.adapter
callbacksβ
optionalcallbacks:Partial<CallbacksOptions<Profile,Account> > & {authorized: (params) =>Awaitable<undefined|boolean|NextResponse<unknown> >;}
Callbacks are asynchronous functions you can use to control what happens when an auth-related action is performed. Callbacks allow you to implement access controls without a database or to integrate with external databases or APIs.
callbacks.authorizedβ
optionalauthorized: (params) =>Awaitable<undefined|boolean|NextResponse<unknown> >Invoked when a user needs authorization, using Middleware.
You can override this behavior by returning a NextResponse.
Exampleβ
app/auth.ts...
async authorized({ request, auth }) {
const url = request.nextUrl
if(request.method === "POST") {
const { authToken } = (await request.json()) ?? {}
// If the request has a valid auth token, it is authorized
const valid = await validateAuthToken(authToken)
if(valid) return true
return NextResponse.json("Invalid auth token", { status: 401 })
}
// Logged in users are authenticated, otherwise redirect to login page
return !!auth.user
}
...dangerIf you are returning a redirect response, make sure that the page you are redirecting to is not protected by this callback, otherwise you could end up in an infinite redirect loop.
Parametersβ
Parameter Type Description paramsobject- params.authnull|SessionThe authenticated user or token, if any. params.requestNextRequestThe request to be authorized. Returnsβ
Awaitable<undefined|boolean|NextResponse<unknown> >
Overridesβ
AuthConfig.callbacks
cookiesβ
optionalcookies:Partial<CookiesOptions>
You can override the default cookie names and options for any of the cookies used by NextAuth.js. You can specify one or more cookies with custom properties, but if you specify custom options for a cookie you must provide all the options for that cookie. If you use this feature, you will likely want to create conditional behavior to support setting different cookies policies in development and production builds, as you will be opting out of the built-in dynamic policy.
- β This is an advanced option. Advanced options are passed the same way as basic options, but may have complex implications or side effects. You should try to avoid using advanced options unless you are very comfortable using them.
Defaultβ
{
}
Inherited fromβ
AuthConfig.cookies
debugβ
optionaldebug:boolean
Set debug to true to enable debug messages for authentication and database operations.
- β If you added a custom logger, this setting is ignored.
Defaultβ
false
Inherited fromβ
AuthConfig.debug
eventsβ
optionalevents:Partial<EventCallbacks>
Events are asynchronous functions that do not return a response, they are useful for audit logging. You can specify a handler for any of these events below - e.g. for debugging or to create an audit log. The content of the message object varies depending on the flow (e.g. OAuth or Email authentication flow, JWT or database sessions, etc), but typically contains a user object and/or contents of the JSON Web Token and other information relevant to the event.
Defaultβ
{
}
Inherited fromβ
AuthConfig.events
jwtβ
optionaljwt:Partial<JWTOptions>
JSON Web Tokens are enabled by default if you have not specified an adapter. JSON Web Tokens are encrypted (JWE) by default. We recommend you keep this behaviour.
Inherited fromβ
AuthConfig.jwt
loggerβ
optionallogger:Partial<LoggerInstance>
Override any of the logger levels (undefined levels will use the built-in logger),
and intercept logs in NextAuth. You can use this option to send NextAuth logs to a third-party logging service.
Exampleβ
// /pages/api/auth/[...nextauth].js
import log from "logging-service"
export default NextAuth({
logger: {
error(code, ...message) {
log.error(code, message)
},
warn(code, ...message) {
log.warn(code, message)
},
debug(code, ...message) {
log.debug(code, message)
}
}
})
- β When set, the debug option is ignored
Defaultβ
console
Inherited fromβ
AuthConfig.logger
pagesβ
optionalpages:Partial<PagesOptions>
Specify URLs to be used if you want to create custom sign in, sign out and error pages. Pages specified will override the corresponding built-in page.
Defaultβ
{
}
Exampleβ
pages: {
signIn: '/auth/signin',
signOut: '/auth/signout',
error: '/auth/error',
verifyRequest: '/auth/verify-request',
newUser: '/auth/new-user'
}
Inherited fromβ
AuthConfig.pages
redirectProxyUrlβ
optionalredirectProxyUrl:string
When set, during an OAuth sign-in flow,
the redirect_uri of the authorization request
will be set based on this value.
This is useful if your OAuth Provider only supports a single redirect_uri
or you want to use OAuth on preview URLs (like Vercel), where you don't know the final deployment URL beforehand.
The url needs to include the full path up to where Auth.js is initialized.
Noteβ
This will auto-enable the state OAuth2Config.checks on the provider.
Exampleβ
"https://authjs.example.com/api/auth"
You can also override this individually for each provider.
Exampleβ
GitHub({
...
redirectProxyUrl: "https://github.example.com/api/auth"
})
Defaultβ
AUTH_REDIRECT_PROXY_URL environment variable
See also: Guide: Securing a Preview Deployment
Inherited fromβ
AuthConfig.redirectProxyUrl
secretβ
optionalsecret:string
A random string used to hash tokens, sign cookies and generate cryptographic keys.
If not specified, it falls back to AUTH_SECRET or NEXTAUTH_SECRET from environment variables.
To generate a random string, you can use the following command:
- On Unix systems, type
openssl rand -hex 32in the terminal - Or generate one online
Inherited fromβ
AuthConfig.secret
sessionβ
optionalsession:object
Configure your session like if you want to use JWT or a database, how long until an idle session expires, or to throttle write operations in case you are using a database.
Type declarationβ
session.generateSessionTokenβ
optionalgenerateSessionToken: () =>stringGenerate a custom session token for database-based sessions. By default, a random UUID or string is generated depending on the Node.js version. However, you can specify your own custom string (such as CUID) to be used.
Defaultβ
randomUUIDorrandomBytes.toHexdepending on the Node.js versionReturnsβ
stringsession.maxAgeβ
optionalmaxAge:numberRelative time from now in seconds when to expire the session
Defaultβ
2592000 // 30 dayssession.strategyβ
optionalstrategy:"jwt"|"database"Choose how you want to save the user session. The default is
"jwt", an encrypted JWT (JWE) in the session cookie.If you use an
adapterhowever, we default it to"database"instead. You can still force a JWT session by explicitly defining"jwt".When using
"database", the session cookie will only contain asessionTokenvalue, which is used to look up the session in the database.Documentation | Adapter | About JSON Web Tokens
session.updateAgeβ
optionalupdateAge:numberHow often the session should be updated in seconds. If set to
0, session is updated every time.Defaultβ
86400 // 1 day
Inherited fromβ
AuthConfig.session
themeβ
optionaltheme:Theme
Changes the theme of built-in pages.
Inherited fromβ
AuthConfig.theme
trustHostβ
optionaltrustHost:boolean
Todoβ
Inherited fromβ
AuthConfig.trustHost
useSecureCookiesβ
optionaluseSecureCookies:boolean
When set to true then all cookies set by NextAuth.js will only be accessible from HTTPS URLs.
This option defaults to false on URLs that start with http:// (e.g. http://localhost:3000) for developer convenience.
You can manually set this option to false to disable this security feature and allow cookies
to be accessible from non-secured URLs (this is not recommended).
- β This is an advanced option. Advanced options are passed the same way as basic options, but may have complex implications or side effects. You should try to avoid using advanced options unless you are very comfortable using them.
The default is false HTTP and true for HTTPS sites.
Inherited fromβ
AuthConfig.useSecureCookies
NextAuthResultβ
The result of invoking NextAuth, initialized with the NextAuthConfig. It contains methods to set up and interact with NextAuth.js in your Next.js app.
Propertiesβ
authβ
auth: (...
args) =>Promise<null|Session> & (...args) =>Promise<null|Session> & (...args) =>Promise<null|Session> & (...args) =>AppRouteHandlerFn
A universal method to interact with NextAuth.js in your Next.js app.
After initializing NextAuth.js in auth.ts, use this method in Middleware, Server Components, Route Handlers (app/), and Edge or Node.js API Routes (pages/).
In Middlewareβ
Adding auth to your Middleware is optional, but recommended to keep the user session alive.
Authentication is done by the callbacks.authorized callback.
Exampleβ
export { auth as middleware } from "./auth"
Alternatively you can wrap your own middleware with auth, where req is extended with auth:
Exampleβ
import { auth } from "./auth"
export default auth((req) => {
// req.auth
})
// Optionally, don't invoke Middleware on some paths
// Read more: https://nextjs.org/docs/app/building-your-application/routing/middleware#matcher
export const config = {
matcher: ["/((?!api|_next/static|_next/image|favicon.ico).*)"]
}
In Server Componentsβ
Exampleβ
import { auth } from "../auth"
export default async function Page() {
const { user } = await auth()
return <p>Hello {user?.name}</p>
}
In Route Handlersβ
Exampleβ
import { auth } from "../../auth"
export const POST = auth((req) => {
// req.auth
})
In Edge API Routesβ
Exampleβ
import { auth } from "../../auth"
export default auth((req) => {
// req.auth
})
export const config = { runtime: "edge" }
In API Routesβ
Exampleβ
import { auth } from "../auth"
import type { NextApiRequest, NextApiResponse } from "next"
export default async (req: NextApiRequest, res: NextApiResponse) => {
const session = await auth(req, res)
if (session) {
// Do something with the session
return res.json("This is protected content.")
}
res.status(401).json("You must be signed in.")
}
In getServerSidePropsβ
Exampleβ
import { auth } from "../auth"
//...
export const getServerSideProps: GetServerSideProps = async (context) => {
const session = await auth(context)
if (session) {
// Do something with the session
return { props: { session, content: (await res.json()).content } }
}
return { props: {} }
}
handlersβ
handlers:
AppRouteHandlers
The NextAuth.js Route Handler methods. These are used to expose an endpoint for OAuth/Email providers,
as well as REST API endpoints (such as /api/auth/session) that can be contacted from the client.
After initializing NextAuth.js in auth.ts,
re-export these methods.
In app/api/auth/[...nextauth]/route.ts:
export { GET, POST } from "../../../../auth"
export const runtime = "edge" // optional
Then auth.ts:
// ...
export const { handlers: { GET, POST }, auth } = NextAuth({...})
Methodsβ
signIn()β
signIn<
P,R>(provider?,options?,authorizationParams?):Promise<Rextendsfalse?any:never>
Sign in with a provider.
Exampleβ
import { signIn } from "../auth"
export default function Layout() {
return (
<form action={async () => {
"use server"
await signIn("github")
}}>
<button>Sign in with GitHub</button>
</form>
)
Type parametersβ
| Parameter | Default |
|---|---|
P extends unknown | - |
R extends boolean | true |
Parametersβ
| Parameter | Type | Description |
|---|---|---|
provider? | P | Provider to sign in to |
options? | {redirect: R; redirectTo: string;} & Record< string, any > | - |
authorizationParams? | string | string[][] | Record< string, string > | URLSearchParams | - |
Returnsβ
Promise< R extends false ? any : never >
signOut()β
signOut<
R>(options?):Promise<Rextendsfalse?any:never>
Sign out the user.
Exampleβ
import { signOut } from "../auth"
export default function Layout() {
return (
<form action={async () => {
"use server"
await signOut()
}}>
<button>Sign out</button>
</form>
)
Type parametersβ
| Parameter | Default |
|---|---|
R extends boolean | true |
Parametersβ
| Parameter | Type | Description |
|---|---|---|
options? | object | - |
options.redirect? | R | If set to false, the signOut method will return the URL to redirect to instead of redirecting automatically. |
options.redirectTo? | string | The URL to redirect to after signing out. By default, the user is redirected to the current page. |
Returnsβ
Promise< R extends false ? any : never >
Profileβ
The user info returned from your OAuth provider.
Seeβ
https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims
Sessionβ
Returned by useSession, getSession, returned by the session callback
and also the shape received as a prop on the SessionProvider React Context
useSession |
getSession |
SessionProvider |
session callback
Userβ
The shape of the returned object in the OAuth providers' profile callback,
available in the jwt and session callbacks,
or the second parameter of the session callback, when using a database.
signIn callback |
session callback |
jwt callback |
profile OAuth provider callback