We are trying to migrate our older application to use the OAuth2 authentication that Google now supports, but we are having some trouble understanding a few things regarding application creation. If anyone could shed some light on these questions, it would be very helpful.
Background: We manage AdWords account for many clients, and are trying to find the simplest way to seamlessly upgrade. Our application is a web-server application. 1) Do we need a client-id for each client's account that we manage? Or only a single ID for our application and then have our clients *allow* our application to manage their accounts? 2) Similarly,for the access token that is returned; do we need one for each client or one for our application that we can send with every request? I guess the simpler way to ask the question is how do we register an application that will need access to many clients' accounts in the simplest manner possible? Thanks. Hunter. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
