omab/django-social-auth — Issue #202: Google OAUTH broken?
Author: patersr
Created: 2011-12-22 02:29:40+00:00
State: open

I suspect this is something I'm doing wrong, because I can't find evidence online that anyone else is having this problem, but...

About 6-8 weeks ago my app www.fit-tracker.com hosted on GAE using django-nonrel and django-social-auth started to get:

"Google accounts

Sorry, there seems to be a problem. The service you're looking for is temporarily unavailable. We're working hard to restore your access as soon as possible. Please try again in a few hours. Thanks for your patience"

Whenever I tried to log on. I've tried various fixes in my code, and then out of desparation I decided to go back to the sample django-social-auth app at http://social.matiasaguirre.net/ to see if I could build back out piece by piece to determine what I've broken. However, the sample app also gets the same error - and yet no-one else seems to experience this - am I the only one using Google OAUTH authentication?

Google OpenID works every time in both Fit-Tracker and the sample app, and Google OAUTH2 works in the sample app.

I get this error at home and at work, however occasionally if I just pound away at it, it will let me through.

Any ideas on what the problem is or should I be avoiding OAUTH entirely?