Hi All, I am a bit confused regarding the correct usage of ClientLogin token to obtain feeds from google calendar. I know google strongly discourages use of ClientLogin Authorization Token to access multiple services and recommends using OAuth/AuthSub tokens. I have implemented the AuthSub/OAuth Token successfully, and now want to understand how the ClientLogin stuff really works. I found this exact question in this forum but no answer :-(
* A user successfully authenticates using ClientLogin (meaning we get an HTTP 200 response after we call https://www.google.com/accounts/ClientLogin with the proper fields and headers set) * We parse the auth token out of the body of the response * We make a second call (to http://www.google.com/calendar/feeds/default/private/full) and include the auth token in the Authorization header as set_header(req, 'Authorization', 'GoogleLogin auth='|| google_auth_token); * here we get an HTTP 401 ("token invalid") response At that point, should we just do the ClientLogin call again to get a new auth token? If so, what's a reasonable number of retries? If not, what should we do at that point? Thanks, Charlie Reference: Charlie Wood http://groups.google.com/group/google-calendar-help-dataapi/browse_thread/thread/1bb1acb812439556/7d58dd9764532871?lnk=gst&q=auth+token#7d58dd9764532871 Thanks, Prateek -- You received this message because you are subscribed to the Google Groups "Google Calendar Data API" 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://code.google.com/apis/calendar/community/forum.html
