Cloudflare launched self-managed OAuth for all

tterryds about 3 hours ago 25 commentsRead Article on blog.cloudflare.com

DE version is available. Content is displayed in original English for accuracy.

⚡ Community Insights

Discussion Sentiment

69% Positive

Analyzed from 912 words in the discussion.

Discussion (25 Comments)Read Original on HackerNews

zaptheimpaler•about 1 hour ago

Oauth and enterprise auth has to be the worst thing ever made, it might be the most confusing and frustrating part of dealing with the cloud. Even the AI tools took a year to just get basic Oauth working on headless systems without assuming you could open a browser. If they're going to go down the auth rabbit hole with RBAC/IAM/Workload identities?/service accounts and all the trash the big cloud providers have, I just hope to god they leave in the simple shit for personal use. I just want a damn API key, I keep it a secret and revoke if necessary and don't need 10000 layers of auth bullshit tangled up in every layer of every platform.

willtemperley•41 minutes ago

What I don't understand is why OAuth is rarely talked about in a privacy context, however your OAuth provider knows all the sites you log into and when.

It's a privacy nightmare.

spaghettifythis•35 minutes ago

Though given most people use gmail or outlook, the two main oauth providers (Google and Microsoft) will know anyway

willtemperley•29 minutes ago

True they'd know which sites you've signed up to, but not the login times, unless the service emails you every time you log in.

jurgenaut23•44 minutes ago

I am tempted to agree with you because I could never quite wrap up my head around it, but I never had to implement OAuth beyond a brief skim through the doc for my own understanding. I always thought this complexity was there for some good reason (security?).

messe•18 minutes ago

> was there for some good reason (security?).

To cover the myriad of (sometimes downright stupid) requirements that large enterprises have.

sandeepkd•about 2 hours ago

Not sure whats the play here, there is no world where this can turn out good. Cloudflare is more or less infrastructure provider, this idea of some user delegating permissions to their account to some third party client for infrastructure is ripe for abuses. If companies like AWS are not doing it then its for a good reason.

codebje•about 2 hours ago

How different is this to, eg, the Google developer program, in which I can create a new OAuth client for Google users?

ok_dad•about 2 hours ago

Do you understand what OAuth is? It’s like an API key but less likely to be abused. This is a good thing. It helps security in many ways and makes security flows more safe than carrying around a token.

usr1106•40 minutes ago

Maybe he doesn't. And I know that I don't (at least not in depth). And that's the frightening thing here. Using a protocol that many don't understand for access to valuable resources

necovek•about 1 hour ago

I thought I understood what Oauth was (a standardized protocol to provide per-client access keys), but this article confuses me.

What's a "self-managed" Oauth here? What is access is being granted to, who are the clients, who are the partners...?

Anyone care to elaborate?

Groxx•about 1 hour ago

>Earlier this month, we announced self-managed OAuth, making it easier for customers to create and manage their own OAuth clients for delegated access to the Cloudflare API.

They're letting you host an OAuth system to approve/deny access to your own resources, so you can build whatever logic you like, rather than waiting on them to allow you to do X under Y conditions. Essentially "log into CloudFlare" -> CF sees you're using this self-managed OAuth -> redirect to your OAuth -> CF trusts your response, and approves access to your account if you approve access.

asdf88990•about 2 hours ago

Cloudflare turning into a Cloud platform is undoing what it was really doing well: making small clouds and diy hosting manageable in the hostile web environment.

Once their revenue from Cloud services overtakes their core offering, bye bye Cloudflare free and so on.

rozenmd•41 minutes ago

Cloudflare free is the business model: https://blog.cloudflare.com/cloudflares-commitment-to-free/

asdfsa32•22 minutes ago

If you carefully read the article, it just explain how it is an economic decision, and one which sooner or later will be no longer the case once they can capitalise on with anything above free, which is the lowest of the lowest bars.

But even to entertain this is crazy, not because of decades of history of capitalist and market enterprise in general, but very specific cases of Technology Companies starting with these kind of feel good ideas and declaring "Don't be evil" or things like " access, safety, and shared prosperity" as their core ideals, turn into absolute panopticon and collaborate with unjust killing of women and children in less than a decade.

The market isn't for free.

reed1234•about 2 hours ago

I doubt it. It’s cheap to run and a good funnel

weird-eye-issue•about 1 hour ago

> Once their revenue from Cloud services overtakes their core offering, bye bye Cloudflare free and so on.

Wait so what do you think their core offering is?

kordlessagain•14 minutes ago

Man-in-the-middle everything.

asdfsa32•30 minutes ago

DDoS Protection?

gnabgib•about 3 hours ago

Title: Unlocking the Cloudflare app ecosystem with OAuth for all

xyzzy_plugh•about 2 hours ago

This is such a weird blog post.

It's full of technical details, but I'm really not sure who they're for. There's nothing particularly novel or impressive. If anything the fact that it took them this long should be embarrassing. They pad it out with a table of stats that are just kind of meh? Congrats I guess for releasing something without burning the house down?

As an on-and-off customer of theirs I tried to quickly skim for some of the details that would impact me, the theoretical end-user, but the vast majority of TFA is just about how they pulled off this apparent feat of engineering.

I'm not trying to be pessimistic, and I don't fault the author (but I question the culture). I honestly don't get who this is for.

For the record this is something they should have had... at least six or seven years ago?

parsadotsh•about 2 hours ago

I for one appreciate them sharing this and found it a very interesting read. Many of us don't have experiences at companies at this scale and so it's nice whenever I get to read about what happens behind the scene.

xyzzy_plugh•about 1 hour ago

Usually I expect an eng blog post to be a recruitment vehicle, wherein the authors articulate a really hard problem they solved, or some novel approach they took, or the cool new open source project they released (for their future SaaS play).

But this is so mundane it bothers me in a way I find surprising. It's more about how they made some questionable choices in the past and how they finally paid off that technical debt. Is it interesting? Perhaps I am just getting old and jaded.

What I find odd is how light TFA is on actual details as to what it is they shipped.

This is the kind of thing I'd ship internally to the org as part of a weekly update or something, but not what I'd expect on a public-facing corporate blog.

system2•about 1 hour ago

I hope Cloudflare does not turn into Google, with so many different things that they will eventually kill all of these services randomly because of the maintenance cost.

holistio•about 1 hour ago

I still kind of think of Cloudflare as "big ass CDN".

I can't keep track of all the new things they do. Something-something-R2? Maybe?