Re: MCC's own client ID Access Denied - Using same account's secret and refresh token

2014-11-21 Thread eric haberman
Thanks for being so responsive! Glad it was ultimately an easy fix and not a *real* problem :) On Friday, November 21, 2014 10:02:16 AM UTC-6, Josh Radcliff (AdWords API Team) wrote: > > Wow - glad you got to the bottom of it. I don't think I would have caught > the locked file issue. :) > > C

Re: MCC's own client ID Access Denied - Using same account's secret and refresh token

2014-11-21 Thread Josh Radcliff (AdWords API Team)
Wow - glad you got to the bottom of it. I don't think I would have caught the locked file issue. :) Cheers, Josh, AdWords API Team On Thursday, November 20, 2014 9:13:56 PM UTC-5, eric haberman wrote: > > Resolved! Thank you for your help. > > The problem was a fluke caused by a locked file not

Re: MCC's own client ID Access Denied - Using same account's secret and refresh token

2014-11-20 Thread eric haberman
Resolved! Thank you for your help. The problem was a fluke caused by a locked file not being overwritten, after I updated the library using CLI instead of dragndrop, it worked fine. On Thursday, November 20, 2014 6:24:40 PM UTC-6, eric haberman wrote: > > *Here is a var_dump of the $user object

Re: MCC's own client ID Access Denied - Using same account's secret and refresh token

2014-11-20 Thread eric haberman
*Here is a var_dump of the $user object's header elements:* ["requestHeaderElements":"AdsUser":private]=> array(4) {["userAgent"]=> string(94) "deleted:targetfinder:v1.9 (AwApi-PHP/5.2.3, Common-PHP/5.2.3, PHP/5.3.10-1ubuntu3.14)"["clientCustomerId"]=>string(12) "581-880-2635"

Re: MCC's own client ID Access Denied - Using same account's secret and refresh token

2014-11-20 Thread eric haberman
Here is my request from the log, it looks like the access token is NOT being sent by the PHP library, though I am sending the 'access_token' in the $oauth2Info array when instantiating the AdWordsUser: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:ns1="https://adwords.google.com/api/adword

Re: MCC's own client ID Access Denied - Using same account's secret and refresh token

2014-11-20 Thread eric haberman
Thanks Josh, you're the man! I'm using the PHP library, I can't find an example for generating the access token (sorry, I took over this code from someone else in the company) Any tips? On Thursday, November 20, 2014 4:03:55 PM UTC-6, Josh Radcliff (AdWords API Team) wrote: > > Hi, > > Looking

Re: MCC's own client ID Access Denied - Using same account's secret and refresh token

2014-11-20 Thread eric haberman
You're the man Josh! I'm using the PHP library, I thought the library handled the access token? Any pointers on where to find an example of this in PHP, I can't find anything in the examples repo? (no worries if not, I can figure it out) Thanks! On Thursday, November 20, 2014 4:03:55 PM

Re: MCC's own client ID Access Denied - Using same account's secret and refresh token

2014-11-20 Thread Josh Radcliff (AdWords API Team)
Hi, Looking at your failed requests, the underlying errors suggest that perhaps you are not passing an access token in your Authorization header. Could you check your logs and confirm that the *Authorization* header is

MCC's own client ID Access Denied - Using same account's secret and refresh token

2014-11-20 Thread eric haberman
Hello, I'm getting the error: AuthorizationError. USER_PERMISSION_DENIED The MCC client ID (581-880-2635), developers token, and Google Developers Console refresh token and secret are all from the same account. (refresh token authorized in the same browser as the MCC account is logged into)