Thank you for the response, Danial. I failed to note that the original
poster was using the deprecated scope. I am getting this result while using
the current adwords scope (https://www.googleapis.com/auth/adwords). Just
tested with the deprecated scope and received the same results.
I've attempted to use the Installed Application grant flow with the results
described on this stackoverflow.com post:
http://stackoverflow.com/questions/25024374/google-api-oauth-2-0-installed-application-grant-flow-why-is-the-authorization
It seems that the Web Application grant flow (including offline) relies
on a server listening at the redirect URI to complete the exchange. (This
is not feasible in my use-case.) Have I missed something?
~Jonathan Jones
On Monday, August 4, 2014 3:37:48 AM UTC-6, Danial Klimkin wrote:
Hello Jonathan,
Please try either offline or web application flows.
Also, note you are requesting the deprecated scope. It should still work
but we recommend to use the new one for all new applications:
https://developers.google.com/adwords/api/docs/guides/authentication#scope
-Danial, AdWords API Team.
On Saturday, August 2, 2014 2:03:48 AM UTC+4, Jonathan Jones wrote:
I am receiving exactly the same response as Jeff Knight reported. The
only difference is that I am making the initial POST from a native C++ app.
If I request a scope of https://www.google.com/calendar/feeds/;, the
response includes a device code, user code, etc.. as expected.
To be perfectly clear, I am attempting to acquire an access/refresh token
for the Adwords API using the OAuth for Devices flow. What might cause this
response?
As a side-note, using a client library is not an option in my use case.
Thank you for your time,
Jonathan Jones
On Friday, May 30, 2014 8:24:52 AM UTC-6, Michael Cloonan (AdWords API
Team) wrote:
Hello Jeff,
Have you tried using one of our automated tools to fetch the refresh
token? They are linked in the middle article you mentioned, after you pick
a client library language. Please give one of these a try. If that still
fails, I can take a more detailed look.
Regards,
Mike, AdWords API Team
On Thursday, May 29, 2014 4:37:34 PM UTC-4, Jeff Knight wrote:
I have followed the following guides, but am still having issues.
https://developers.google.com/accounts/docs/OAuth2ForDevices
https://developers.google.com/adwords/api/docs/guides/authentication#getting_started_with_oauth_20_and_the_adwords_api
https://support.google.com/a/answer/162106?hl=en
Whenever I make the curl call to get the refresh token, I keep getting
the following error
curl -d client_id=.apps.googleusercontent.comscope=
https://adwords.google.com/api/adwords/;
https://accounts.google.com/o/oauth2/device/code
{
error : invalid_scope,
error_description : Not authorized to request the scopes: [
https://adwords.google.com/api/adwords/];,
error_uri : http://code.google.com/apis/accounts/docs/OAuth2.html;
}
I have enabled the client id and scope access following the Third
Party Data Access (Oauth) guide.
Any help would be greatly appreciated
Thanks
Jeff
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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
---
You received this message because you are subscribed to the Google Groups
AdWords API Forum group.
To unsubscribe from this group and stop receiving emails from it, send an email
to adwords-api+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
