GitXplorerGitXplorer
n

next-auth-starter

public
0 stars
0 forks
0 issues

Commits

List of commits on branch main.
Verified
6e4de7214852d3067a48ba27f6dd24623103ae0c

Update SETUP-1.md

nnitya committed 2 years ago
Unverified
30467cd3d0d4191d5cbda9edd6f08d2dfc7a074f

ci: add Azure Static Web Apps workflow file

nnitya committed 2 years ago
Unverified
28042efba4ab513e8c3e91ca901a77d76cd9da1c

Updating Setup with planned work

nnitya committed 2 years ago
Unverified
38bb285232d7ce2aeec5330cac8dc54c76573af6

Initial Setup to explore SWA deployment

nnitya committed 2 years ago
Unverified
0f39c6c9baed37f06c1bc5884e6e4b62650ae0dc

Initial working demo: next-auth with GitHub provider

nnitya committed 2 years ago
Verified
9bc84f4d64eed16465fb5f4bc2097ae1b7d22ca2

Initial commit

nnitya committed 2 years ago

README

The README file for this repository.

The example repository is maintained from a monorepo. Pull Requests should be opened against nextauthjs/next-auth.


NextAuth.js Example App

Open Source. Full Stack. Own Your Data.

npm Bundle Size Downloads TypeScript

Overview

NextAuth.js is a complete open source authentication solution.

This is an example application that shows how next-auth is applied to a basic Next.js app.

The deployed version can be found at next-auth-example.vercel.app

About NextAuth.js

NextAuth.js is an easy to implement, full-stack (client/server) open source authentication library originally designed for Next.js and Serverless. Our goal is to support even more frameworks in the future.

Go to next-auth.js.org for more information and documentation.

NextAuth.js is not officially associated with Vercel or Next.js.

Getting Started

1. Clone the repository and install dependencies

git clone https://github.com/nextauthjs/next-auth-example.git
cd next-auth-example
npm install

2. Configure your local environment

Copy the .env.local.example file in this directory to .env.local (which will be ignored by Git):

cp .env.local.example .env.local

Add details for one or more providers (e.g. Google, Twitter, GitHub, Email, etc).

Database

A database is needed to persist user accounts and to support email sign in. However, you can still use NextAuth.js for authentication without a database by using OAuth for authentication. If you do not specify a database, JSON Web Tokens will be enabled by default.

You can skip configuring a database and come back to it later if you want.

For more information about setting up a database, please check out the following links:

3. Configure Authentication Providers

  1. Review and update options in pages/api/auth/[...nextauth].js as needed.

  2. When setting up OAuth, in the developer admin page for each of your OAuth services, you should configure the callback URL to use a callback path of {server}/api/auth/callback/{provider}.

e.g. For Google OAuth you would use: http://localhost:3000/api/auth/callback/google

A list of configured providers and their callback URLs is available from the endpoint /api/auth/providers. You can find more information at https://next-auth.js.org/configuration/providers/oauth

  1. You can also choose to specify an SMTP server for passwordless sign in via email.

4. Start the application

To run your site locally, use:

npm run dev

To run it in production mode, use:

npm run build
npm run start

5. Preparing for Production

Follow the Deployment documentation

Acknowledgements

Powered By Vercel

Thanks to Vercel sponsoring this project by allowing it to be deployed for free for the entire NextAuth.js Team

License

ISC