Hi Ryan, The behavior you've observed is by design. Google Accounts users must explicitly sign in to any application wishing to have access to their email. Google Apps does not have the same login policy.
-Marzia On Tue, Jan 6, 2009 at 7:17 PM, ryan <r...@vanmiddlesworth.org> wrote: > > I've written a basic App Engine app that authenticates with my Google > Apps account fine. That is, if I'm logged in to my Google Apps mail, > I can jump over to my App Engine app and I'll already be logged in. > The opposite also works fine. > > However, I've now written a small Google Gadget that offers a sliver > of functionality of the main app, but when I place that on the start > page for the Google Apps account, it doesn't respect the login status > of the user. That is, the user can be logged in on the start page, > but the Gadget doesn't know. Similarly I can log in to the App Engine > app, but then go to the start page and click sign out. The rest of > the page shows the logged out status, but the gadget remains logged > in. > > It's almost like my gadget is using a separate auth mechanism than the > main app pages, but they aren't. They're both using the Users API > (http://code.google.com/appengine/docs/users/). > > Does it have something to do with the fact that my gadget is using URL > content-type instead of HTML? > > Thanks, > Ryan > > > > --~--~---------~--~----~------------~-------~--~----~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
