Sunday 15 July 2012

google api - Using googlecl with a non-Gmail address -



google api - Using googlecl with a non-Gmail address -

i trying build little toolbox of scripts such can automate tasks involving google contacts, calendar , on. of work done means of googlecl project, looks promising.

as far understand process, googlecl needs request authentication ticket google means of oauth. admittedly, have sketchy notion of going on there, that’s wikipedia help me solve.

here’s catch: google business relationship uses non-gmail address (let vucar@example.invalid sake of discussion). business relationship created in old days when google didn’t forcefulness gmail downwards people’s throats have no utilize it. googlecl direct me https://www.google.com/accounts/oauthauthorizetoken?oauth_token=…&hd=example.invalid finish oauth handshake. google tell me ‘the domain name has not been signed google apps’. correct.

if don’t supply user id googlecl, url reads …&hd=default. google take oauth request, granting whichever permissions needed locally running googlecl, googlecl complain token issued different user id user id requested. of course of study correct.

i’ve read through https://support.google.com/a/answer/33419, in turn redirects me http://www.google.com/a in order ‘to sign domain google apps’. apparently, if google business relationship uses domain different @gmail.com, business user , need purchase google apps domain—to get, amonst truckload of other stuff, domain connected gmail, polar opposite of wanted have having ‘foreign’ domain in first place.

i have admit stymied. understand oauth in case used for, fail grasp byzantine reasoning @ google’s. not believe want google apps domain, , especially not want hand on emails or else google. simply want access , modify info @ google’s, user id happening not end in @gmail.com.

is strictly required purchase google apps work such configuration? contacts, calendars , forth @ google’s, , used both google’s web site , android clients. thing new mix api access.

google-api google-oauth

No comments:

Post a Comment