Yes, i implemented this already. I developped the widget in GAE in Java.
There I used OAuth to authenticate against the gdata-api. Then I stored the
combination of "usern...@gappdomain.xxx" and the OAuth accesskey in the GAE
persistant storage. Everything works fine. So when i log in google apps th
Probably OAuth, though I'm not sure how that will work with a gadget. In
most places gadgets will include a user ID with the makeRequest.
On Tue, Feb 23, 2010 at 12:23 PM, Thomas Schnocklake <
thomas.schnockl...@googlemail.com> wrote:
> Thank you for your answer.
>
> So what would you suppose to
Thank you for your answer.
So what would you suppose to use for authentication for a gadget that is
places in google apps (e.g. gmail, google sites ) ?
thanks
thomas
2010/2/18 Ikai L (Google)
> Yes, this seems to make sense. Being logged into Google Apps is independent
> of being logged into
Yes, this seems to make sense. Being logged into Google Apps is independent
of being logged into an App Engine application. They don't use the same
cookie. App Engine's User service allows you to use Google logins, but not
the Google Apps session.
On Tue, Feb 16, 2010 at 3:29 AM, tsschnoc wrote:
Hello,
I use App Engine in my Google Apps domain and restricted the
authentification of app
engine to my apps domain. (see
http://code.google.com/appengine/articles/auth.html
)
I developed a widget and use this in multiple accounts of my google
apps domain.
When i switch from one account (of my a
