Hi,

Unfortunately AuthSub is not a supported authorization mechanism for
the AdWords API at this time.  Did you find documentation that said it
was?  At this time the ClientLogin API is the only option available.

Best,
- Eric Koleda, AdWords API Team

On Oct 5, 7:09 am, nick <[email protected]> wrote:
> Hello,
>
> I'm new with the Adwords Api, but have recently begun development with
> the 2009 version. Right now I'm stuck on authentication.
>
> As I've read on the Adwords Api docs page, I'm supposed to obtain an
> auth token by means of the Clientlogin or AuthSub interface. Since
> AuthSub is meant for web apps, which I am working on, I chose to use
> that method.
> I found the documentation 
> onhttp://code.google.com/intl/nl/apis/accounts/docs/AuthSub.html#AuthSu....
>
> Next, I implemented all of it, resulting in a google page asking me to
> verify access for our system to access the adwords service, which
> redirects back to the app with a single use token. Then I make a call
> to google with the AuthSubSessionToken command, trading the single use
> token for a long lived session token. All of this seems to be working
> fine, resulting in a response providing me a session token. The token
> validates with the AuthSubTokenInfo command.
>
> Now the problem is, when I provide this token in the Soap headers of
> my v2009 api request, I get a Fault stating the following:
> AuthenticationError.AUTHENTICATION_FAILED @ ; trigger:'Invalid
> gaiaCookie: XXX', with XXX being the authentication token I obtained.
>
> Can somebody please tell me where I'm going wrong? Any help would be
> much appreciated.
>
> Sincerely
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/adwords-api?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to