About next-auth
Next-auth is a powerful authentication solution specifically designed for Next.js applications, simplifying the process of adding authentication to these modern web projects. This npm package integrates seamlessly with Next.js, providing a ready-to-use system that supports various login mechanisms, including email, password, OAuth, and more. One of the primary benefits of using next-auth is its adaptability to different authentication providers like Google, Facebook, Twitter, and GitHub, making it incredibly versatile for developers looking to implement robust and secure authentication in their applications. Additionally, next-auth ensures security by handling sessions and tokens effectively, thereby safeguarding user data from potential threats.
For developers looking to incorporate next-auth into their Next.js projects, the process is straightforward with the command npm install next-auth. This command installs the necessary package to begin integrating sophisticated authentication systems into your applications. The implementation of next-auth not only enhances the security features of your web applications but also offers a better user experience by supporting session management and JSON Web Tokens (JWT). This module also provides hooks and utilities to interact with the authentication state throughout your application, ensuring that developers have full control over user sessions and authentication flows. By using npm install next-auth, developers can leverage these advanced features to build more secure, efficient, and user-friendly web applications.
Next-auth comes with comprehensive documentation and a supportive community, making it an excellent choice for developers at all levels. Its compatibility with various databases and the ability to customize authentication flows allows for flexibility in development, catering to a wide array of project requirements. This node module not only streamlines authentication processes but also contributes to the scalability and maintainability of Next.js applications, proving its indispensability in modern web development.
Dependencies
Core dependencies of this npm package and its dev dependencies.
@actions/core, @balazsorban/monorepo-release, @playwright/test, @types/node, @typescript-eslint/eslint-plugin, @typescript-eslint/parser, @vitest/coverage-v8, @vitest/ui, eslint, eslint-config-prettier, eslint-config-standard-with-typescript, eslint-plugin-import, eslint-plugin-jsdoc, eslint-plugin-node, eslint-plugin-promise, eslint-plugin-react, eslint-plugin-svelte, fake-smtp-server, prettier, prettier-plugin-svelte, prettier-plugin-tailwindcss, svelte-eslint-parser, turbo, typescript, utils, vite, vitest
Documentation
A README file for the next-auth code repository. View Code
Auth.js
Authentication for the Web.
Open Source. Full Stack. Own Your Data.
Auth.js is a set of open-source packages that are built on standard Web APIs for authentication in modern applications with any framework on any platform in any JS runtime.
Need help? See authjs.dev for the documentation, or
join our community on Discord
.
Sponsored Looking for a hosted alternative? Use Clerk →
Features
Flexible and easy to use
- Designed to work with any OAuth service, it supports 2.0+, OIDC
- Built-in support for many popular sign-in services
- Email/Passwordless authentication
- Bring Your Database - or none! - stateless authentication with any backend (Active Directory, LDAP, etc.)
- Runtime-agnostic, runs anywhere! (Vercel Edge Functions, Node.js, Serverless, etc.)
Own your data
Auth.js can be used with or without a database.
- An open-source solution that allows you to keep control of your data
- Built-in support for MySQL, MariaDB, Postgres, Microsoft SQL Server, MongoDB, SQLite, etc.
- Works great with databases from popular hosting providers
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 used, they are encrypted by default (JWE) with A256CBC-HS512
- 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
Advanced configuration allows you to define your 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 can sign in and how often sessions have to be re-validated.
TypeScript
Auth.js libraries are written with type safety in mind. Check out the docs for more information.
Security
If you think you have found a vulnerability (or are not sure) in Auth.js or any of the related packages (i.e. Adapters), we ask you to read our Security Policy to reach out responsibly. Please do not open Pull Requests/Issues/Discussions before consulting with us.
Acknowledgments
Auth.js is made possible thanks to all of its contributors.
Sponsors
We have an OpenCollective for companies and individuals looking to contribute financially to the project!
Clerk
💵
|
FusionAuth
💵
|
Beyond Identity
💵
|
Stytch
💵
|
Prisma
💵
|
Lowdefy
💵
|
Vercel
💵☁️
|
Descope
💵
|
Checkly
☁️
|
superblog
☁️
|
Netlight
☁️
|
- 💵 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.
[!NOTE] The Auth.js/NextAuth.js project is not provided by, nor otherwise affiliated with Vercel Inc. or its subsidiaries. Any contributions to this project by individuals affiliated with Vercel are made in their personal capacity.
License
ISC