OpenID login redirect (/_ah/login_redir?) fails with 500 server errors!

[Jan Zawadzki / Hapara]

We're seeing consistent OpenID redirect 500 server failures for
specific Google Apps domains.

OpenID works for other domains just fine, but we're seeing an
increasing number of domains where the redirect just dies.

Fix ETA please?

Jan

[Lucian Baciu]

I'm seeing the same issue in my app as well. This is very <inconvenient> as users can no longer log in to the app.

Regards,

Lucian

[Jan Zawadzki / Hapara]

So this is getting worse - domains that used to work yesterday are now
getting the 500 error.  It looks like a security change that's getting
rolled out across domains is causing this.

The actual URL that triggers it:

https://teacherdashboard.appspot.com/_ah/login_redir?claimid=www.google.com/accounts/o8/site-xrds?hd=MYDOMAIN&continue=https://teacherdashboard.appspot.com/MYDOMAIN

Btw - the following doesn't work either:

https://teacherdashboard.appspot.com/_ah/login_redir?claimid=www.google.com/accounts/o8/id?hd=MYDOMAIN&continue=https://teacherdashboard.appspot.com/MYDOMAIN

(note /o8/site-xrds vs /o8/id)

This is quite critical as our users cannot login to GAE apps.

Thanks!

Jan

[Joshua Smith]

It's issues like this which lead me to conclude that the whole "let someone else manage your user's identity" is a fundamentally flawed business proposition.

If you are in the business of providing services to your users, relying on an unpaid, non-supporting 3rd party to handle their login credentials is insane.

> --
> You received this message because you are subscribed to the Google Groups "Google App Engine" group.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
>

[radomir]

We have a similar issue using Google account login, not OpenID. It appears whenever you're signed in to Google with multiple accounts. After you selected an account to sign-in with, you get error 500 (and nothing appears in the application logs). If you're signed in to Google using one account only, it works as expected.

I reported this two months ago (and created a production issue) but no fix.

On Tuesday, May 22, 2012 10:20:22 PM UTC+2, Joshua Smith wrote:

It's issues like this which lead me to conclude that the whole "let someone else manage your user's identity" is a fundamentally flawed business proposition.

If you are in the business of providing services to your users, relying on an unpaid, non-supporting 3rd party to handle their login credentials is insane.

On May 22, 2012, at 4:07 PM, Jan Zawadzki / Hapara wrote:

> So this is getting worse - domains that used to work yesterday are now
> getting the 500 error.  It looks like a security change that's getting
> rolled out across domains is causing this.
>
> The actual URL that triggers it:
>
> https://teacherdashboard.appspot.com/_ah/login_redir?claimid=www.google.com/accounts/o8/site-xrds?hd=MYDOMAIN&continue=https://teacherdashboard.appspot.com/MYDOMAIN
>
> Btw - the following doesn't work either:
>
> https://teacherdashboard.appspot.com/_ah/login_redir?claimid=www.google.com/accounts/o8/id?hd=MYDOMAIN&continue=https://teacherdashboard.appspot.com/MYDOMAIN
>
> (note /o8/site-xrds vs /o8/id)
>
> This is quite critical as our users cannot login to GAE apps.
>
> Thanks!
>
> Jan
>
> --
> You received this message because you are subscribed to the Google Groups "Google App Engine" group.

> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to google-appengine+unsubscribe@googlegroups.com.

[Jeff Tone]

Same problem here.  500 Errors at login now for  http://db.XXXXXXXXXXXXXX.com/_ah/login_redir?claimid=www.google.com/accounts/o8/id&continue=http://db.XXXXXXXXXXXXXXX.com/

It work 10 minutes ago for a moment but I tried to log out and back in and it immediately broke.

[Jeff Tone]

I tried wiping out multiple logins but this did not fix the problem even with the single Google login.

[Jeff Tone]

Is there anyway to access the app without going through the google login?  Our developer is on the case in 6 hours but is there anyway to use the app untill then?

[Yudong Li]

Would like to know if there is any workaround too.
No one can login any more since this morning.

On May 23, 9:10 am, Jeff Tone

[Yudong Li]

After clear all the cache from my browser,
and reload the login page a couple of times,
login is ok now...

[Jeff Tone]

Its intermittent.  Our employees cant get in again unfortunately.

On Monday, May 21, 2012 11:03:52 PM UTC-10, Jan Zawadzki / Hapara wrote:

[James Broberg]

Jeff,

Did you try as a minimum clearing all cookies relating to your app
(eg... xxx.appspot.com or whatever your custom domain happens to be),
or for the nuclear approach, clearing your entire browser cache?

Doing the above seems to have resolved it for us.

-James

> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.

> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/WUyclJIcIA4J.
>
> To post to this group, send email to google-a...@googlegroups.com.

> To unsubscribe from this group, send email to

> google-appengi...@googlegroups.com.

[Rajkumar Radhakrishnan]

Hi,

I have filed a production issue here, where you can..

• star the issue --and--
• add your Application ID in the comments

to notify Google staff and to help identify and fix the issue..

http://code.google.com/p/googleappengine/issues/detail?id=7560 

Best Regards,

Raj

--

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Build online database applications, over Google App Engine.

iFreeTools Creator - http://creator.ifreetools.com

[James Broberg]

Thanks - I spoke too soon. This issue is back for us and no amount of
cache clearing will fix it.

[Joshua Smith]

Another desperate measure to try: Use an incognito window in Chrome.

[Dao Linh Viet]

[Dao Linh Viet]

On Tuesday, 22 May 2012 16:03:52 UTC+7, Jan Zawadzki / Hapara wrote:

[Dao Linh Viet]

[Vinay]

We are using the  Federated Login feature of GAE and also experiencing this issue. I logged into the GAE control panel > Application Settings. I toggled both of "Cookie Settings" and "Authentication Options" to a different value, hit save, waited a minute, and toggled them back. Some of our users are reporting the ability to log in again. We need more data points, but we thought we'd put it out there for the rest of you in the meanwhile.

Vinay, Dito

[Vinay]

for what it's worth, my suggestion did not fully resolve the problem...just a fluke I guess.

[James Foster]

Is this currently happening again?

[Akitoshi Abe]

Hello,

It seems happening again.

Sometimes I saw this error recently.

Akitoshi Abe

2013/6/4 James Foster <james...@gmail.com>

--

You received this message because you are subscribed to the Google Groups "Google App Engine" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.

To post to this group, send email to google-a...@googlegroups.com.

Visit this group at http://groups.google.com/group/google-appengine?hl=en.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Henrique Casagrande Bravin]

Olá. Meu nome é Henrique e estou com um projeto na faculdade em desenvolvimento Python no GAE. Porém estou enfrentando um problema crítico que a dias não consigo resolver e gostaria da opinião de vocês se possível.

Usando o código na documentação do GAE sobre OpenID eu implantei o mesmo no meu código, porém ao invés de tê-lo diretamente no arquivo principal criei em um arquivo separado e chamei-o via import nos arquivos principais.

No SDK funciona bem sem nenhum erro. Más quando coloco para rodar online e clico em fazer login com qualquer serviço OpenID e o aplicativo redireciona para a página /_ah/ o servidor me retorna um erro 500.

Vocês saberiam me dizer qual poderia vir a ser o problema e se já enfrentaram algo parecido pois não existem nada nos Logs do aplicativo.