20 ms·
OAuth Has Ruined Everything
- megaman821 11y agoThe author has actually just described a standard called Open ID Connect, which is built upon OAuth 2.0 and JWT. Those same steps can be used to authenticate with Microsoft accounts.
- devsquid 11y agolol.... I implemented both Google and Facebook's Oauth as a complete noob. It was super easy. Like literally its a button and a few lines on the client and a few GET/POST requests to double check the user says who they say they are on the server side.
- pfooti 11y agoSo I guess I'll be the goose at the party, or whatever the metaphor is for the person who disagrees with the headline. First of all: author complains about spec and then pitches their in-house (non-free) solution. This is something like https://xkcd.com/927/ https://xkcd.com/927/ in spirit, at least. Second of all: .NET notwithstanding, there's plenty of other decent libraries for handling OAuth. Personally, I use hapijs/bell. Third of all: I like OAuth. I like the way they handle scopes, I like the way I can just authenticate a user by grabbing an identifier from some third-party provider (and link together multiple social logins). I like how I can ask for other stuff via scope grants. I also like how I have lots of control over what my applications do. I can grab the oauth token from [provider] and generate my own token-based authentication system for accessing my API. I can do it all in the client, or I can use a client-server workflow. I can grab refresh tokens and keep the oauth grant alive for longer if needs be (for example: I let my identity tokens expire and only refresh them when the user needs to open the attach file from drive widget, and I do that refresh request on the back end). I'm not super-wild about relying on a single OAuth provider, which is why I typically allow different IdPs, and depending on the project will also do regular username / password, but man I love when I don't have to worry about dealing with authentication. Let google handle "I forgot my password" errors, let me focus on the rest. I have to be careful, as there are pitfalls: you can't do token auth if you're not always on https, since OAuth basically falls down if someone gets on your transport stream. You have to understand how the system works and how to use it. In other words: you have to be a programmer to use it. That's not to say OAuth is perfect. But it by no means has ruined everything. For example: would I rather have a better, more intuitive federated authentication and ID validation system, or would I rather Apple allow multiple browsers on their iOS platform so I can start using modern web tech instead of dealing with mobile safari's foibles? I'd say mobile safari is ruining things far more than OAuth, at least IMO.
- devsquid 11y agoYea. I found Oauth to be pretty straight forward and easy to figure out. I'm also pretty new to this game, so I couldn't imagine people with more experience than me having difficulty implementing it properly. The blog posts seems more like a clever marketing scheme than a real rant against setting it up.
- intrasight 11y agoI agree. In fact I would say "OAuth has made possible everything". Sure, something better will come along soon. But I'm quite happy we have OAuth now.
- rdsubhas 11y agoYep. Projects like everyauth as a multi-oauth client (https://github.com/bnoguchi/everyauth https://github.com/bnoguchi/everyauth) and OAuth2orize as an oauth server (https://github.com/FrankHassanabad/Oauth2orizeRecipes https://github.com/FrankHassanabad/Oauth2orizeRecipes) have made our lives very simpler in recent projects. I agree that OAuth is complicated and not that great, but its definitely a huge step forward from what we had to deal with earlier!
- taspeotis 11y agoThe post complains about the dearth of resources for authenticating an ASP.NET application to Google via OAuth 2 but ... Microsoft do that for you [1]. [1] https://www.nuget.org/packages/Microsoft.Owin.Security.Google/ https://www.nuget.org/packages/Microsoft.Owin.Security.Googl... I think it's thinly veiled advertising. At Telerik, we’re all about making the developer experience better, and I can’t think of a worse development experience than OAuth. Telerik Backend Services was designed to mitigate this sort of nonsense. Let’s take a look at how it works.
- muzmath 11y agoA typical low quality Telerik rant followed up with product placement. After being forced into using Kendo UI, I will never willingly use one of their products.
- elijahlofgren 11y agoI have really enjoyed Kendo UI but am now just getting into a world beyond jQuery based frameworks, what were you comparing Kendo UI to that you liked better?
- muzmath 11y agoMy hate for Kendo is very biased, due to the fact that my use of Kendo was not by my choice, and I quickly left the company for many reasons - one of them being that the overall technical prowess was very low (programming was seen as a cost center there so this is no surprise). ... I view Kendo as an attempt to create an all in one solution to UI, primarily used by 'enterprise' type companies (i.e. not very tech savvy). This is a fine goal but... I hate the imperative syntax. The Razor based Imperative syntax for creating Kendo components is god awful. Simply look at what configuring one of those ridiculous grids imperatively looks like. But you say, there is declarative syntax! Until you start needing some of the edge cases and you will start to find missing documentation that exists in the imperative syntax documentation but not declarative. There are countless subtle differences just enough so that you may spend hours trying to fix a damn kendo grid. MVVM Kendo: Kendo has a half baked solution for MVVM which does not compare to other open source solutions. You are better off with using a more standard open source solution where there is an actual community surrounding the development. I used to keep a list of all of the bugs I had found upon using declarative MVVM kendo, but it's been a long time and I will absolutely never work anywhere that uses Kendo again so I brain dumped all of my specific kendo knowledge. When all things are considered, KendoUI trys to hold your hand very tightly, and it does a great job and spinning up complicated grids. When you want something that isn't explicitly accounted for, or combine things in novel ways - you are going to be in a world of hurt. UI Kits I like better: I think you will be better off with any widely used UI kit. I've played around with Material Design and Twitter Bootstrap. These are both significantly lighter weight than Kendo. Over All Frameworks/Libraries to replace the MVVM portion: I've fallen favor of React as opposed to Kendos attempt at databinding. There's tons of great resources out there for React so I won't even try to go into it but it's been a pleasure.
- reimertz 11y agoIf you feel it's boring to learn how to authenticate your users, from a security point, you should probably not do it. Meteor.js has a very beatiful way of solving this and I strongly recommend everyone who wants to authenticate users but don't want to know how it works to try Meteor.js.
- dvanduzer 11y agoOAuth is for authorization, not authentication.
- aikah 11y ago"Alternatives" such as OpenID and Persona flopped though. So it is not like there is much choice anyway AFAIK.
- andersriutta 11y agoOpenID Connect [0] is "an interoperable authentication protocol based on the OAuth 2.0 family of specifications." Note this is a different protocol from OpenID 2.0. [0] http://openid.net/connect/faq/ http://openid.net/connect/faq/
- dvanduzer 11y agoYes, OpenID Connect is a protocol that builds on the authentication features developed from previous versions of OpenID, and merges it with the authorization features defined via OAuth. It is all laid out fairly clearly in this comment on the original blog post, for example: http://developer.telerik.com/featured/oauth-has-ruined-everything/?imm_mid=0dac54&cmp=em-web-na-na-newsltr_20151021#comment-2285976650 http://developer.telerik.com/featured/oauth-has-ruined-every...
- crashedsnow 11y agoThat may have been the intent, but in a (very, very) large portion of cases the developer simply wants a way to verify identity claims. That is, verify that you are who you claim to be. 3rd party identity providers (Facebook et. al.) are a convenient way to do this, for both the user and the developer (maintaining your own passwords is a pain etc). It's coincidence that these providers choose oAuth for this, but you still end up with oAuth for identity, not auth'z.
- hlieberman 11y agoThere was a fantastic protocol that really could have replaced much of the problems that OAuth has, while providing its users more privacy: BrowserID, aka Mozilla Persona. Sadly, it got effectively gutted by the Mozilla Foundation due to lack of use, and even Mozilla has stopped using it most places in favor of Firefox Accounts.
- deleted 11y ago[deleted]
- hlieberman 11y agoIndeed, it does! I'm a little bit scared of it, though, to be honest. It's a giant of a protocol, and has a lot of moving parts. I'm worried that implementation is going to be so complicated, it'll end up as OAuth 3.0.
- guelo 11y agoMozilla only really gave it like a year before they pulled the devs. Probably to work on Hello and Pocket or something worthless like that.
- scrollaway 11y agoLet's be fair to Mozilla. Pocket is a separate company, and Hello is definitely not worthless in the grand scheme of things... merely less useful.
- cobweb 11y agoOff topic: Pocket turned up in my Firefox. I don't even know what it is, and why it's there. It weirdly replaced my Readability icon. (Goes off to read). Okay so it's ReadItLater. Which I assume is something like Readability. Or is it bookmarking or shared bookmarking? What is it and why is it in Firefox? Mozilla pared down their suite to a barebones browser. With the option of add-ons. Now it looks as if Firefox are adding services/features back in the browser. I think I'd prefer Mozilla work on a better bookmarking/history api. And hopefully given a good API, I could drop in a provider that I could set up in any browser.
- tiles 11y agoBring back Mozilla Persona: https://www.mozilla.org/en-US/persona/ https://www.mozilla.org/en-US/persona/
- ghshephard 11y agoI for one, am very happy about this. Difficulty with centralized logins encourages sites to maintain their own ID system, which, along with mailinator and tools like 1password, allows people to trivially generate separate logins/email accounts/passwords for each site that they visit.
- hlieberman 11y agoThat seems rather like throwing out the baby with the bathwater. If there was a strong federated identity provider, there would be less crappy passwords out there. Despite what it might seem like from HN users, the vast majority of people don't use password managers.
- arbitrage 11y agoIf there was a strong federated identity provider, there would be one massive target for abuse and attack. If there was a well written protocol and library to help with the independent federation of identities, that could be used by anyone, that would truly help the security of the vast majority of people.
- Pharaoh2 11y agoOh, do you mean like the massive target for abuse and attack that are password managers?
- dvanduzer 11y agoPassword management software centralizes the credentials of a given user. But each instance of the credential database is highly decentralized. So it's only a massive target if you then recentralize those credential databases on a cloud storage service, for example. Attacking the security of a password management system is different than stealing the credential database.
- deleted 11y ago[deleted]
- gkoberger 11y agoOAuth2 isn't a spec. It's merely loose guidelines. I've worked with dozens of OAuth2 providers, and I am yet to see two implementations that are interchangeable. That's the point of a spec! All implementations required custom code. It's absolutely insane. We need a better way. Whatever replaces OAuth2 needs to be much more strict in how it should be implemented.
- deathanatos 11y agoIn what way is OAuth2 not a spec? Both your comment and the article leave me wanting some concrete complaint…
- gkoberger 11y agoThe definition of a spec is "an act of describing or identifying something precisely or of stating a precise requirement." OAuth2 is really just a collection of suggestions. Here's some examples: * What field should the token be passed back as? * What are the token + auth URLs? * Should there be a separate profile URL, or is user data passed back with the token? * What field is the email address passed back as? The user's name? * Are refresh tokens used? How? These are just things I literally ran into today. There's hundreds more things like this. And on top of that, pretty much every single OAuth provider requires custom code: http://passportjs.org/ http://passportjs.org/
- mikesickler 11y agoYep- don't get me started: * Do access token expire and need to be refreshed at all? * Are scopes used? * Appropriate header values? * Can redirect URI be overrided in auth request (my personal favorite)?
- makkes 11y ago* Do access token expire and need to be refreshed at all? => https://tools.ietf.org/html/rfc6749#section-4.2.2 https://tools.ietf.org/html/rfc6749#section-4.2.2 * Are scopes used? => https://tools.ietf.org/html/rfc6749#section-3.3 https://tools.ietf.org/html/rfc6749#section-3.3 * Appropriate header values? => https://tools.ietf.org/html/rfc6749#section-7 https://tools.ietf.org/html/rfc6749#section-7 as well as https://tools.ietf.org/html/rfc6750 https://tools.ietf.org/html/rfc6750 * Can redirect URI be overrided in auth request (my personal favorite)? Sth. like https://tools.ietf.org/html/rfc6749#section-10.6 https://tools.ietf.org/html/rfc6749#section-10.6 ?
- whatusername 11y agoSo no mention in the article of Open ID Connect?
- ForHackernews 11y agoIt's even more inexcusable because half of what he's complaining about (id_tokens, JWT, aud, etc.) is actually OpenIDConnect and isn't even part of the OAuth2 spec.
- rocha 11y agoIt seems like the author doesn't realize that. OpenID Connect fills the specification holes in OAuth 2.0 that he is complaining about. If he had used an OpenID Connect library, his life would have been a lot easier.
- jakeway 11y agoNo there was no mention. Plus, Open ID Connect is built on top of OAuth, so I don't think the author is a big fan of connect either.
- the8472 11y ago> Registering for applications is a tax that nobody really wants to pay It's quite the opposite for me. I vastly prefer a simple signup than being offered to sign in with an account on a 3rd party site that I don't have or don't want associated to another site. I like to wear more than one hat.
- mmcclellan 11y agoFor fun: Why I Love Basic Auth: http://www.rdegges.com/why-i-love-basic-auth/ http://www.rdegges.com/why-i-love-basic-auth/
- jacquesm 11y agoThat's not user facing, and that's the subject here. In the user facing context the bigger problems are that 'basic authentication' did not support such niceties as logging out and sends the password in plaintext. So yes, it's easy to use and simple but so is a tri-cycle and I'd hate to have to make any miles on a tri-cycle.
- pbreit 11y agoBut how does the consumer get the credentials in the first place? That's the main or only purpose of Oauth!
- vonklaus 11y agoI like Simple Value. It was a concept that a lot of people have stopped using. You either allow a user to use your site without signing in, with extra value for them if they do OR just provide the value proposition up front so that they will be willing to sign in. Obviously, this won't work if you are hocking sluggish blogspam with less content than the titanic had lifeboats and enough javascript to track my cross atlantic voyage. Just make shit that doesn't suck and users will sign up if it is necessary. If there is no need to have users sign up don't have it. Super Simple Value. Build on Super Simple Auth ^TM.
- RickHull 11y agoThis earned a hearty chuckle. +1 Insightful to boot.
- seanp2k2 11y agoAuthentication and authorization are different concerns, and OAuth attempts to handle both in a secure manner. I love working with basic with too, but it's not a fair comparison.
- broodbucket 11y agoI don't think this is a good critique of OAuth at all. First of all, the majority of complaints aren't even about OAuth, they're about (a specific implementation of consuming) OpenID Connect, which it doesn't seem like the author realises he's using. JWTs aren't in OAuth 2.0. If the author had realised this, surely when looking for libraries to assist with the project he would've looked for an OIDC or JWT library instead of something specific to Google. There are plenty of library recommendations on the JWT website[1], including .NET. It's not like OAuth 2.0 or OIDC are trivial to use, but these aren't easy problems to solve. OpenID Connect is young, and there's still a lot lacking in terms of library support and (probably more importantly) documentation. I'd rather deal with the rough edges of OIDC than use SAML any day of the week. [1]: http://jwt.io http://jwt.io
- nickbauman 11y agoAgree. SAML is crazy complicated.
- notwhereyouare 11y agoYep. Spent basically 2 months trying to implement saml manually. We had kinda a working implementation for something else. Tried to use it. Didn't work. Ended up finding a solution that somebody published. Modified and got working for my situation. It sucked and put me really behind schedule. Doesn't matter. The other members of the project were ever further behind
- volkadav 11y agoThe entire spec, yes, is big, but the part you actually need is not that complicated. I implemented the IdP for the new york times (there's quite a bit of third party shit plugged into the nytimes.com web experience that we wanted to be transparent to users) in a few weeks as I recall, and I'm not some coding super-genius. (It was kinda hacktified and minimalistic, but it worked at scale. ¯\_(ツ)_/¯) Most of our counter-parties were up and running in a week or so. Compared to the abysmal quagmire that was our ecommerce code, SAML implementation was a total milk run.
- X-Istence 11y ago
- sinzone 11y agoOne of the folks behind OauthBible. Have you looked into Kong [1]? We built it as Open-Source proxy (based on NGINX) that has many out-of-the-box plugins for Authentication: including JWT [2], HMAC and the tedious OAuth2 [3]. For example, Kong reduces the complexity of adding OAuth2 to your services in just a restful POST request, similar to this: $ curl -X POST http://kong:8001/apis/{api}/plugins http://kong:8001/apis/{api}/plugins \ --data "name=oauth2" \ --data "config.scopes=email,phone,address" \ --data "config.mandatory_scope=true" Another alternative is Auth0.com but it's cloud based and Kong is obviously a fully featured API Gateway that does many other things so it might be too heavy if all you need is authentication. [1] https://github.com/Mashape/kong https://github.com/Mashape/kong [2] https://getkong.org/plugins/jwt/ https://getkong.org/plugins/jwt/ [3] https://getkong.org/plugins/oauth2-authentication/ https://getkong.org/plugins/oauth2-authentication/
- rynop 11y agoI hate OAuth [2.0] as well. So how do you do twitter? They don't have a full JS client side implementation..
- lootsauce 11y agoTotally agree OAuth sucks. Want a simple way forward? https://passwordless.net/ https://passwordless.net/ For profile info: https://en.gravatar.com/ https://en.gravatar.com/ Why do you need someone to sign in with their third party service account? If it's just because you want a low friction sign up / sign in think again, it is not low friction. If its to prevent from having yet another account and password? This could be a great option. With OAuth There is a lot of friction on the flow and privacy concerns. "What kind of data are they going to suck out of my account?" Last time I looked at OAuth years ago I had huge reservations. In mobile apps it uses a web-view in the middle of the flow. Is that web-view logging my key presses? Is it using HTTPS? Is the cert good? You'll never know. I ran some of these concerns by Eran Hammer (brilliant, great guy) and he had no great consolation to give me. Not long after came his epic departure from OAuth (Not implying any correlation.) I went on to "invent" a new auth system for mobile based on push notifications. I got mired in trying to patent this and realized that was stupid. TL;DR of that project, push notifications are an amazingly secure and targeted way to deliver auth tokens try it out! But in the end, nothing beats the simplicity of letting go and just going with passwordless and gravatar IMHO.
- pfooti 11y agoI dunno - I get the privacy concerns, sure. But passwordless requires the user have an email address to receive the nonce, and it requires the developer to deal with that flow. It also requires transactional email, which can be laggy at times - I know sometimes (rarely, but not never) my mandrill outbounds can take minutes to actually resolve. If I'm sitting waiting for a login token to get to my emails and it's not Right There, I'm walking. I don't see passwordless fixing anything new that OAuth doesn't fix. Use the basic profile grant, and the user sees the consent screen where you're just asking for a small grant. Passwordless works for users whose email providers are not also major OAuth providers, which is nice, but also pretty niche.
- lootsauce 11y agoSure, lag could be a problem with some email providers, but you are not limited to email. From the site: "Deliver your tokens via email, text messages (SMS), or smoke signs. You can embed Sendgrid, emailjs, Twilio, or any other framework you like to get the token to your user."
- Mimick 11y agoI made a Facebook and Twitter OAuth libraries, and I can see it sucks. Twitter's PHP library that is linked on thier documentation is based on a really heavy OAuth library and it's old a bit that most things their aren't need and it seems to care that as long it works it's fine. Facebook OAuth isn't complicated since they don't look to care about "security" as much as Twitter do (or just Twitter trying to implement every OAuth specification blindly). But again Twitter trust you with thier Token for life while Facebook is for a while... So I agree with the author except on the part when he said he came up with a good alternative which is just a step behind.
- resonanttoe 11y ago"It’s a sentiment that’s so common, it has it’s own Twitter account." So does Texts from Dogs. Twitter is not a good measure for anything.
- artifaxx 11y agoImplementing OAuth 2.0 client and server code in a .NET stack this summer for a job makes me inclined to agree that OAUTH has confusing points. It definitely is not precise enough to be called a specification, but more just guidelines. I am quite impressed with how the author overblew the whole thing to show off their solution, it was an interesting fusion of technology and selling their idea.
- tacotuesday 11y agoI've arrived at the opinion that users simply cannot be trusted to keep their own credentials safe. It's literally impossible to secure a system based on trusting the user. There are very successful businesses (mint.com) built around the concept of sharing extremely sensitive credentials for some reward. In the tutum intro video I watched yesterday, the pitchman is asking developers within the first minute of video to enter AWS credentials into his website I've never heard of. If anyone would balk at that suggestion, I would expect it to be developers, yet they are so successful, Docker is buying them for meeellions of dollars. I'm really surprised no one in the thread has yet mentioned yubico as a solution. I like yubikeys because they are something users can't upload. Keys are a concept everyone understands, and despite what I'm told by friends, I've yet to lose mine. I've never lost my car/house/mailbox keys either though. Maybe I'm odd in both respects. I keep my credentials and keys close to me.
- mmebane 11y agoI found keeping my Yubikey Neo on my actual keychain to be a bit inconvenient, but wearing it around my neck like a dog tag has worked great. Sadly, I've been unable to convince my wife that it's worth it. She won't wear it as a necklace or bracelet, almost never has pockets, and rarely has her keys near her when at home. I might just have to stick an Edge-N in her laptop and slip an Edge onto her keychain, so that when she inevitably calls complaining she can't log into GMail from a friend's computer, I'll be prepared... From a development perspective, I've read through the U2F spec, and it seemed quite reasonable. I haven't had a chance to try implementing it in anything, though.
- deleted 11y ago[deleted]
- aianus 11y ago> There are very successful businesses (mint.com) built around the concept of sharing extremely sensitive credentials for some reward. That's because banks are too backwards to support something like OAuth so I don't have to share my whole damn password when I just want mint to have my balance. Hell, in Canada banks are so backwards you can barely send $1,000 online even with the password.
- segphault 11y agoOAuth is broken by design. Among many other serious issues, it's ridiculous that Twitter and other major OAuth adopters still implement it in a manner that relies on native/mobile client applications uniquely identifying themselves with "secret" keys that are trivially easy to extract. It's deeply unfortunate that so many of the people involved with the spec chose to shout down critics and hand-wave away serious concerns until it was too late to fix the problems. OAuth 2 should have provided an opportunity to address the issues, and instead it just rubber-stamped many of the worst practices used by implementors.
- lobster_johnson 11y agoAuthentication on the web is not going anywhere until browsers implement native identity support. The constant focus on authentication and "identity providers" in discussing this stuff misses the fact that sites and apps, above all, are concerned with continuity: The next time I'm visiting foo.com, I'm the same person that visited yesterday. It's the good old session cookie. Right now, most sites ask you to sign up with an email address because that's the constant; but that leads to a proliferation of accounts strewn across the Internet, each with its own password and identity data. On the other hand, the whole idea of authenticating through a third-party provider such as Google just centralizes identity with what ends up being a very small pool of select providers, because nobody wants to show 42 different "login in with..." buttons. But all we really want is that browser can prove (cryptographically) to foo.com that I'm "user #2048203", and foo.com can prove that it is privy to that information. foo.com shouldn't get anything but a opaque identifier, and anything else it wants (my email, my name, my address) can be divulged through an API dedicated to this purpose. The whole login problem was derailed because of authorization ("site foo.com wants to access your contacts"), which OAuth was originally designed for, was abused for authentication. But authorization is a completely orthogonal use case, and it's a fairly limited compared to login; I authorize an app maybe once a month, but I login every day. We don't need or want Google or Twitter or any third-party authority to manage our identities. What we do need is to be able to store our sets of identities somewhere so that all our devices can share them — Apple could offer that through iCloud, for example, and browsers could easily give you different options. Apple already invented ApplePay, which is exactly this for payments. Isn't anyone working on something like this for login?
- copsarebastards 11y agoI have deep, deep objections to OAuth, and I hoped this article would espouse some of them, but it doesn't. Instead, this article is basically whining about "programming is hard" which is true but also something anyone trying to solve serious problems got over somewhere between high school and getting a real job. OAuth is hard because it's pretending to solve a hard technical problem (logging in and sharing some private data securely) while actually solving an easy business problem (how do we (a big company) get smaller companies to outsource as much of their user data as possible to us). It kind of solves the hard technical problem (because bigger companies are better at hiding the data you give them from other companies who don't pay for it, and have all your data anyway). But if that half-assed solution to the hard problem is good enough for you, you aren't actually trying to solve it, you're just to persuade uneducated users you've solved it. In short, OAuth For Dummies would be a tautological title for a book. I've heard it said that it's okay and even desirable to outsource everything in your business to other companies except your core service. But what service exists without users? If you can't get users to sign up for your service and give you their information, then I'd argue you don't even have users. You might as well quit. This isn't a question of "what's the best way to authorize users?" question it's a "do I even have users?" question.
- testrun 11y agoI do not know who is the uneducated here, but in the case of OAuth, the other company already has the user data. What OAuth enables is to use their information to verify the user. What this post is trying to say, is that the method stinks.
- copsarebastards 11y ago> I do not know who is the uneducated here, but in the case of OAuth, the other company already has the user data. No, they don't. Google, for example, doesn't have the entire signup list of all the users of The Old Reader, but they have a lot of The Old Reader's users, because The Old Reader outsources authorization for some of its users to Google. That's data that Google is collecting via OAuth, and you'd better believe they use that data. > What OAuth enables is to use their information to verify the user. That's what it enables for the OAuth consumer, but there are far easier ways of doing that. The difficulties of OAuth exist because OAuth doesn't serve the OAuth consumer's needs, it serves the OAuth provider's needs.
- zkhalique 11y agoYou shouldn't have to "Allow" a big provider like Facebook or Google to share your first name, last name and sex with a website, just so they can display it back to you. Fred Wilson spoke about the rise of decentralized identity: https://www.youtube.com/watch?v=R43OKYmGbhU#24:00 https://www.youtube.com/watch?v=R43OKYmGbhU#24:00 Do you think such a thing exists successfully yet? Anyone heard about good implementations?
- mixmastamyk 11y agoAnd if you think it ruins the user experience when a person is involved, it's even worse when if you need to automate api calls.
- hardwaresofton 11y agoHas anyone worked with or have a strong opinion regarding CAS? http://www.yale.edu/tp/auth/cas10.html http://www.yale.edu/tp/auth/cas10.html It's very similar to OAuth, except way simpler to understand, and very easy to implement (I'm working on a standalone go server that will perform authentication, but have been dragging my feet a bit so it's not done yet -- basically the only reason it's not shipped is that it's failing tests)
- hardwaresofton 11y agoOh for those interested, here's the standalone server I've been working on (it's super rough): https://github.com/t3hmrman/casgo https://github.com/t3hmrman/casgo While there are other versions of the CAS specification (v2, v3, v4), my implementation sticks pretty close to v1, since it has what you really need (I diverge a little because I use JSON).
- jldugger 11y agoCAS is not federated. If your CAS authenticated wiki detects you're not logged in, it redirects you to what it knows as the CAS url, not YOUR CAS url. This makes it wonderful for universities and large institutions that deploy lots of small applications and buy third party hosted services, as you can keep the passwords local while proving identity and providing relying parties limited data they may need for authorizations. But if you don't have an account my CAS setup recognize, you'll need to make one first. And if you have one with another institution, we won't recognize it.
- hardwaresofton 11y agoYes, CAS is primarily for that usecase, but could you explain what stops Facebook (or some other current oauth provider) from running a CAS server and enabling me to register a callback URL and using it to authenticate a user visiting my site? Maybe I'm misunderstanding something fundamental
- jldugger 11y agoWell, I mean, a lot of the complaints about OAuth2 revolve around how the system was designed for high scalability over security; OAuth tokens never expire. Beyond that, I'd have to think a bit. I haven't studied OAuth2 in sufficient detail really.
- BinaryIdiot 11y agoI'm curious what people's opinion of Oz is as it was created by the "Fuck OAuth" guy aka Eran Hammer that the article refers to. http://hueniverse.com/2015/09/19/auth-to-see-the-wizard-or-i-wrote-an-oauth-replacement/ http://hueniverse.com/2015/09/19/auth-to-see-the-wizard-or-i...
- scintill76 11y ago> only after lifting code from what’s got to be the most obscure message board on the internet. So obscure that I can’t find it anymore. Side note, but this is one of the reasons I always put in a comment with a source URL when I lift code from somewhere.
- intrasight 11y agoOMG. Give me a frickin break. OAuth is hard? Get serious, get a CS degree, then come back here and tell us OAuth is hard. Complaining that it is a weak standard, however, is an argument that holds water.
- mariusmg 11y agoOAuth might not be good but this "article" is just a commercial for their product.
- fkooman 11y agohttps://tools.ietf.org/html/rfc6749#section-1.8 https://tools.ietf.org/html/rfc6749#section-1.8 ``` OAuth 2.0 provides a rich authorization framework with well-defined security properties. However, as a rich and highly extensible framework with many optional components, on its own, this specification is likely to produce a wide range of non-interoperable implementations. In addition, this specification leaves a few required components partially or fully undefined (e.g., client registration, authorization server capabilities, endpoint discovery). Without these components, clients must be manually and specifically configured against a specific authorization server and resource server in order to interoperate. This framework was designed with the clear expectation that future work will define prescriptive profiles and extensions necessary to achieve full web-scale interoperability. ``` So what are we waiting for? I don't think OpenID Connect is the answer here, maybe something more in the direction of IndieAuth (https://indieauth.com/ https://indieauth.com/).
- steviee 11y agoDeal with it. Want to use a framework, learn how to use it properly, especially if it's authentication/security related. Programming is hard. You won't learn anything about the technology by only using high level point-and-click libraries and IDEs. best regards, Steviee
- Luker88 11y agoWill anyone that is interested in authentication protocols participate at the Chaos Communication Congress late this year? I might present a new solution to this OAuth madness, and I will be looking for people to help me finish the project.
- adimania 11y agoFrom implementation standpoint, I frequently use Google Auth and a bunch of their APIs. At least for Python, I can confidently say that they are not at all painful. Yes, there is fragmentation between different oAuth providers but unless you are writing oAuth library yourself, you may not need to face these problems ever. Fyi, I am not using any oAuth lib but then I only use google auth for my app, not fb or twitter.
- jpdlla 11y agoSimilar read[0] with an actual proposal replacement for OAuth at the end. Thoughts? [0] http://hueniverse.com/2015/09/19/auth-to-see-the-wizard-or-i-wrote-an-oauth-replacement/ http://hueniverse.com/2015/09/19/auth-to-see-the-wizard-or-i...
- anusem12 11y agohttp://www.expert5th.in/packers-and-movers-bangalore/ http://www.expert5th.in/packers-and-movers-bangalore/ @ Packers and Movers in Bangalore http://www.expert5th.in/packers-and-movers-hyderabad/ http://www.expert5th.in/packers-and-movers-hyderabad/ @ Packers and Movers in Hyderabad
- anusem12 11y agoPackers and Movers India @ http://www.expert5th.in/ http://www.expert5th.in/ http://www.expert5th.in/packers-and-movers-pune/ http://www.expert5th.in/packers-and-movers-pune/ @ Packers and Movers in Pune
- homakov 11y agoSee Homakov edition of OAuth, it's simpler and more secure http://www.oauthsecurity.com/ http://www.oauthsecurity.com/
- crusso 11y agoI'm surprised I don't see more buzz about Steve Gibson's SQRL authentication system during discussions like this. It seems lightweight, simple, and fairly well thought-out. https://www.grc.com/sqrl/sqrl.htm https://www.grc.com/sqrl/sqrl.htm
- al2o3cr 11y agoSee, and here I was thinking that people who whine about technical complexity without understanding it just to push their company's product was "ruining everything". Don't get me wrong - OAuth is neither fun nor straightforward. But making "yuck" faces at the details isn't helpful.
- itaysk 11y agoIsn't OpenID Connect supposed to solve this? (don't know if it actually delivers though)
- dboreham 11y agoDisappointing article. The executive summary could be "software development is hard". Well, we knew that.
- arca_vorago 11y agoWhile I have my issues with OAuth, I think it depends on the use case more than anything. For example, I have written a custom ticket system for my current company, and since they have drank the google coolaid, everyone has a google apps account, so using OAuth2 to provide an easy login that doesn't require the often clueless users to remember yet another password. (working on pushing pass management, yubico integration and other two factor). It was simple to implement, gives me information that is helpful (the person who submits the ticket doesn't have to tell me who they are, I already know.), and just works. On the other hand though, I have two side projects at the moment. A reddit/hn-esque news site dedicated to logical analysis of stories, and an Unreal Engine 4 FPSRPG game. For the game, I really want to encourage good security, both for accounts (the game website accounts) and for game login (game login accounts). Looking at the issues that the major MMO providers ran into, and for example, Blizzard finally come out with the Battle.net authenticator, but adoption was fairly low, but the important part is for the people who valued their account greatly, it was often worth the overhead. Besides that though, there was just a simple in-house auth. I don't think anyone would want OAuth to login to an MMO, so there it's not even an option. The alternative I have thought of is instead of a physical dongle authenticator, having some sort of two factor built into the login portal. While it doesn't offer the same protection as a dongle, it would be more than the simple user/pass combo to help reduce compromised accounts. For my news site on the otherhand, I am struggling to decide what kind of logins to allow/seek. Since it would be a social type of site, OAuth could be useful for people who want an account but don't want to sign up for yet another thing. As a privacy conscious person though, it raises lots of privacy and user identity concerns. Reddit free-for-all style user-creation though seems to be too apt to be abused in all kinds of ways, but then HN has a similar system but then prevents that with restrictions on top. (which I think would falter under the same user-load as reddit). In the end I think the free-for-all is probably inevitable, especially if I want to allow tor connections, and restrictions will, like hn, have to be placed on top. A lot of that is design related. Stories would be wikipedia-esque in that some users could edit, and comments would be a separate section, and I think that's where slashdot style random mods and perhaps user points over time would give good commenting users ability to then do edits... I still haven't ironed all that out yet. The bottom line is that it's all about use case. And while OAuth isn't perfect, sometimes it works just fine, and in others it won't. Use the right tool for the job.
- Shorel 11y agoDamn, and I was so busy hating SAML and hoping next system would use OAuth.