Re: Simple Questions about the OAuth2 access_token and Redirect URI

Thanks to Ewan's fantastic tutorial I know have OAuth2 sorted. Using his simple example everything I've spent the last few weeks reading now makes sense. Cheers Ewan! On Thursday, September 12, 2013 10:49:18 AM UTC, Ewan Heming wrote: > > Hi Alan, > > You might find the one on the OAuth > Play

Re: Simple Questions about the OAuth2 access_token and Redirect URI

Hi Alan, You might find the one on the OAuth Playgroundeasier to get going quickly. Also, you might just need to refresh your access token with the code you've already written already. Just run the following code before making API calls:

Re: Simple Questions about the OAuth2 access_token and Redirect URI

Okay, I'm going to follow Ewan Heming's tutorial and see how I get on with that: http://www.ewanheming.com/adwords-api-oauth-tutorial Thanks On Tuesday, September 10, 2013 11:14:42 PM UTC+1, Alan Coleman wrote: > > Hi David, > > Many thanks for taking the time to reply. > > I understand the con

Re: Simple Questions about the OAuth2 access_token and Redirect URI

Hi David, Many thanks for taking the time to reply. I understand the concepts of OAuth2, I've been through all of the documentation many times and it all makes sense. Much of the documentation seems to be geared towards web applications for anonymous users, whilst this is very useful it just a

Re: Simple Questions about the OAuth2 access_token and Redirect URI

Hi Alan, You use your refresh token to generate new access tokens. Then the access token is the one you include in the API calls so your request get properly authorized, as you mentioned. So if you were able to generate a refresh token already, a call to https://accounts.google.com/o/oauth2/t

Re: Simple Questions about the OAuth2 access_token and Redirect URI

Hi Brett, Thanks again for replying, I'm still confused about the returning * access_token* that my app will need to use the API. Do I need to handle or store it somewhere? I understand that OAuth2 uses the *client_id*, *client_secret* and * refresh_token* to get an *access_token*, which in tur

Re: Simple Questions about the OAuth2 access_token and Redirect URI

Alan, here's a link to Google's official explanation of the different types of projects. I suggest that, instead of thinking of these different project types in relation to what _your_ application is, think of them in relation

Simple Questions about the OAuth2 access_token and Redirect URI

Hello everyone, Apologies for my lack of understanding surrounding this topic and continuous post about the basics of the protocol. I'm passing *client_id*, *client_secret* and *refresh_token* to the Google OAuth2 Authorisation Server but my application is returning an *access token required*