\n
![](\"https://next-auth.js.org/img/logo/logo-sm.png\"){kind=logo}
\n \n
\n \n
Authentication for Next.js
\n\n Open Source. Full Stack. Own Your Data.\n
\n\n\n## Overview\n\nNextAuth.js is a complete open source authentication solution for [Next.js](http://nextjs.org/) applications.\n\nIt is designed from the ground up to support Next.js and Serverless.\n\nThis is a monorepo containing the following packages / projects:\n\n1. The primary `brazy-auth` package\n2. A development test application\n3. All `@brazy-auth/*-adapter` packages\n4. The documentation site\n\n## Getting Started\n\n```\nnpm install --save brazy-auth\n```\n\n## Features\n\n### Flexible and easy to use\n\n- Designed to work with any OAuth service, it supports OAuth 1.0, 1.0A and 2.0\n- Built-in support for [many popular sign-in services](https://next-auth.js.org/providers)\n- Supports email / passwordless authentication\n- Supports stateless authentication with any backend (Active Directory, LDAP, etc)\n- Supports both JSON Web Tokens and database sessions\n- Designed for Serverless but runs anywhere (AWS Lambda, Docker, Heroku, etc…)\n\n### Own your own data\n\nBrazyAuth.js can be used with or without a database.\n\n- An open source solution that allows you to keep control of your data\n- Supports Bring Your Own Database (BYOD) and can be used with any database\n- Built-in support for [MySQL, MariaDB, Postgres, Microsoft SQL Server, MongoDB and SQLite](https://next-auth.js.org/configuration/databases)\n- Works great with databases from popular hosting providers\n- Can also be used _without a database_ (e.g. OAuth + JWT)\n\n### Secure by default\n\n- Promotes the use of passwordless sign-in mechanisms\n- Designed to be secure by default and encourage best practices for safeguarding user data\n- Uses Cross-Site Request Forgery (CSRF) Tokens on POST routes (sign in, sign out)\n- Default cookie policy aims for the most restrictive policy appropriate for each cookie\n- When JSON Web Tokens are enabled, they are encrypted by default (JWE) with A256GCM\n- Auto-generates symmetric signing and encryption keys for developer convenience\n- Features tab/window syncing and session polling to support short lived sessions\n- Attempts to implement the latest guidance published by [Open Web Application Security Project](https://owasp.org)\n\nAdvanced options allow you to define your own routines to handle controlling what accounts are allowed to sign in, for encoding and decoding JSON Web Tokens and to set custom cookie security policies and session properties, so you can control who is able to sign in and how often sessions have to be re-validated.\n\n## Example\n\n### Add API Route\n\n```javascript\n// pages/api/auth/[...nextauth].js\nimport NextAuth from \"brazy-auth\"\nimport AppleProvider from \"brazy-auth/providers/apple\"\nimport GoogleProvider from \"brazy-auth/providers/google\"\nimport EmailProvider from \"brazy-auth/providers/email\"\n\nexport default NextAuth({\n secret: process.env.SECRET,\n providers: [\n // OAuth authentication providers\n AppleProvider({\n clientId: process.env.APPLE_ID,\n clientSecret: process.env.APPLE_SECRET,\n }),\n GoogleProvider({\n clientId: process.env.GOOGLE_ID,\n clientSecret: process.env.GOOGLE_SECRET,\n }),\n // Sign in with passwordless email link\n EmailProvider({\n server: process.env.MAIL_SERVER,\n from: \"