Authentification failed

8 views
Skip to first unread message

SEO Sniffer

unread,
Aug 3, 2010, 3:52:26 PM8/3/10
to AdWords API Forum
I wrote my authentification data in the auth.ini file. But I get this
error message.
I don't know what the application token is. I comment it out.

http://nopaste.info/6d177aea98.html

AdWords API Advisor

unread,
Aug 4, 2010, 4:32:03 PM8/4/10
to AdWords API Forum
Hi,

This error is being returned by the ClientLogin API, which the AdWords
API uses for authorization.

http://code.google.com/apis/accounts/docs/AuthForInstalledApps.html

The error indicates that the username and password is not correct.

Best,
- Eric Koleda, AdWords API Team

SEO Sniffer

unread,
Aug 5, 2010, 1:14:47 PM8/5/10
to AdWords API Forum
But I use the email and password from my google MMC Account in
auth.ini file.

emailfrom...@yahoo.de
password

SEO Sniffer

unread,
Aug 5, 2010, 1:43:00 PM8/5/10
to AdWords API Forum
I use aw_api_php_lib_2.2.0 for php.
That's my auth.ini file.

email = "mym...@yahoo.de"
password = "mypassword"
userAgent = "SEO Sniffer"
applicationToken = "INSERT_APPLICATION_TOKEN_HERE"
developerToken = "mydevelopertoken"

; Uncomment to make requests against a client account.
;clientId = "mym...@yahoo.de"

AdWords API Advisor

unread,
Aug 5, 2010, 4:25:32 PM8/5/10
to AdWords API Forum, SEO Sniffer
Hi,

Please ensure you are using the primary email address listed on this
page:

https://www.google.com/accounts/ManageAccount

Best,
- Eric

SEO Sniffer

unread,
Aug 5, 2010, 4:38:42 PM8/5/10
to AdWords API Forum
Yes, I use this Email-Address. I cannot understand this problem.
I downloaded aw_api_php_lib_2.2.0 lib, copy the Google folder in my
project and Edit the auth.ini file with my login data. Should I send
you my auth.ini file, so that you can test it?

SEO Sniffer

unread,
Aug 5, 2010, 7:38:54 PM8/5/10
to AdWords API Forum
Now It works online on my linux webserver.
Offline with windows xampp system it doesn't work.

AdWords API Advisor

unread,
Aug 6, 2010, 5:17:08 PM8/6/10
to AdWords API Forum
Hi,

I've seen this problem before when arg_separator.output isn't '&'.
I'll update my library to always use this value when constructing the
ClientLogin request.

Best,
- Eric
Reply all
Reply to author
Forward
0 new messages