Okta's NextJS-0auth troubles

#1

Post by ramimac » Tue, Nov 18, 2025, 10:17 AM UTC

Re: Okta's NextJS-0auth troubles

#2

Post by dovys » Tue, Nov 18, 2025, 1:22 PM UTC

You're either free OSS that gets flooded with AI slop PRs to overwhelm maintainers or you're a corporate OSS that uses AI slop to frustrate contributors. Are there any positive stories I've not seen?

Re: Okta's NextJS-0auth troubles

#3

Post by cedws » Tue, Nov 18, 2025, 4:04 PM UTC

That’s funny. I spotted a similar issue in their Go SDK[1] a few years back. I was pretty appalled to see such a basic mistake from a security company, but then again it is Okta. [1]: https://github.com/okta/okta-sdk-golang/issues/306

Re: Okta's NextJS-0auth troubles

#4

Post by DetroitThrow » Thu, Nov 20, 2025, 6:14 PM UTC

Security companies that prioritize bugs being sold rather than be reported will eventually blow up. Good luck Okta shareholders.

Re: Okta's NextJS-0auth troubles

#5

Post by Will-Reppeto » Thu, Nov 20, 2025, 6:47 PM UTC

[flagged]

Re: Okta's NextJS-0auth troubles

#6

Post by jonathaneunice » Thu, Nov 20, 2025, 6:47 PM UTC

cedws wrote: post #3

That’s funny. I spotted a similar issue in their Go SDK[1] a few years back. I was pretty appalled to see such a basic mistake from a security company, but then again it is Okta. [1]: https://github.com/okta/okta-sdk-golang/issues/306

> I was pretty appalled to see such a basic mistake from a security company, but then again it is Okta.

Oh. Em. Gee.

Is this a common take on Okta? The article and comments suggest...maybe? That is frightening considering how many customers depend on Okta and Auth0.

Re: Okta's NextJS-0auth troubles

#7

Post by hypeatei » Thu, Nov 20, 2025, 6:51 PM UTC

I think GitHub should allow disabling PRs. I don't believe most big corporations are interested in dealing with fly-by contributions because it might make them look bad or be riddled with quality issues.

Also some projects like the Linux kernel are just mirrors and would be better off with that functionality disabled.

Re: Okta's NextJS-0auth troubles

#8

Post by roze_sha » Thu, Nov 20, 2025, 6:52 PM UTC

Will-Reppeto wrote: post #5

[flagged]

Is this ai generated

Re: Okta's NextJS-0auth troubles

#9

Post by transcriptase » Thu, Nov 20, 2025, 6:55 PM UTC

roze_sha wrote: post #8

Will-Reppeto wrote: post #5

[flagged]

Is this ai generated

More than likely. Look at the users most recent comment with the random “ at the end too.

Re: Okta's NextJS-0auth troubles

#10

Post by jchw » Thu, Nov 20, 2025, 6:56 PM UTC

IANAL 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.