Authenticate using OAuth 2.0 (and not Client Login)

AML authentication needs to switch from Client Login to OAuth 2.0 before the Client Login sunset date on July 21, 2014.

From: Caitlyn Duggan

OAuth 2 slide from v201309 workshop: http://www.slideshare.net/marcwan/oauth-20-refresher-talk
OAuth 2 slide from v201302 workshop: http://www.slideshare.net/marcwan/05-o-auth2-17314226

http://code.google.com/p/google-api-ads-java/wiki/OAuth2
https://developers.google.com/adwords/api/docs/guides/authentication
https://developers.google.com/accounts/docs/OAuth2InstalledApp#choosingredirecturi

Add new "Installed Application" or "Native Application" to get the secret token.
https://code.google.com/apis/console

https://developers.google.com/oauthplayground/

And here are mine & Jeph's notes from that workshop related to OAuth2: http://kbase.ri.thesearchagency.com/index.php/Google_AdWords_API_v201302_workshop#OAuth_2
________________________________________

From: Mark R. Bowyer bowyer@google.com

It's now been decided that we will be sunsetting ClientLogin to authenticate with the AdWords services in June 2014, and the next release of the API and Client Libraries will be the last ones to support it. They will also then be sunsetting as we sunset ClientLogin.

We have been saying for some time that ClientLogin is insecure and deprecated, and asking our users to switch to OAuth2.0, and now we're moving to make it a requirement. However, the latest release of the Client Libraries, as well as supporting v201306, also included better support for OAuth2.0 in all supported API versions, making the transition far easier.

If you have a top level MCC that you connect as, and gain access to the rest of your accounts using that account's credentials, then there is very little you need to change. Some config in PHP, up to a few lines in Java as well as the properties file update, but basically everything remains much the same. The examples that are provided alongside the Client Libraries demonstrate what you need to do. We also have a Blog post that explains everything you need to know, whichever language you use, provided by my two London colleagues, Paul and Marc.

Marc has also written a Node.js credentials store for those who need to share credentials between different applications and locations.