*Originally posted to the Google Apps How-To Help forum.*
I have been tasked with developing server-side Google Apps integration
modules for our client-server CRM product, which normally runs entirely on
our customers' own hardware (server on IBM i; clients on a variety of
hardware), and specifically for tying our server into Google Calendar.
Can 2-legged OAuth work in this situation, and if so, how?
I've begun looking at the online documentation, and specifically at
http://code.google.com/apis/accounts/docs/OAuth.html#GoogleAppsOAuth
and I'm having a great deal of difficulty determining which of the "three
key groups" (if any) would apply here.
We are definitely not in the business of hosting a web application on our
own hardware, and have no interest in entering such a business, but much of
what I've been reading (including everything that mentions 2-legged OAuth)
seems to be written for those who are.
We've got other developers waiting for me to achieve proof-of-concept here,
and I'm having trouble getting a handle on this. I have a number of
different technologies at my disposal for both consuming and hosting web
services from the IBM i platform; the problem is that I'm drowning in the
docs for how to use OAuth.
Would somebody please throw me a proverbial life-ring?
--
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
