calendso VS next-auth

Cal (https://github.com/calendso/calendso)

AuthJS - still not sure why NextAuth and AuthJS are still separate things? Combine them please, including the website. This is confusing!

Auth.js

Azure AD can be configured to provide roles and group membership information as part of the OpenID Connect ID tokens (encoded as JWTs) it returns during the auth flow. It doesn't look like the NextAuth Azure AD provider supports reading these claims from the ID token, but it looks like you can configure a custom provider instead that has access to the ID token. You'll probably have to play around with the options a bit, but it looks like setting idToken: true should make the claims from the ID token available in the profile function you define in the NextAuth custom provider.

https://github.com/nextauthjs/next-auth/pull/3474 https://github.com/nextauthjs/next-auth/issues/1110 and https://github.com/stevesouth/next-auth-react-native-expo (his attempt 3 should be something doable)

So it pushes people with limited backend experience into the arms of Supabase, Pocketbase, Whateverbase and companies like Netlify and Vercel. And then there's the rise of stuff like [Auth.js](https://authjs.dev/)

Furthermore, an exiting release is on the way, with first-class support for the App Router. You can peek art NextAuth.js v5 here: https://github.com/nextauthjs/next-auth/pull/7443 👀

Authentication Library

Auth.js, just like Clerk, is used for authentication in web applications. It is an open-source authentication solution that was first developed for only Next.Js applications but now supports other frameworks like Svelte and SolidJS, with a staggering number of database integrations.

Note: There's a super weird bug(?) when using NextAuth on Firebase Hosting. Firebase doesn't allow multiple session keys due to it stripping all cookies besides __session. To keep a persistent session, you have to rename your session cookie so that Firebase can persist it, but you only have 4096 bytes to fit your session in it.