OK, and you're saying this can be done automatically after the first manual authorization? I just want to make sure so that I won't have to do manual authorization every now and then for the app to be able look in the calendar.
Just so we're clear: The GAE-app will NOT need access to the calendar of any of its users. However it WILL need around-the-clock access to the calendars of a specific Gmail-account created only for this purpose. Just want to make sure before investing time and effort into learning OAuth2. So: Can I use OAuth2 for my needs? Cheers! /Tottish On 9 Jan, 00:07, Ernesto Oltra <[email protected]> wrote: > Hi, > > I didn't have any problems in sharing all the code, but it's in Go; contact > me if you need it. > I meant that the OAuth flow is: > > You prepare the authorization & redirect the user to Google ---> The user > allows your app ---> Google gives you a temporary token ---> You > interchange that token with a permanent one (with an expire date) ---> > Store it > > Each time you do a request, the code must: > > Retrieve the token ---> If it's expired, ask for a new one -> Store it > again if it has changed ---> Do the request > > Hard-coding the password in your code requires an update & deploy each time > the user changes the password (apart from being less secure). > > Ernesto -- 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.
