@@iraniannuclearprogram3382 it is but its also way less complex than a lot of the stuff we have today. I am of the opinion that the insane complexity of auth systems these days makes them considerably less secure. Which is why this, though complex, is less complex then configuring / deploying a lot of the systems available today.
Cody thanks for this. I will extend this and make it fully functional like a complete auth email verification, password reset, 2 factor auth, google auth, GitHub auth and will add rate limiting
had to figure out lucia auth (with oauth) a few weeks back. it was a pain with the docs but overall the code is pretty simple, glad i set it up instead of relying on another auth library
Absolutely loved this video! It's short, concise, and straight to the point. Thanks for making such an informative piece so easy to understand. Great job Cody!
The 1 thing I don't like about Lucia is that it queries the DB every time you need to check for authentication. I guess that's not a Lucia issue, more of a DB Session issue, but if you're interracting with an api/trying to fetch data securely that's a lot of queries to make sure you get the data to the properly authenticated user every time.
I think it’s an issue when it’s actually a measurable issue. If your server and database are close in proximity (which they should honestly be), we are talking milliseconds to look up a single session record. You can also use reddis
@@SirMeowMeow I love sessions because they give you the ability to authorize users in real time unlike JWT tokens. I just don't know how bad it is for performance to have to do an additional query on every authorized request to the server. As Cody said, it's not an issue until it's measurable.
This is a benefit in certain applications, especially ones that need a high level of security. Sometimes you want to ban users/hackers and instantly revoke their access. This becomes even more important for fintech.
Thank you for the videos. Currently going through the online auction app video and get stuck early on as apparently Next.js, drizzle/postgres and Auth.js don't get on well together with error messages like the one below appearing: Module build failed: UnhandledSchemeError: Reading from "cloudflare:sockets" is not handled by plugins (Unhandled scheme). Hopefully switching the auth to Lucia will help as had no problems before putting the auth in.
Are there any advantaged of Next Auth at this point? Other than momentum? Looks like, thanks to artic, Lucia also has a ton of auth providers it can use.
Because building all those login flows took me a lot of time and I’m still fixing small bugs in that repo. It’s nice having something that basically works out of the box. But I guess that’s what you mean by momentum
Next-Auth is totally shit. It's TOO opininated and abstracted for just auth. It makes you crazy when little quirks pops up that you cannot fix until NextAuth team fixes or manually edit them. Easier Usage = More Abstraction = Less Customization, Less Flexible
sorry but I have to ask, what type of content do you want to make because what you are doing now is just so average and doesn't have any vision or goal you are just doing thing that doesn't have or give a plus to your subscriber. I am not trying to make fun of you or anything else it's just that I feel like what you are doing with this channel now is really different than what it was before ( before I was really feeling like you wanted to educate you viewer and help them become more senior )
Thanks for the feedback! I’m just trying some new content honestly. At this point I’ve made so many videos that I’m a bit burned out, so these type of videos are fun to challenge myself and some comments I’m getting show people like the concise nature of the videos.
Would love to see what you would come up with for a auth library tailored for drizzle and nextjs! Getting Lucia to work with the Next middleware is also a huge pain 🥲
