If we already have OAuth 2.0 working using the web application
registration, is there any benefit to switching to the native application
registration? Everything has been working fine for close to a year, but we
are managing accounts from a single top MCC.
On Monday, February 17, 2014
Jeremy,
If you have it working then you won't have to worry about it =). For new
developers who are getting started, or for folks who are migrating from
ClientLogin to OAuth 2.0 - native application registration is a bit simpler.
Thanks,
Ray
On Tuesday, February 18, 2014 2:27:41 PM UTC+1,
Thank you for the response Ray Tsang.We are managing all of the adwords
accounts from a single top MCC and we have registered it as a web
application.I want to know how do we get refresh token for a web
application rather than for a native application.Please clarify.
Regards,
Karthik
On
Karthik,
I'd highly recommend registering a Native application if you are managing
accounts from a single top MCC. You'll only need one single refresh token
in this case.
However, if you really want to explore using an OAuth 2.0 web application,
please see behind the scene
Karthik,
GetRefreshToken works best when you have registered a native application.
Please see our OAuth 2.0 Authentication Guide for AdWords
APIhttps://developers.google.com/adwords/api/docs/guides/authentication
.
Whether you need to use OAuth 2.0 native application or web application
We have registered our site as a web application and in which there is a
redirect url which redirects to the status of the application ex:
https://app_name.organization_name.com/status . when I run the
getRefreshToken() method, I have to get a code on which typing it on the
input console
