Hello, Please have a look at the OAuth developer's guide for the raw protocol: http://code.google.com/apis/accounts/docs/OAuth.html#GoogleAppsOAuth
Best, Alain On Wed, Nov 16, 2011 at 2:00 PM, James Lampert <[email protected]>wrote: > Thanks, Alain and omirza. > > This puts me a bit further than I was in the authentication part of the > project, but I'm still a bit stuck, because the examples given at > http://code.google.com/apis/**gdata/docs/auth/oauth.html#** > 2LeggedOAuth<http://code.google.com/apis/gdata/docs/auth/oauth.html#2LeggedOAuth> > use client libraries, but unfortunately, at least as far as I know, > nobody's written one for OS/400 native ILE. > > Instead of a client library, I'm accessing the web services directly > (opting for JSON output), using Scott Klement's HTTPAPI ( > http://www.scottklement.com/httpapi/ ). > > Which is to say that I've successfully accessed a calendar, and retrieved > and parsed its events, using "magic cookie" authentication, but that hardly > seems adequate for the task at hand, i.e., checking Google Calendar for > conflicts when scheduling activities in a CRM system, given that any user > may need to check any other user for time conflicts. > > Is there an example for 2-legged OAuth without a client library? > > -- > 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 > -- Alain Vongsouvanh | Developer Programs Engineer -- 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
