The refresh token is the long-lived token you are looking for, so there
should be no need to use ClientLogin. When your access token expires, use
the refresh token to get a new access token. More details at:
http://code.google.com/p/google-api-java-client/wiki/OAuth2
-- Yaniv
On Thursday, Se
Does anyone know of an example using a Service Account to access the
AdWords API?
On Thursday, September 27, 2012 4:06:50 PM UTC-4, j.e.frank wrote:
>
> Most services do have a shared database, but not all of them.
>
> I continued investigating this issue, and I've also tried the Service
> Accou
Most services do have a shared database, but not all of them.
I continued investigating this issue, and I've also tried the Service
Account approach which uses a private key instead of getting an
authorization through a browser URL. However, this keeps giving me a "bad
grant" exception if I tr
Excellent questions, and I hope someone can answer them soon.
Do your servcies not access a shared database to store a common token to be
used by all services?
Oliver
On Thursday, September 27, 2012 7:24:50 PM UTC+1, j.e.frank wrote:
>
> I'm looking at migrating to the new Java client library a
I'm looking at migrating to the new Java client library as part of the
upgrade from v201109. One thing I thought was going to be a benefit of
this migration was long-lived access tokens, to enable long-running
services to use the API without having to worry about refreshing the
ClientLogin tok
