I am closing this thread as it is an old one, unrelated to this question
(it was about jwt) and the same question is discussed on several other
threads.
-Danial, AdWords API Team.
On Saturday, July 20, 2013 2:30:47 AM UTC+4, Matthew Ledom wrote:
>
> Did you ever answer the question about usin
Did you ever answer the question about using the refresh token in:
token = { :refresh_token => '' }
api.authorize({:oauth2_token => token})
The sample app does not show how to use that. I have setup the sample app
and it works great. In my application I can't have the user logging in all
th
Hello hagay,
Yes, JWT is supported in the Ruby library. See this example:
https://code.google.com/p/google-api-ads-ruby/source/browse/adwords_api/examples/v201302/misc/use_oauth2_jwt.rb
Most likely you only need to alter your configuration file to include:
:authentication:
:method: OAUTH2
Hi Daniel,
In my company we have our own domain. and we prefer to gain oauth2 without
user interaction as the nature of our application is server side only.
Is the Oauth2 jwt working for ruby users? if not is there a chance to use
another library (say python) in order to use the oauth2-jwt
What
Hi Daniel,
Can you please, give me a code example for how to use the refresh_token. I
tried this:
token = { :refresh_token => '' }
api.authorize({:oauth2_token => token})
Thanks in advanced for your help.
hagay. (clock is running out for ver201206...)
On Monday, February 18, 2013 1:15:29
Hello,
I am sorry we can not provide support on domain administration. Please
consider using non-JWT flow (which is a better approach in most cases) as I
outlined in this thread.
-Danial, AdWords API Team.
On Thursday, February 14, 2013 7:06:28 PM UTC+4, jmcu...@restorando.com
wrote:
>
> H
Hello hagay,
You can use OAuth2 to achieve that. There will be user interaction require *
once* -- the step with the verification code. After that, you need to store
the refresh token and use it every time you need to access the account. You
will not need user input again -- as long as the acce
Hi Danial, I'm having the same problem here.
I'm using OAuth2_Jwt with this config:
:oauth2_issuer: xx...@developer.gserviceaccount.com'
:oauth2_secret: 'notasecret'
:oauth2_keyfile: '/path/to/privatekey.p12'
:oauth2_prn: ''
# Other parameters.
:developer_token: 'xx
Hi Daniel,
Ok. In that case i guess I should use the the Oauth2 .
The issue is that I need to access the adsowrds api (using oauth2) *without
user interaction*. Do i still need the 'Service account' or 'Installed
Application' ?
If I need to use the 'Installed Application' how can i fetch the
Hello hagay,
You should only use OAUTH2_JWT if you are administering your own domain. If
you access 3rd party accounts, you should use plain OAUTH2.
In case you do manage the domain, you need to grant the application to
impersonate users for AdWords, please check with your domain administrator
Hi Daniel,
i added the ":oauth2_prn" authorization field but still instead of having
the NOT_ADS_USER problem i now get:
Signet::AuthorizationError: Authorization failed. Server message:
{
"error" : "access_denied"
}
my configuration file looks like:
:oauth2_keyfile: config/privatekey.
Hi,
I am writing server side application that using adwords_api, witch mean i
should use OAUTH2_JWT, right?
To create the client id i used the api console with the option of
'service_account'.
to the config file i am using:
:authentication => {
:method: OAUTH2_JWT
:oauth2_issuer: <
Hello Georgi,
Yes, the new gem supports the additional ":oauth2_prn" authorization field.
You need to set it to the user login your application should impersonate
for the request.
-Danial, AdWords API Team.
On Friday, February 8, 2013 11:13:33 PM UTC+4, teamma...@gmail.com wrote:
>
> Hi Dan
Hi Danial,
I see there is a posted answer
(http://code.google.com/p/google-api-ads-ruby/issues/detail?id=93) with
comment "fixed". I've updated the gems to the latest versions but still
have the same error (AuthenticationError.NOT_ADS_USER).
Is there anything else i should do?
Thank you in ad
Hello Thomas, Richard,
For Ruby, the library fails to pass PRN personalization email address. As
such, there is no way to identify which account you are authorizing
against. For Java, please create a new thread and library authors will get
back to you.
Richard, please follow up on the bug, I'
I'm also seeing this issue with the Ruby client. If there's any workaround
that'd be really handy to know.
Cheers!
Richard
On Friday, 18 January 2013 19:20:14 UTC, Thomas Heller wrote:
>
> Hi,
>
> I get the same NOT_ADS_USER error using the Java API Client.
>
> Any hints what exactly causes thi
Hey guys,
Any update on this?
Thanks,
Georgi
On Friday, January 18, 2013 9:20:14 PM UTC+2, Thomas Heller wrote:
>
> Hi,
>
> I get the same NOT_ADS_USER error using the Java API Client.
>
> Any hints what exactly causes this? I'm trying with access the
> CampaignService with a OAuth2 Service Acc
Hi,
I get the same NOT_ADS_USER error using the Java API Client.
Any hints what exactly causes this? I'm trying with access the
CampaignService with a OAuth2 Service Account and all I get is NOT_ADS_USER?
Regards,
Thomas Heller
On Friday, January 18, 2013 10:21:52 AM UTC+1, Danial Klimkin wrot
I see, thank you for the support, what are the available workarounds?
Best,
Georgi
On Friday, January 18, 2013 11:21:52 AM UTC+2, Danial Klimkin wrote:
>
> Hello Georgi,
>
>
> I have to say it is a library bug. I've logged it and will look into it
> soon:
>
> http://code.google.com/p/google-ap
Hello Georgi,
I have to say it is a library bug. I've logged it and will look into it
soon:
http://code.google.com/p/google-api-ads-ruby/issues/detail?id=93
-Danial, AdWords API Team.
On Thursday, January 17, 2013 1:30:58 PM UTC+4, teamma...@gmail.com wrote:
>
> Hi Danial,
>
> Just tried
Hi Danial,
Just tried replacing the method with OAuth2_jwt and we are doing good
progress, because i think the authentication passed successfully.
I have the following error now:
http://schemas.xmlsoap.org/soap/envelope/";>https://adwords.google.com/api/adwords/cm/v201209";>0004d3788a92a0600ae
Hello Georgi,
>From the stack trace I can see OAUTH2 method is used. You should use
OAUTH2_JWT instead. Please check this line in the configuration:
:authentication => {
:method: OAUTH2_JWT
...
Not related to the issue below, but require for the next step. Please make
sure you are signed
Hi Danial,
Thanks for the quick reply, we've replaced the adwords initialization with
the one you've suggested and we are having a progress, but still there is
another error:
/path/.rvm/gems/ruby-1.9.3-p327/gems/google-ads-common-0.9.0/lib/ads_common/auth/oauth2_handler.rb:116:in
`validate_cr
Hello Georgi,
If you initialize the library with a hash, you need to make sure to provide
all required credentials. Make sure to include all required fields like
this:
adwords = AdwordsApi::Api.new({
:service => {
:environment => :PRODUCTION
},
:library => {
:log_level => "DEBUG"
24 matches
Mail list logo
