Google Ads API - new authentication method

[César Diaz]

Hi,

   We have an app running in a server and configured as an installed desktop app. It authenticates using the ruby gems "google-ads-googleads"(https://github.com/googleads/google-ads-ruby) for the client and later it uploads offline conversion data to the Ads portal. But we have been told that our authentication method is going to be deprecated in October(https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html#disallowed-oob) and we should change it then.

Which should be the right method to use in replace of our actual one in our case?

[Google Ads API Forum Advisor]

Hi Cesar,

Thank you for reaching us out. I am Sherwin from Google Ads API support team. I hope that you are doing well today.

Moving forward to your concern regarding OOB. Based on the blog posted, I highly suggest you to download the latest version of the client library that you are using as it is now using the loopback IP address which is the workaround for the said deprecation. Then, I suggest you follow this guidance "Desktop clients: OAuth 2.0 for Desktop apps".

If you have further concerns, please feel free to reply on this thread.

Warm regards,

Sherwin Vincent Google Ads API Team

ref:_00D1U1174p._5004Q2bwUSe:ref

[César Diaz]

Hi Sherwin, many thanks for your quick answer!  

so to understand even better ..

We are using so far the version 16.0 from February without any problem to upload the conversion to the portal, and then to continue using our script, all we need to do is just update the gem to the newer versin 17.0 from May this year. Should be enough to sort this deprecation issue?

To give you a context

All our config for authentication nowadays with google-ads-googleads version 16.0 relies in a file google_ads_config.rb similar to this next sample

Google::Ads::GoogleAds::Config.new do |c|
  c.developer_token = 'INSERT_DEVELOPER_TOKEN_HERE'
  c.client_id = 'INSERT_CLIENT_ID_HERE'
  c.client_secret = 'INSERT_CLIENT_SECRET_HERE'
  c.refresh_token = 'INSERT_REFRESH_TOKEN_HERE'
  c.login_customer_id = 'INSERT_LOGIN_CUSTOMER_ID_HERE'
end

with that been said, then if we update to this new version of the gem, this configuration file should remain without any change at all as it is now cuz all the loopback ip work was solved in this new version rigth and we can continue running our scripts without problem after October 3rd 2022 right?!

Many thanks for your help!

Cesar

[Google Ads API Forum Advisor]

Hi Cesar,

Thank you for reaching out to the Google Ads API support team.

We only provide support related to the AdWords API/Google Ads API on this support channel. For the Ruby client library, with this, I recommend you to reach out to Ruby client library owners by opening a new issue with their team via issue tracker , for further assistance.

Thanks,

Nirmita Google Ads API Team

ref:_00D1U1174p._5004Q2bwUSe:ref