That should possibly save a little head banging.
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
date: Thu, 14 Feb 2013 14:58:09 -0600
from: Bradley Stone <bvstone@xxxxxxxxx>
subject: Re: *afpds spooled file not printing correctly on ip attached
Without a browser on your device you have 2 options when dealing with
OAuth 2.0 and Google APIs:
1. Service account
With option 1, you'll get used to receiving the error "invalid_scope" for
some of the APIs, like drive. I've confirmed with Google they have some of
them turned off right now and that's whey the error happens.
With option 2 you have to store the userid and pw of the account which
defeats the purpose and intention of OAuth 2.0 (ie, you don't have to know
or ask for their account id and pw). Not sure it's as "easy" as it was
with 1.0 as well.
Anything is possible, and I could have written something to mimick a
browser, but with the service account option (which you would use on
devices that don't have browsers, like a fridge or IBM i) I'm sure the APIs
will open up soon enough.
You still have to USE a browser with the service account. But it isn't as
seamless as if you were using a PC or Android phone where the user is
already logged into their google account on that device and therefore just
gives authority to use the specific API/service/app.