We gotta start somewhere, and Next.js is popular right now — we're working on some cool non-Next stuff though (eg. auth proxies that can provide user info to any server, which we can hopefully launch within the next weeks).

Regardless, the focus of this blog post is on OAuth, not Stack Auth =) I appreciate the feedback though.

Yes, the blog post is very informative (although the images do not scale well on mobile).

My previous post was based on the phrase “open-source Auth0” (in your blog post) and we use Auth0 (and don’t like it). But all of out apps are react, not nextjs

I’m currently evaluating Auth0 and other similar services with a view to migrating from Cognito. May I ask what you don’t like about it?

(plugging my startup- hope that’s ok!)

we’ve had lots of folks migrate from Cognito to WorkOS. Lots of more features, modern API, and better extensibility.

More here: https://workos.com/docs/migrate/aws-cognito

Thanks for this, I will work through it.

If you happen to be looking for future blog posts:

One thing that would help me and probaby a lot of other people is to show the flow using API calls in Postman.

Currently I am planning to reverse engineer example code in an unfamiliar framework...

Wheels should be reinvented once in a while, just to make sure there's not a better way to do it. They just shouldn't be reinvented by everyone all the time when there are perfectly good solutions available.

> And why do most of these “Auth0” replacements only implement nextjs?

Probably because it's hard to support different languages. Even if all the replacements support OIDC (not a given) there are still subtle differences in implementation and integration.

That said, check out FusionAuth! We have over 25 quickstarts covering a variety of languages and scenarios. (I'm employed by them.)

https://fusionauth.io/docs/quickstarts/

We're free if you don't need advanced features and run it yourself, as documented here: https://fusionauth.io/blog/fusionauth-on-fly-io