Auth just got WAY better

#t3stack #fullstack #webdevelopment

S/O Mir for the awesome edit 🙏

[luanhenning]

There's also keycloak out there which is open source, super complete and gives you stuff like auth screens, fine grained authorization including UMA, a nice interface for you to manage your users, different auth flows and so on.. There are libs for keycloak in virtually every framework out there and it's not expensive to run. I mean, you won't get away with aws free tier on lambda but I think I spend like, 20 dollars maintaining my auth service on ecs, rds and load balancing and we support multiple applications on it so I'm quite happy with that.

Just throwing that out there in case it helps someone

[anshnanda]

You need some really basic native code for Auth to work. They should work with Expo to make this happen as they've done all the hard work already.

[emanuelescarsella]

I was waiting for Sveltekit auth, love how fast the svelte environment is growing in support and functionalities 😍🥰

[TheIpicon]

I swear to god Theo!,
That's why you're my favorite developing channel.
I saw this video came out when was in the office and new I had to watch it once I got back home.
I asked in the prev video for you to say something about t3-turbo, and like magic, the next vid you mention it and address the big problem of auth it has.
Keep it up man <3

[lutfiikbalmajid]

Hi Theo, I am learning typescript, trpc and monorepo and use t3 turbo as my stack. it's supercool. thank you, as begginner it really helped me to setup the project. can't wait to see next auth support for react native :D

[Xe]

Your channel keeps me excited about learning new things. I can't wait to build things using unfamiliar, new tools like the t3 stack. Thank you for everything you do.

[mobile-mountain]

Thank you for the callout about React Native!

[zhenobiikuzo]

Authentication on mobile is definitely pain to work with. Hope that AuthJS mature in which mobile authentication will be made easy. I think this will be definitely happen

[spicynoodle]

Web devs still trying to figure out auth 30 years after it was solved

[dustatron]

I have been really enjoying these short tech videos. 🎉

[mechrono]

Really got my hopes up with that title but I think I'll be sticking with keycloak for now

[MrMcFyfey]

We need something like PHP-FIG and their PSRs. Standard interfaces to common problems which can be shared across frameworks. The JS ecosystem feels a bit disjointed where everyone's trying to create their own solutions to the same problem. This library looks great, don't get me wrong, but I feel we need a more official channel to create "standards". We have TC39 for core language support for things, but we need something on the userland level as well

[narendrapatwardhan]

Supertokens is a great backend-agnostic alternative

[cloudsquall]

Hi! What is your opinion on Keycloak? Seems to me to be a great solution for oauth. Or are you trying to keep the content more focused on the Javascript ecosystem?

[echobucket]

Does this support WebAuthn? I couldn't find any reference to it on the site.. Seems like an oversight.

[zombiefacesupreme]

OrJDev's Solid port works so well that people are quickly running out of reasons not to use SolidJS...

[siya.abc]

Looks promising. But no react-native support is a showstopper for me at the moment

[brag-]

I'm a Front End Dev and don't know much about auth. Looking at the documentation on their site all relates to meta-frameworks such as NextJS, Sveltekit and SolidStart - but would this work with more traditional jamstack, decoupled FE and BE stacks?

For example, would this work on if you ran AuthJS on the Front End in React, then had it talking to a custom API Backend built in node or .Net?

(React Auth is a pain).

[SharonStone-zork]

Ugg, tried next.js and ran in the opposite direction. Plain react is way better. Need SEO? just use pre-rendering

[thesunabsolute]

We just started migrating to Nextauth at work as we slowly move our CRAs to Nextjs. We ran into an awful issue where jest completely breaks, when testing a file using the unstable_getServerSession function. This means we can’t authenticate server side, and have to use the client library and mock that in tests. I brought this up to the maintainers, and they have no interest in fixing this. It’s yet another huge bummer for those of us who have to keep 100% test coverage at work.