AdWords API Re: Clarifications needed on ClientLogin API and AuthenticationError for v200909

2010-03-19 Thread AdWords API Advisor
Hi,

My apologies, I actually referenced the wrong error in my last
response.  For expired authTokens the reason is:

  GOOGLE_ACCOUNT_COOKIE_INVALID

This reason will be returned for any invalid authToken, including
those that were invalidated due to a password change.

The reason OAUTH_TOKEN_EXPIRED is only applicable when OAuth
authentication is used, which isn't fully fleshed out yet in the API.

Best,
- Eric

On Mar 18, 10:22 am, SEM  wrote:
> Eric:
>
> You're right in that the error reason for an expired auth token being
> LOGIN_COOKIE_INVALID isn't obvious.
> That said, in what situation would the error OAUTH_TOKEN_EXPIRED be
> returned?
>
> Lastly, which of the above erros would be returned if the user changes
> his password and we attempt to reuse the authtoken for the invalidated
> login?
>
> Let me know.
>
> Thanks!

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en

To unsubscribe from this group, send email to 
adwords-api+unsubscribegooglegroups.com or reply to this email with the words 
"REMOVE ME" as the subject.


AdWords API Re: Clarifications needed on ClientLogin API and AuthenticationError for v200909

2010-03-18 Thread SEM
Eric:

You're right in that the error reason for an expired auth token being
LOGIN_COOKIE_INVALID isn't obvious.
That said, in what situation would the error OAUTH_TOKEN_EXPIRED be
returned?

Lastly, which of the above erros would be returned if the user changes
his password and we attempt to reuse the authtoken for the invalidated
login?

Let me know.

Thanks!

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


AdWords API Re: Clarifications needed on ClientLogin API and AuthenticationError for v200909

2010-03-17 Thread AdWords API Advisor
Hi,

To address your questions:

a) Auth tokens expire after 2 weeks, or when a user changes the
password on their account.

b) The reason returned for an expired auth token is
LOGIN_COOKIE_INVALID, which isn't immediately obvious.  We are working
on improving the documentation to make this more clear.

Best,
- Eric Koleda, AdWords API Team

On Mar 16, 9:00 pm, SEM  wrote:
> We use the ClientLogin RESTful API for authentication (http://
> code.google.com/apis/accounts/docs/AuthForInstalledApps.html) for
> Google Adwords API v200909.
> As recommended, we plan on caching the authtoken returned by the
> ClientLogin API for subsequent use in AdWords API calls.
>
> A few questions arise with regards to this implementation:
>
> a. What are the criteria that cause an authtoken to change?
> e.g. expiration after a set duration of time, user manually changed
> his login credentials, etc.
>
> b. Subsequently, after an authtoken changes, when we attempt to use a
> previously cached value, we would probably get an AuthenticationError
> via a SOAP response.
> The various reasons for this as enumerated (as 
> perhttp://code.google.com/apis/adwords/v2009/docs/reference/AdGroupAdSer...)
> are...
>
> AUTHENTICATION_FAILED
> CLIENT_CUSTOMER_ID_IS_REQUIRED
> CLIENT_EMAIL_REQUIRED
> CLIENT_CUSTOMER_ID_INVALID
> CLIENT_EMAIL_INVALID
> CLIENT_EMAIL_FAILED_TO_AUTHENTICATE
> CUSTOMER_NOT_FOUND
> GOOGLE_ACCOUNT_DELETED
> GOOGLE_ACCOUNT_COOKIE_INVALID
> FAILED_TO_AUTHENTICATE_GOOGLE_ACCOUNT
> GOOGLE_ACCOUNT_USER_AND_ADS_USER_MISMATCH
> LOGIN_COOKIE_REQUIRED
> NOT_ADS_USER
> OAUTH_TOKEN_INVALID
> OAUTH_TOKEN_EXPIRED
> OAUTH_TOKEN_DISABLED
> OAUTH_TOKEN_REVOKED
> OAUTH_TOKEN_HEADER_INVALID
> LOGIN_COOKIE_INVALID
> FAILED_TO_RETRIEVE_LOGIN_COOKIE
> USER_ID_INVALID
>
> Unfortunately, the documentation isn't very clear about what causes
> each of these failure reasons to occur.
>
> e.g. if the token is invalidated by Google after a set period of time,
> which of the following AuthenticationError.Reason would we get:
> AUTHENTICATION_FAILED?
> OAUTH_TOKEN_INVALID?
> OAUTH_TOKEN_EXPIRED?
> LOGIN_COOKIE_INVALID?
> FAILED_TO_RETRIEVE_LOGIN_COOKIE?
>
> We need this information to determine whether we should 'automatically
> retry' a ClientLogin request with the original login credentials (and
> follow it up with the failed SOAP request) or whether the process
> should be aborted.
>
> Any help on this is appreciated.
>
> Thank you!

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en