https://github.com/nabind47/authjs

Authentication in Next.js 14 with Auth.js and server actions having credentials as well as socials signin along with forgot password and 2FA.
https://github.com/nabind47/authjs

authjs nextjs14 prisma shadcn-ui

Last synced: about 2 months ago
JSON representation

Authentication in Next.js 14 with Auth.js and server actions having credentials as well as socials signin along with forgot password and 2FA.

• Host: GitHub
• URL: https://github.com/nabind47/authjs
• Owner: nabind47
• Created: 2023-12-31T11:11:59.000Z (about 1 year ago)
• Default Branch: master
• Last Pushed: 2024-07-22T16:40:06.000Z (6 months ago)
• Last Synced: 2024-07-22T20:13:30.588Z (6 months ago)
• Topics: authjs, nextjs14, prisma, shadcn-ui
• Language: TypeScript
• Homepage:
• Size: 1.97 MB
• Stars: 18
• Watchers: 1
• Forks: 3
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# [Authjs](https://authjs.dev/)

![login](public/login.png)

![admin](public/admin.png)

![settings](public/settings.png)

> [Edge compatibility](https://authjs.dev/guides/upgrade-to-v5?authentication-method=middleware)

> while `NextAuth.js` strictly uses standard Web APIs (and thus can run in any environments that supports that), some `libraries/ORM` packages that you rely on might not be ready yet. In this case, you can split the auth configuration into multiple files.

> [Upgrading V5](https://authjs.dev/guides/upgrade-to-v5?authentication-method=middleware#new-features)

## [Callbacks](https://authjs.dev/guides/basics/callbacks#:~:text=Callbacks%201%20Sign%20in%20callback%20Use%20the%20signIn,3%20JWT%20callback%20...%204%20Session%20callback%20)

Callbacks are asynchronous functions you can use to control what happens when an action is performed. Callbacks are extremely powerful, especially in scenarios involving JSON Web Tokens as they allow you to implement access controls without a database and to integrate with external databases or APIs.

```ts

  callbacks: {

    async signIn({ user, account, profile, email, credentials }) {

      return true

    },

    async redirect({ url, baseUrl }) {

      return baseUrl

    },

    async session({ session, user, token }) {

      return session

    },

    async jwt({ token, user, account, profile, isNewUser }) {

      return token

    }

  }

```

> If you want to pass data such as an Access Token or User ID to the browser when using JSON Web Tokens, you can persist the data in the token when the jwt callback is called, then pass the data through to the browser in the session callback