85

Apparently, for some reason, Google is retiring its OpenID 2.0 platform. I got this notice while logging in with Disqus, but not with Stack Exchange.

So... is Stack Exchange going to be affected by this? Do I need, or want, to add extra login methods to my Stack Exchange account to ensure I can still log in come April?

Improve this question

1 Answer 1

Reset to default
68

Stack Exchange already uses the OAuth 2.0 APIs to log you using a Google account; note the URL in those screenshots. You can also verify this by logging in with a Google account, the login screen URL contains:

https://accounts.google.com/o/oauth2/auth

As such, Stack Exchange is not affected by this deprecation, it is already using one of the recommended APIs.

However, StackExchange.com, the Data Explorer, and Area 51 have not yet been updated; you will see the deprecation warning there if you use Google to log in. The Data Explorer is Open Source, so if you can help out with migrating that stack, please do so! It'll be interesting to see if Area 51 will get the update any time soon; the stack running that site is quite outdated.

Improve this answer
18
  • 10
    Yes, as soon as we noted that Google was retiring OpenID 2.0, we started moving to its OAuth 2.0 APIs. And most people didn't even notice ;)
    – Oded
    Commented Nov 29, 2014 at 14:06
  • @Oded: apart from those that noted that you now copy across the name (and a few other bits and bobs). :-P
    – Martijn Pieters
    Commented Nov 29, 2014 at 14:06
  • Yeah, which is mostly a result of how the Google OAuth implementation works.
    – Oded
    Commented Nov 29, 2014 at 14:07
  • 1
    I started switching Data Explorer over but I haven't had a chance to finish it up yet (hopefully soon)
    – Tim Stone
    Commented Nov 30, 2014 at 0:50
  • No plans to update Area 51 as such... but we're working on a new login system that should take care of this as well. Same goes for stackexchange.com, which I believe also still uses the OpenID endpoints.
    – Adam Lear StaffMod
    Commented Nov 30, 2014 at 6:00
  • 1
    @Anna Lear: how could Ī help with it? The problem at Area 51 affected me just today, as an intrusion of Gravatar. Will it be fixed? Ī’d not object against Gravatar, but it prompts me to register at wordpress.com whereas Ī’m unwilling to signup on a service Ī have no use.
    – Incnis Mrsi
    Commented Dec 1, 2014 at 15:07
  • I recently logged in (minutes ago) to meta and was presented with the notification. Does that mean meta has not been updated?
    – Joe C
    Commented Dec 7, 2014 at 3:02
  • @Joe: I can't quite reproduce that. How did you log into Meta exactly? What was the first URL you were directed to when you picked Log in using Google? Specifically, what was the continue parameter in that URL set to?
    – Martijn Pieters
    Commented Dec 7, 2014 at 3:07
  • @Oded SO Careers is also affected, btw.
    – badp
    Commented Dec 8, 2014 at 18:25
  • @badp - I think the careers team are on it. Will make sure.
    – Oded
    Commented Dec 8, 2014 at 18:34
  • It seems like Chat is also affected.
    – user188031
    Commented Dec 19, 2014 at 2:36
  • 12
    Also, most urgently of all, the Winter Bash site.
    – jrturton
    Commented Dec 26, 2014 at 19:32
  • 2
    Still affecting the main stackexchange.com site, confused the heck out of me when I logged in via there today.
    – deworde
    Commented Feb 3, 2015 at 10:08
  • @Tim ummm.... did you finish this?
    – Shadow Wizard
    Commented Apr 19, 2015 at 13:43
  • 2
    I can no longer log into data.stackexchange.com :(. I hope it's fixed soon.
    – Millie Smith
    Commented Apr 22, 2015 at 5:09

Not the answer you're looking for? Browse other questions tagged .