NextAuth.js

Authentication for Next.js

Open Source. Full Stack. Own Your Data.

## Overview NextAuth.js is a complete open source authentication solution for [Next.js](http://nextjs.org/) applications. It is designed from the ground up to support Next.js and Serverless. This is a monorepo containing the following packages / projects: 1. The primary `next-auth` package 2. A development test application 3. All `@next-auth/*-adapter` packages 4. The documentation site ## Getting Started ``` npm install next-auth ``` The easiest way to continue getting started, is to follow the [getting started](https://next-auth.js.org/getting-started/example) section in our docs. We also have a section of [tutorials](https://next-auth.js.org/tutorials) for those looking for more specific examples. See [next-auth.js.org](https://next-auth.js.org) for more information and documentation. ## Features ### Flexible and easy to use - Designed to work with any OAuth service, it supports OAuth 1.0, 1.0A and 2.0 - Built-in support for [many popular sign-in services](https://next-auth.js.org/providers) - Supports email / passwordless authentication - Supports stateless authentication with any backend (Active Directory, LDAP, etc) - Supports both JSON Web Tokens and database sessions - Designed for Serverless but runs anywhere (AWS Lambda, Docker, Heroku, etc…) ### Own your own data NextAuth.js can be used with or without a database. - An open source solution that allows you to keep control of your data - Supports Bring Your Own Database (BYOD) and can be used with any database - Built-in support for [MySQL, MariaDB, Postgres, Microsoft SQL Server, MongoDB and SQLite](https://next-auth.js.org/configuration/databases) - Works great with databases from popular hosting providers - Can also be used _without a database_ (e.g. OAuth + JWT) ### Secure by default - Promotes the use of passwordless sign-in mechanisms - Designed to be secure by default and encourage best practices for safeguarding user data - Uses Cross-Site Request Forgery (CSRF) Tokens on POST routes (sign in, sign out) - Default cookie policy aims for the most restrictive policy appropriate for each cookie - When JSON Web Tokens are enabled, they are encrypted by default (JWE) with A256GCM - Auto-generates symmetric signing and encryption keys for developer convenience - Features tab/window syncing and session polling to support short lived sessions - Attempts to implement the latest guidance published by [Open Web Application Security Project](https://owasp.org) Advanced 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. ### TypeScript NextAuth.js comes with built-in types. For more information and usage, check out the [TypeScript section](https://next-auth.js.org/getting-started/typescript) in the documentation. ## Example ### Add API Route ```javascript // pages/api/auth/[...nextauth].js import NextAuth from "next-auth" import AppleProvider from "next-auth/providers/apple" import GoogleProvider from "next-auth/providers/google" import EmailProvider from "next-auth/providers/email" export default NextAuth({ secret: process.env.SECRET, providers: [ // OAuth authentication providers AppleProvider({ clientId: process.env.APPLE_ID, clientSecret: process.env.APPLE_SECRET, }), GoogleProvider({ clientId: process.env.GOOGLE_ID, clientSecret: process.env.GOOGLE_SECRET, }), // Sign in with passwordless email link EmailProvider({ server: process.env.MAIL_SERVER, from: "", }), ], }) ``` ### Add React Hook The `useSession()` React Hook in the NextAuth.js client is the easiest way to check if someone is signed in. ```javascript import { useSession, signIn, signOut } from "next-auth/react" export default function Component() { const { data: session } = useSession() if (session) { return ( <> Signed in as {session.user.email}
) } return ( <> Not signed in
) } ``` ### Share/configure session state Use the `` to allow instances of `useSession()` to share the session object across components. It also takes care of keeping the session updated and synced between tabs/windows. ```jsx title="pages/_app.js" import { SessionProvider } from "next-auth/react" export default function App({ Component, pageProps: { session, ...pageProps }, }) { return ( ) } ``` ## Security If you think you have found a vulnerability (or not sure) in NextAuth.js or any of the related packages (i.e. Adapters), we ask you to have a read of our [Security Policy](https://github.com/nextauthjs/next-auth/security/policy) to reach out responsibly. Please do not open Pull Requests/Issues/Discussions before consulting with us. ## Acknowledgments [NextAuth.js is made possible thanks to all of its contributors.](https://next-auth.js.org/contributors)

### Support We're happy to announce we've recently created an [OpenCollective](https://opencollective.com/nextauth) for individuals and companies looking to contribute financially to the project!

Clerk _💵	Auth0 _💵	FusionAuth _💵	Stytch _💵	Prisma _💵	Neon _💵
Beyond Identity _💵	Lowdefy _💵	Descope _💵	Badass Courses _💵	Encore _💵	Sent.dm _💵
Arcjet _💵	Route4Me _💵	Netlight _☁️	Checkly _☁️	superblog _☁️	Vercel _☁️

- 💵 Financial Sponsor - ☁️ Infrastructure Support
## Contributing We're open to all community contributions! If you'd like to contribute in any way, please first read our [Contributing Guide](https://github.com/nextauthjs/.github/blob/main/CONTRIBUTING.md). ## License ISC

패키지	다운로드	Stars	크기	Issues	발행일	라이선스

next-auth	1,787,075	27,413	828 kB	537	9ヶ月前	ISC