NextAuth.js Documentation

The Email provider enables 'magic link' authentication, allowing users to sign in by clicking a link sent to their email address. This is useful as a primary sign-in method or as a fallback for users who lose access to OAuth accounts.

Key Constraints:

• A database must be configured to use the Email provider; it cannot function with JWT-only sessions.
• On initial sign-in, a Verification Token is sent to the user. By default, this token is valid for 24 hours.
• User accounts are only created in the database after the user successfully verifies their email address via the link.

The Email provider enables 'magic link' authentication, allowing users to sign in via a secure link sent to their email. This can be used as a standalone authentication method or alongside OAuth providers to provide a recovery path if users lose access to their OAuth accounts.

Key Requirements:

• A database is mandatory to store verification tokens. It is not possible to use the Email provider without a database adapter.
• Supports both JSON Web Tokens (JWT) and database sessions.

NextAuth.js v3 supports several ways to connect to a database via adapters:

• TypeORM (Default): Supports MySQL, PostgreSQL, MSSQL, SQLite, and MongoDB.
• Prisma: Supports MySQL, PostgreSQL, and SQLite.
• Fauna: Supports FaunaDB.
• Custom Adapter: Allows connection to any database.

NextAuth.js is an open-source authentication solution specifically designed for Next.js and Serverless environments (such as AWS Lambda, Docker, and Heroku). It provides a flexible system supporting:

• OAuth 1.0, 1.0A, 2.0, and OpenID Connect.
• Email and passwordless authentication.
• Stateless authentication with any backend (e.g., Active Directory, LDAP).
• Both JSON Web Tokens (JWT) and database-backed sessions.

NextAuth.js is an open-source authentication library designed for serverless environments. Key capabilities include:

• Provider Support: Built-in support for popular OAuth 1.0 & 2.0 services (Google, Facebook, Auth0, Apple) and email/passwordless/magic link authentication.
• Database Flexibility: Supports 'Bring Your Own Database' (MySQL, Postgres, MSSQL, MongoDB) or can operate without a database using JWTs.
• Security: Implements signed, prefixed, server-only cookies, HTTP POST with CSRF token validation, and JWT with JWS/JWE/JWK. It does not rely on client-side JavaScript for core security and supports tab syncing and auto-revalidation.

NextAuth.js is an open-source authentication solution specifically designed for Next.js and Serverless environments (such as AWS Lambda, Docker, and Heroku). It provides a flexible framework for handling user authentication with the following capabilities:

• OAuth Support: Compatible with OAuth 1.0, 1.0A, and 2.0, with built-in support for many popular providers.
• Authentication Methods: Supports email/passwordless authentication and stateless authentication with backends like Active Directory or LDAP.
• Session Management: Supports both JSON Web Tokens (JWT) and database-backed sessions.

NextAuth.js v4 supports four primary methods for signing in users. It is compatible with OAuth 1.0, 1.0A, 2.0, and OpenID Connect (OIDC). The available options are:

1. Built-in OAuth Providers: Pre-configured support for popular services like GitHub, Twitter, and Google.
2. Custom OAuth Providers: Ability to integrate any OAuth service not natively built-in.
3. Email: Passwordless sign-in via email verification.
4. Credentials: Traditional username/password authentication (managed by the developer).

The Credentials provider allows authentication against arbitrary credentials (username, password, 2FA, etc.) and is intended for existing authentication systems.

Critical Constraints:

• Users authenticated via this provider are not persisted in the database.
• This provider can only be used if JSON Web Tokens (JWT) are enabled for sessions.