Hi David, OAuth2 does not have long-lived OAuth tokens. It has short-lived access tokens that can be refreshed using the refresh token as needed. OAuth 1 does allow for long-lived access tokens. Note that we've not yet tested OAuth2 support with the AdWords API.
The OAuth playground may be able to help you test your implementation: http://googlecodesamples.com/oauth_playground/ - Kevin Winter AdWords API Team On Tuesday, November 15, 2011 7:06:38 AM UTC-5, [email protected] wrote: > > Thanks for the reply Kevin. I've reviewed the docs you've referenced, and > could not find the method to generate a long-lived access token - one that > does not require continued refresh token exchanges. I was looking for an > interactive panel to perform the OAuth2 dance; after completing I would > have a long lived access token. I could then use this token for my future > Reporting API access. > > I'll begin experimentation with my custom application (do not use the > client libraries) using "grant_type "password" in the OAuth2 dance steps > and see how this plays out. I found this information at the OAuth2 > documentation site: http://tools.ietf.org/html/draft-ietf-oauth-v2-22 in > section 4.3.2. > > David > > > > > -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
