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 [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.
> 

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

Reply via email to