How about having the continue url page check if it's being called on appspot, and then forwarding to your 'correct' url? Then you can continue using Users etc and just have a tiny bounce in-between that'll be hardly noticeable. Using Users is a longer-term decision, the current problem is (hopefully) temporary.
On Wednesday, March 21, 2012 5:37:40 AM UTC+2, tarun2000 wrote: > > I set up a reverse proxy with nginx on ec2 to provide ssl for my appengine > custom domain. It works until users need to login. The users are > redirected to my appspot url after authenticating if I provide a relative > continue url. I tried setting the continue parameter with the entire url > (the one that hits the proxy) instead of just the relative location, but > this results in a 500 on appengine when appengine redirects to > mycustomdomain?conflogin (which the proxy sends to my appspot url). > > Is there a way to use Google Accounts and User Service with a reverse > proxy or will I need to create my own sign on system? (I know SSL for > custom domains is in testing but I'm looking for an immediate solution > since there is no telling when this will be available). > -- 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/-/22mP8yZGo8kJ. 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.
