4

Recently I have received complaints about my app suggesting that logging in with a Google account shows a warning message that OpenID authentication has gone away. When I tried to log in with my own Google account the same warning was shown to me blocking the login flow.

It seems that the mobile authentication page has not been updated to use the Google OAuth option, and is instead still trying to use the Google OpenID endpoint. Can the mobile authentication page be updated?

Improve this question
5
  • Which authentication page are you talking about? Got a link handy?
    – Adam Lear Staff♦
    Commented May 23, 2015 at 15:52
  • @AnnaLear I am using stackexchange.com/oauth/dialog link for authentication in my app.
    – Birkan Cilingir
    Commented May 23, 2015 at 19:38
  • This is not WARNING but ERROR like problem, which is stopping any possibilities to use this app via google account identification.
    – michal
    Commented May 25, 2015 at 7:48
  • @AnnaLear has there been any progress about this problem? Were you able to reproduce it? Do you need more information?
    – Birkan Cilingir
    Commented Jun 10, 2015 at 19:59
  • @BirkanCilingir I looked at this earlier today. I think I see where the problem is, but I don't have the environment on my machine just yet to reproduce/fix. I'll hunt down a way to do that ASAP.
    – Adam Lear Staff♦
    Commented Jun 10, 2015 at 23:23

1 Answer 1

Reset to default
2

So, this was a fun one. :)

We apparently broke several different things over the course of a year that went unnoticed until Google turned off OpenID support. In no particular order but for fun and posterity:

  1. Facebook OAuth authentication just straight up didn't work. It broke back in January of 2014 when the code was accidentally changed from function loginWithFacebook() to function oauth_version().
  2. Once that was fixed, it turned out that at some point we broke the part of the OAuth flow that would fake a redirect instead of issuing a 302 and running face-first into a denied cross-domain AJAX request. (Google OAuth flow had the same problem.)
  3. Tangentially related, we also broke error message display about a month ago when we noticed a weird header being set in the HandleError method and figured it was save to remove instead of, I don't know, search for where else it may be used. :P

All in all, a bit of a comedy of errors, starting with "uh, how do I even test this locally?". It's all fixed now, so the Google auth flow in your app should work fine once more.

Improve this answer
2
  • Hooray! Happy days! \o/
    – Tim Stone ♦
    Commented Jun 11, 2015 at 22:16
  • I didn't finish the login via Google flow but I was able to pass the page that caused the problem. Thanks for your support :)
    – Birkan Cilingir
    Commented Jun 13, 2015 at 11:53

You must log in to answer this question.

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