Hi,
The AdWordsUser class, when constructed without arguments, reads values
from the adwords.properties file. It will automatically request an
AuthToken once you make a request that needs it - afterwords, you can
retrieve the AuthToken from the AdWordsUser. You should be able to
construct a
Hello stepanian,
The AuthToken is valid for up to two weeks. Please note it is very
sensitive string as it grants access to the account in full, not just
AdWords.
To avoid this we recommend to use OAuth2.0 instead which is supported by
all our libraries. With OAuth the token does not expire a
OK - this is what I got so far - I just need a confirmation that this is
correct:
1) It seems like the auth token is associated with a user only not with an
account (in other words, the client email is tied to the auth token).
2) The AuthToken object can be created from an email and a password.
Oliver,
Thank you very much for responding to me and attaching the link.
I looked at the thread thoroughly. I'm not 100% sure if the answer to my
first question is yes or no.
Tozor said that "from looking at the stack trace, it looks like the Adwords
client library is actually reloading the
This recent thread discusses what needs to be cached:
https://groups.google.com/forum/?fromgroups#!topic/adwords-api/xr8pRG8NkF8[1-25]
Oliver
On Wednesday, August 15, 2012 1:12:45 AM UTC+1, stepanian wrote:
>
> When I create an AdWordsUser object using the Java client library v201109,
> does i
When I create an AdWordsUser object using the Java client library v201109,
does it cache the authentication token behind the scenes?
If no, do I need to account for it manually? How?
If yes, does it also do it when creating AdWordsUser objects in separate
threads (processes)?
Recently I have
