Hi, Thanks for your detailed explanation of the problem, I'll make sure the dotnet client library maintainer take notice of this post. I would like to ask you to file an issue in the client library issue tracker, http://code.google.com/p/google-api-adwords-dotnet/issues/list
Thanks, -David Torres - AdWords API Team On Thursday, May 3, 2012 6:22:50 PM UTC-4, mpad...@marketingpilot.com wrote: > > So apparently, for my usage (where I'm not prompting for authorization > when trying to download a report or something like that but instead > prompting ahead of time and caching the access token), the first time I > call OAuthProvider.GenerateAccessToken, what that *really* means is "take > the user to Google for approval, and you'll get back a request token, even > though the name of the method implies we'll get the access token too", > whereupon I then call OAuthProvider.GenerateAccessToken *again* to > actually get the access token. Most people probably don't hit a similar > issue, because they are trying to load data when the user is prompted to > authorize, but my intention is to use this token for updating data behind > the scenes on a daily basis or something like that, so user interaction is > not guaranteed when actually doing something useful with the API. > > I can certainly live with this scenario (calling GenerateAccessToken > twice), but I think at minimum the Wiki on how to use OAuth with the .NET > client library needs updating. The *Loading existing AccessToken* section > states that the value of the access token would be available after calling > GenerateAccessToken, but that's clearly not the case after the first call > to it. (You either need to make an API call for some data or call > GenerateAccessToken again [which is what those API calls are doing] to get > the access token to cache.) > > In general, I would suggest providing a second method called > StartAuthorizationProcess or something to that effect to make it clear that > you're not actually getting the access token as a result of the first call. > I realize that it would be a compatibility break to force that on > everyone, so I'm merely requesting it as an option. I've been banging my > head against the wall for the better part of 3 days to figure this out. :) > -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
