WTF is Okta?
An auth integrator, a pretty notable one, mostly (originally?) OAuth I think. Multiple people calling it a trash fire here came as a surprise to me, but I defer to their experience.
Okta's NextJS-0auth troubles
21–30 of 167 posts
Re: Okta's NextJS-0auth troubles
#22Is there any non shite managed oAuth solution with a free tier available?
Auth0 really is super easy and comfortable to integrate and I don‘t want to run my own keycloak or whatever.
Re: Okta's NextJS-0auth troubles
#23Okta is, if you may excuse my French, straight garbage.
Why if I may ask?
Re: Okta's NextJS-0auth troubles
#24IANAL but unfortunately, I think the fix itself shown here might be too simple to actually clear the bar for copyright eligibility. (And in fairness to copyright law, it is basically the only sane way to fix this.) That means that there's probably not much you can really do, but I will say this looks fucking pathetic, Okta.
I'm more confused by the fact that the OP freely submits a PR into an open source repo but then wants to use "copyright" because the code he submitted ended up being used under the wrong name, which was then corrected.
Re: Okta's NextJS-0auth troubles
#25You couldn't pay me a billion dollars to use Okta.
Re: Okta's NextJS-0auth troubles
#26IANAL but unfortunately, I think the fix itself shown here might be too simple to actually clear the bar for copyright eligibility. (And in fairness to copyright law, it is basically the only sane way to fix this.) That means that there's probably not much you can really do, but I will say this looks fucking pathetic, Okta.
I'm more confused by the fact that the OP freely submits a PR into an open source repo but then wants to use "copyright" because the code he submitted ended up being used under the wrong name, which was then corrected.
Why is it confusing to you to expect attribution?
Re: Okta's NextJS-0auth troubles
#27You couldn't pay me a billion dollars to use Okta.
Sadly many people will spend a million dollars to use Okta for their 10,000 logins/day (read: OIDC is not scary, and advanced central authorization features (beyond group memberships) are a big ole YAGNI / complexity trap.
Re: Okta's NextJS-0auth troubles
#28I LOVE LLMs as a learning tool. I HATE LLMs as a communication tool. I know, there are people with serious handicaps who benefit from LLMs in this area. If only I could talk to those people and not wade through all this other garbage.
Especially when the AI is being represented as a person, this to me is dishonest. Not to mention annoying, almost more-so than the number of different apps that think they are important enough to send me push notifications to fill out a survey (don’t even get me started).
Re: Okta's NextJS-0auth troubles
#29I've been quite happy with FusionAuth so far. Free to run on your own server, easy to understand and set up, easy to program against, reliable.
Re: Okta's NextJS-0auth troubles
#30Earlier quoted context omitted.
I'm more confused by the fact that the OP freely submits a PR into an open source repo but then wants to use "copyright" because the code he submitted ended up being used under the wrong name, which was then corrected.
Why is it confusing to you to expect attribution?
thats not the confusing part, its rather confusing to threaten to sue for copyright because of mistaken attirbution