Live data from Hacker News

Okta's NextJS-0auth troubles

joshua.hu

151–160 of 167 posts

Re: Okta's NextJS-0auth troubles

#151

I'm shocked. Where are all the "SSO companies handle edge cases you can't even imagine" people? It's been 24 hours.

If SSO were so easy to solve we wouldn't have a gazillion companies for it. It's probably easy enough if you are a really good engineer, but like 90% working in this industry aren't. Also you ever implemented OAuth2 or shudder SAML? Not how I would like to spend the one life I have been given.

Re: Okta's NextJS-0auth troubles

#152

Earlier quoted context omitted.

Auth providers are among the hardest systems to secure. It's not just a question of the underlying code having vulnerabilities - for companies with Internet logins, auth systems (a) are exposed to the internet, (b) are not cache-friendly static content, (c) come under heavy expected load, both malicious (the DDoS kind) and non-malicious (the viral product launch kind), (d) if they ever go down, the rest of the system…

I rather disagree on the difficulty of pulling it off. The problem space is well-defined and there aren't that many degrees of freedom in functional design. I'll concede there is some complexity in integrating with everything and putting up with the associated confusion. And granted the stakes are a little raised due to the nature of identity and access, and like you point out what could go wrong. Implementation is a…

> The C-level folks seem to think they are buying some kind of indemnity with these "enterprise" grade solutions, but there is no such thing.

Something you need to understand about executives, is that they're not really individual God-like figures ruling the world; at the end of the day they answer to their CEO, to their Boards, and want to look good to executive recruiters who might consider them for a C-level role at a larger company for higher pay; and a good many of them lead not-so-affordable lifestyles to keep up appearances among aforementioned folk and might be worse off in their personal finances than you.

All of which is just to say - "nobody got fired for buying IBM." It might be tragic, but going with peer consensus is what helps them stay with their in-crowd. The risks for departing from the herd (holding up deals on compliance concerns, possibly higher downtime for whatever reason, difficulty of hiring people who demand cheaper salaries but already know an Industry Standard Solution) are too high compared to the potential benefits (lower total cost of ownership, increased agility, better security/engineering quality, higher availability assuming for the sake of argument that is actually the case), particularly when increased agility and better quality are difficult to quantify, higher availability is hard to prove (Okta and peers don't exactly publish their real availability figures), and the difference in TCO is not enough to move the needle.

It's very rare to find executives who care more about their company's engineering than their peer group - folks who care that much rarely become executives in the first place.

Re: Okta's NextJS-0auth troubles

#153

Earlier quoted context omitted.

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.

People calling it trash and then recommending microsoft was an even bigger shock to the point where I am not convinced that those aren't microsoft AI bots astroturfing this post.

Yeah, wasn't essentially every Azure resource wide open for exploitation until august of this year?

https://dirkjanm.io/obtaining-global-admin-in-every-entra-id...

Re: Okta's NextJS-0auth troubles

#154

Earlier quoted context omitted.

The fact that they have a "stay signed in" checkbox that doesn't keep me signed in tells me all I need to know about these jokers. I love going through a bloated login process multiple times a day, apparently.

Microsoft/EntraID does this too. The famous "Keep me signed in" and "Don't show this message again" buttons that don't do what they say they do, ever. Maybe if enterprise sales decisions weren't made based on checklist and which account exec took them out on the best golf trip, we'd have better products.

Microsoft's EntraID "unsubscribe" functionality also doesn't do anything, evidently. The spam from them just keeps rolling in.

Re: Okta's NextJS-0auth troubles

#155

Earlier quoted context omitted.

Yeah I got a kick out of that. "We might have fixed your issue, if we didn't, open a new one because we took so long acknowledging this one".

Or 3 years later: can you verify this is still needed. Why on earth did I spend time in creating a reproducible example?

People move on from issues. You apply a workaround, and the fix is no longer needed. Not every issue opened needs a fix. We all have limited resources, and prioritize the most important stuff to fix.

Re: Okta's NextJS-0auth troubles

#156
post #141
post #140

Earlier quoted context omitted.

No provider has been able to match Auth0 actions unfortunately. Auth0 allows you to execute custom code at any point in the auth lifecycle and allow/deny based on that or enrich user attributes. Super useful when you have a legacy system that is hard to migrate away from. If anyone has any recommendations I'm all ears

I am not qualified to say whether Authentik can do all of what you need but it does allow custom python code in a lot of places. Perhaps you can ask whether what you need is available directly. They are very active in Discord.

(authentik maintainer here) It does! Also, not only in the authentication process, but also during individual authorization flows, and in a few other places as well, like when a user edits their settings, or whenever an event (basically whenever something happens in authentik) but that's more a reactive process than inline

Re: Okta's NextJS-0auth troubles

#157
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

"someone will look at this issue soon"

(3 years later...)

Re: Okta's NextJS-0auth troubles

#158
post #155

Earlier quoted context omitted.

Or 3 years later: can you verify this is still needed. Why on earth did I spend time in creating a reproducible example?

People move on from issues. You apply a workaround, and the fix is no longer needed. Not every issue opened needs a fix. We all have limited resources, and prioritize the most important stuff to fix.

A stalebot marks it as inactive because you didn't take 2mins of your time to write a thank you, it's been fixed with commit xyz.

That's what the critique is about, lack of communication and lack of acknowledgement. Ghosting people when they took the time to file an issue/bug report, with providing a PoC and test case is just rude behavior.

Re: Okta's NextJS-0auth troubles

#159
I've been (trying) to use Auth0 over the last few weeks, just as a PoC / "base" app scaffold.

My conclusion has been: for social and email login, you don't need things like Auth0. Just write it yourself.

You need: session management, account management (you'd already have this), and some simple social login pathways (PKCE etc). If you're an experienced engineer and take the time to do it properly, it's totally fine to "roll your own auth". Things like Auth0 and Firebase Auth are built for nobody and make life more difficult.

Any SaaS service that saves you like Basically, don't cargo-cult things just because everyone says you should. You should feel the "aha" for why you need to introduce a 3rd party thing.

Re: Okta's NextJS-0auth troubles

#160

Earlier quoted context omitted.

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

We evaluated them a while ago but concluded it was amateur-hour all the way down. They seem to be one of those classic tech companies where 90% of resources go to sales/marketing, and engineering remains "minimum viable" hoping they get an exit before anyone notices.

Okta is already public and has been for years. They had an exit already. For whatever reason, many large organizations trust them.
Post reply on HN