Since about the beginning of december the oauth flow for our app has been
broken. It previously worked for ~3 months with no changes. It seems to
have coincided with the new permission page for oauth and only affects
functionality after an adwords token has been granted.
Steps to reproduce:
var
This issue is still live, and it seems to only affect my oauth login when
using the adwords scope.
On Wednesday, January 15, 2014 12:32:36 PM UTC-8, Pere Kyle wrote:
>
> Since about the beginning of december the oauth flow for our app has been
> broken. It previously worked for ~3 months with no
Anyone?
On Thursday, January 16, 2014 5:23:43 PM UTC-8, Pere Kyle wrote:
>
> This issue is still live, and it seems to only affect my oauth login when
> using the adwords scope.
>
> On Wednesday, January 15, 2014 12:32:36 PM UTC-8, Pere Kyle wrote:
>>
>> Since about the beginning of december the
Hello Pere,
Do you get the same error if you provide *only* AdWords scope? Can you
combine those calls to have a shared refresh token for both GA and AdWords
API?
-Danial, AdWords API Team.
On Thursday, January 16, 2014 12:32:36 AM UTC+4, Pere Kyle wrote:
>
> Since about the beginning of de
Daniel,
Anytime I request a adwords scope for an already authed adwords account I
get a 400 error.
Tried
var scopes = 'https://adwords.google.com/api/adwords/';
gapi.auth.authorize({client_id: clientId, scope: scopes, access_type:
'offline', response_type: 'code', prompt: 'select_account',authus
Hello Pere,
So far I wasn't able to reproduce this scenario. Can you please outline the
exact steps how your users get into this state?
-Danial, AdWords API Team.
On Saturday, January 25, 2014 6:53:59 AM UTC+4, Pere Kyle wrote:
>
> Daniel,
>
> Anytime I request a adwords scope for an already
Danial,
It seems it may be related to the google api javascript library and
specifically using the postback option. I am requesting an auth_code via a
postback on the js side, then getting a refresh token using the php library
on server side. Should I degrade use of the postback option?
Thanks
Here is the code on server side using the adwords client library:
$redirectUri = 'postmessage';
$OAuth2Handler = $user->GetOAuth2Handler();
// Get the access token using the authorization code. Ensure you use the
same
// redirect URL used when requesting authorization.
$user->Se
After some more testing I tried forming the url without using the google js
lib like such:
https://accounts.google.com/o/oauth2/auth?scope=https://adwords.google.com/api/adwords/&response_type=code&access_type=offline&redirect_uri=MYURL&approval_prompt=force&client_id=MYID.apps.googleusercontent.
Hello Pere,
Looks like this is indeed an issue with the JS lib. Unfortunately it is out
of scope for our team as it's not specific to the AdWords.
I suggest to generate the URL yourself but consider reporting it as a bug
for the JS library.
-Danial, AdWords API Team.
On Wednesday, January
10 matches
Mail list logo
