Hi All, I think it would be cool if this could be looked at soon as well! I've started using OAuth for the Analytics API recently after someone I was working for found that there was a funnel drop-off in their sign up process on the page where they were asked for their Google Account password. There's also some issues with ClientLogin due to the CAPTCHA challenges, keeping password changes in sync, and the more recent 2 step verification codes that aren't issues with OAuth.
Additionally, the documentation for Google accounts authorization (http://code.google.com/apis/accounts/docs/GettingStarted.html) suggests that ClientLogin is a legacy API and OAuth should be used instead. Moreover, the documentation states that ClientLogin is only for installed applications and should not be used for web applications. These types of system are supposed to use either AuthSub or OAuth to keep customer accounts confidential. I was hoping to start using OAuth with the AdWords API until I realized about this problem. The Reporting Service is one of the ones I use most often so can't move to it before it's resolved. I was considering trying to work around it by emailing reports out but AdWords doesn't actually send them as attachments (unless I've missed something) and you still need to login with an email and password to download the report. Regards, Ewan -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
