8 ms·
Google is shutting down OpenID 2.0
- teh 12y agoOpenID has been on its way out for a while. It's being replaced by OpenID Connect [1] so this is not bad news, but a good reminder in any case! [1] http://openid.net/connect/ http://openid.net/connect/
- nailer 12y agoPractically, openID is being replaced by oauth. A decade ago authentication and authorisation were quite separate concepts. This has been replaced with a realisation that 'being authorised to use a particular account' (Google Account, Twitter, FB, etc) is sufficient to prove ownership of that account and therefore identity.
- Tobu 12y agoOpenID Connect is based on OAuth.
- nailer 12y agoOK. What else does OpenID Connect get me, vs asking for a limited-scope oauth?
- bvirkler 12y agoBasically, OpenID Connect is for federated authentication, and OAuth2 is for delegated authorization. I like Vitorrio's explanation: http://www.cloudidentity.com/blog/2013/01/02/oauth-2-0-and-sign-in-4/ http://www.cloudidentity.com/blog/2013/01/02/oauth-2-0-and-s...
- soapdog 12y agoEven though its community maintained these days, Mozilla Persona was a great authentication mechanism with federation support. I loved using it. A pity it failed to get traction.
- nly 12y agoThis gives me the creeps. Authorisation and identification are not the same. If you use 'Login with X' you're giving X access to all your accounts. That's not just third party attestation of your identity. It's kind of like saying a passport is what gives you access to your home country... in reality your status as a citizen is what gives you that right, the passport is merely a convenience.
- cheald 12y agoAuthorization of a null permission is effectively the same as authentication, though. I think the GP's point was that authz implies authn, even if the set of permissioned authz'd for is empty.
- deleted 12y ago[deleted]
- deleted 12y ago[deleted]
- nailer 12y agoEdit: see reply below, I think I misunderstood the parent post. > If you use 'Login with X' you're giving X access to all your accounts. That's definitely not correct. You are giving X to access only whatever scopes you allowed, on a single account. Here's an example of just 'userinfo'. Click this and see what it asks for: https://accounts.google.com/AccountChooser?service=lso&continue=https%3A%2F%2Faccounts.google.com%2Fo%2Foauth2%2Fauth%3Fscope%3Dhttps%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile%26response_type%3Dcode%26access_type%3Doffline%26redirect_uri%3Dhttps%3A%2F%2Fdevelopers.google.com%2Foauthplayground%26approval_prompt%3Dforce%26client_id%3D407408718192.apps.googleusercontent.com%26hl%3Den%26from_login%3D1%26as%3D-6660997c12ed44e0&btmpl=authsub&hl=en https://accounts.google.com/AccountChooser?service=lso&conti... Per the screen, it only allows: " - View your full name, profile picture and profile URL" " - View any publicly available information on your Google+ profile (if you have one or create one in the future)" It can't see your photos, see your contacts, read your email, post G+ messages, or anything else you didn't authorise.
- rabbyte 12y agoThat was actually understood a decade ago as well and was part of the conversation that led to OpenID and OAuth. It was suggested close to a decade ago that they both merge efforts and they have both struggled to find their place. Development on this scale just lags a bit behind, specially when the community around it is so fragmented and opinionated.
- chris_wot 12y agoI'm a tad confused... To be authorised is great, but authentication must first happen surely? Authorisation says I can access x, but authentication says I am who I say I am! Being authorized to use a particular account is still seperate from proving who I am. I have visions of going to the Pentagon and I say "Hi, President Obama here, give me access to all your intelligence data" and the analysts saying "Certainly sir! You have top authorisation, here is all the data". :-) Actually, that would work better at a bank. "Hi, I'm Donald Trump, give me a million dollars from my loose change account, thanks!"
- keeperofdakeys 12y agoTechnically you don't authenticate using OAuth, you just have a secret token - which is proof you own the account. If you wanted to stretch your analogy, you could say a check from Donald Trump is just an authorisation. OAuth definitely does authenticate though (hence the name).
- nailer 12y agoThe auth on 'oauth' is for authorization - see https://tools.ietf.org/html/rfc6749 https://tools.ietf.org/html/rfc6749 Your first sentence is totally correct though.
- nailer 12y agoGreat question. Think of it as "Hi, I'm an individual who has an oauth access token for President Obama's userinfo.me scope. The only person who can authorise this is President Obama". Hope that helps.
- christiansmith 12y agoIn fact, unlike previous OpenID protocols, OpenID Connect is a profile of OAuth 2.0. The conflation of authorization with authentication is an accident and a mistake. They are still quite separate concepts. Authentication is about verifying identity. Authorization is about privileges afforded a given identity. Access control models usually depend on some form of upstream authentication. The third-party authorization flows provided by OAuth are not intended to establish or verify a user's identity. Their purpose is to extend a user's access to a third-party in a limited way without sharing passwords. Social Sign-in is an accident of 3-Legged OAuth and its use for this purpose is considered a very weak form of authentication. OpenID Connect takes the best ideas from preceding identity protocols and incorporates them into OAuth flows, giving the best of both worlds. More information on all of the above here: https://github.com/christiansmith/anvil-connect/wiki/References https://github.com/christiansmith/anvil-connect/wiki/Referen...
- nailer 12y agoYou've said limited scope authorisation is weak authentication, but you haven't said why in your post. Can anyone advocating OpenID connect give a single sentence explanation of why people (developers and users) would want to use it vs limited scope oauth?
- learningram 12y agoDo you have any suggested good reads about the topics ?
- ComputerGuru 12y agoCalled it back in 2008: https://neosmart.net/blog/2008/google-doesnt-use-openid/ https://neosmart.net/blog/2008/google-doesnt-use-openid/ OpenID 2.0 screamed "embrace, extend, and extinguish" loud and clear. It's 8 years later, probably not as evil (TM) as I had prophesied (more likely attributable to the death of OpenID rather than malice), but, yeah... EDIT: Yes, 6, not 8. I got the 8 from 2008 stuck in my head, apparently. Oops!
- taytus 12y agoYou "called it" 6 years ago :/
- StavrosK 12y agoMozilla Persona was the best of the authentication protocols :(
- ldng 12y agoWell, it still could be, no ? If someone would put the resources behind that is.
- StavrosK 12y agoSure, protocols only die when nobody uses them, but who will?
- onli 12y agoI would. Depending on what you are working on, you can use it how it is right now. It's nicely integrated into gmail, it works good enough for other mail providers. There are modules for probably every big web programming language and for many frameworks, most blogsoftware should have a plugin for it. I use it in all my personal projects and had no issue with persona itself. The one issue was that the sinatra gem is unmaintained, but there is a fork that works fine.
- StavrosK 12y agoSure, I do too, but I'm talking about a big-name mail provider, like Google or yahoo. The bridge is good enough for support, but not for mindshare.
- zanny 12y agoYou should. Not necessarily you, but a lot of startups are on here and they all should be pushing persona logins. It works, its available, go get it If enough sites adopt it it puts pressure on both Google and Mozilla to implement it as a browser feature the way it was designed to be. Then we have personal logins without information jacking or the potential for tolls on logins.
- brunoqc 12y ago
- mahouse 12y ago> ...is disabled for a small number of requests on an intermittent basis, some users will be forced to re-consent Very inconsiderate.
- fryguy 12y agoActually, it's considerate. Given the choice of having all of your users suddenly shut off, or a small portion of them, the latter is better. Suppose that the number is 1% of people that get shown this page. This means only 1% of the people are going to email you to remind you to fix it, instead of everyone at once. By gradually ramping this number up, you get the most notification with the least number of users inconvenienced.
- fintler 12y agoPrevious discussion at https://news.ycombinator.com/item?id=8346355 https://news.ycombinator.com/item?id=8346355
- PythonicAlpha 12y agoWhat me frightens a little with this move (OK, I acknowledge that OpenID2.0 is deprecated and should be updated to something new), is that Google talks only about "Google+ Signin". And OK, as I read in previous discussion, Google will also in the future support logins from people with normal eMail account. Still, I am worried, since Google does not clearly communicate these facts, but when you look at their communications, you read only about "Google+ Signin" and you have to search to find that you do not need Google+ but just the new protocol OpenID connect. I don't like to see such communications from a company, that once claimed (long, long time ago!! Do you remember Google?) "Don't be evil". It is OK, when they move away from an old protocol, but it is not OK, when they (and it very much looks that way to me!) use it as vehicle to market their products. Google has troubled people enough with forcing G+ on them -- so I even find it more troublesome, how they do it now (as it seems to me currently). I fear, Google is still hunting after Facebook and is by the way inheriting its bad habits. As I see now, they also want that a new button is used -- something with G+ on it. I see, they really lay the pressure on the people -- many people will think, that they need a Google+ account to use this feature (even if not required). I would say, Google you are going to hurt yourself! I myself, was thinking about using a "Login with Google" button in my application ... but now, with things changed, I will think twice, before I do such a move!
- timothya 12y agoGoogle+ Sign-In is an implementation of OpenID Connect, with some nice features built on top: "Google+ Sign-In is built on the OAuth 2.0 and OpenID Connect protocols. It supports over-the-air installs, social features, and a sign-in widget on top of standardized OpenID Connect sign-in flows. Google+ Sign-In works for all users with a Google account, whether or not they have upgraded to Google+." [0] I don't understand where all your other conclusions came from. [0]: https://developers.google.com/accounts/docs/OAuth2LoginV1 https://developers.google.com/accounts/docs/OAuth2LoginV1
- PythonicAlpha 12y agoFrom this Link: https://developers.google.com/accounts/docs/OpenID#shutdown-timetable https://developers.google.com/accounts/docs/OpenID#shutdown-... and from common sense. BTW: Maybe you should also read my full post, before answering.
- higherpurpose 12y agoTime to replace it with SQRL? https://www.grc.com/sqrl/sqrl.htm https://www.grc.com/sqrl/sqrl.htm (I think the final spec will launch in a week or two.
- nly 12y agoSQRL doesn't solve any of the hard problems. See my post here https://news.ycombinator.com/item?id=8790768 https://news.ycombinator.com/item?id=8790768
- jay_kyburz 12y agoI'm going to use this opportunity to transition my users off social loggins altogether. I used Google and Facebook when first building the webapp because I simply didn't want to do the work of building an authentication system. It's lots of work to get right. About a year ago I had a lot of users complain my site _only_ had social logins so I had to implement my own anyhow. Now I have it, I don't see a lot of value in keeping the social logins around. I just need to ask users to add a password to their account and they can login using email/password combo.
- dyoo1979 12y agoI don't know your audience, so perhaps this makes sense. I don't want to remember or keep track of yet another password for a random web site. If the web site requires login and doesn't support Facebook/Twitter/G+ login, then I'll likely give up and avoid the page.
- jay_kyburz 12y agoI think there are a lot of users who feel the other way around, they can't trust "some random website" with their facebook / G+ identity. They would rather just make a throw away account with some easy to remember password.
- dyoo1979 12y agoI would agree that this is a major flaw, if the "scope" were unrestricted. But most of these systems support a capability-style model where you can say: "I give you permission to let me log in as myself, for this particular web site. But you have no other authority to do anything else as me." For example, "email" scope: https://developers.google.com/+/api/oauth#email https://developers.google.com/+/api/oauth#email, or the Permissions in Facebook login: https://developers.facebook.com/docs/facebook-login/permissions/v2.2 https://developers.facebook.com/docs/facebook-login/permissi... Another reason why I don't feel happy about forcing people to make passwords for random web sites: most people are really bad at understanding risky computer behavior. Do you have a parent or relative who uses the same password for everything? I do. Despite my best efforts to warn them, they are not convinced that this is a dangerous thing to do. I don't think they're alone in this. Education is not enough.
- knocte 12y agoSorry if this is a stupid question but, does this mean that Google accounts will no longer be OpenID accounts?
- lowlevel 12y agoJust wait until they shut down gmail.
- kordless 12y agoThere's no mention in here about the Python Users API that Google provides for managing users in your Python AppEngine application. Google hasn't updated the Python Users page (other than mentioning there are changes coming) and haven't indicated if they will or will not update the Users API methods to support the new auth methods. Given I chose AppEngine in part because of the Users API, it would be nice if there was some clarification by Google on what they plan to do with the Users call and how provide some suggestions (or, heaven forbid, sample code) to show us how to do it ourselves.
- kordless 12y agoJust a small update, because there's basically nowhere else anyone is going to read this given Google suspended Google groups for AppEngine and doesn't answer StackOverflow questions. I tried using the sample code from the User API pages and built this: http://kordtester2.appspot.com/ http://kordtester2.appspot.com/. The app is using standard Google authentication, not the federated auth. The docs say it should work, but it's clearly broken.