railtrack VS next-auth

I use Prisma along with Supabase auth in my OSS project: https://github.com/noahflk/railtrack

If you're looking for something smaller and simpler, check out my project: https://github.com/noahflk/railtrack. Feel free to hit me up if you're looking for some contribution ideas.

This post picks up on an article I wrote earlier this year titled The good parts of Supabase. Wherein I reflected on my experience building Railtrack with Next.js and Supabase. If you're curious, you can read the whole post.

If you want to see a real-world example of what I described, check out my repository for Railtrack here: https://github.com/noahflk/railtrack.

My own repo using Supabase auth: https://github.com/noahflk/railtrack

In this article, I'll write about the experiences I had when using Supabase to build Railtrack. That’s why I’ll only talk about using Supabase for web development with Next.js with TypeScript that’s hosted on Vercel.

NextAuth.js is not perfect. One of the shortcomings is that it currently does not implement federated logout. This means that even if a user signs out of the Next.js app, he does NOT get signed out of the Cognito user pool client. As a consequence, the user is not really being logged out (i.e he is able to login again without providing the credentials). You can read more about this problem in this Github thread.

NextAuth for adding auth

Let's learn a bit about Descope and how to use it with Auth.js (next-auth) to protect our Next.js app with role-based access control (RBAC).

https://github.com/nextauthjs/next-auth/issues/5647#issuecom...

Next Auth CognitoProvider Internal Library: https://github.com/nextauthjs/next-auth/blob/v4/packages/next-auth/src/providers/cognito.ts

I mentioned this in an age-old discussion on NextAuth GitHub repo.

Authentication is a fundamental part of most web applications. Integrating authentication into your Next.js app can be simplified with NextAuth, a powerful authentication library that supports various authentication methods. However, the documentation around setting up NextAuth with the "Credentials" auth provider might not be as clear as you'd hope. My implementation is greatly enriched and partially based on Next-Auth docs and the following github thread.

For Auth: https://authjs.dev/ - works like a charm with Svelte https://authjs.dev/reference/sveltekit

NextAuth.js

I'm surprised nobody mentioned https://authjs.dev/