Hi Joey, Our recommendation, moving forward is to use OAuth2. I recommend you looking at the installed applications flow, in which a single user interaction is required to authorize your application access to their account and will grant you a refresh token - that never expires - that your scheduler can re-use to authorize requests.
Using OAuth2 will ensure a longer-life to your application in terms of authorization as opposed to ClientLogin which we have already marked as a deprecated authorization method. Best, - David Torres - AdWords API Team On Wednesday, November 14, 2012 2:55:54 PM UTC-5, Joey Muller wrote: > > I have developed a tool for my agency's internal clients. It uses a > scheduler to send automatica emails containing AdWords data. Now, some > other folks are interested in using this, but their AdWords accounts are > not linked to our MCC. What would be the best way to handle this? Would I > use a sign-on or authentication process using oAuth? Or would I store email > and password combinations in a database and use ClientLogin? I recall third > party PPC platforms like Marin and others use the email/password combo > solution, but I'm wondering if there is something slicker. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
