Re: Migration from clientLogin to oAuth2

Hi Derek, Shruti, >From an older thread , it looks like the error you mentioned happens when the clientId in your App.config doesn't match the one for which

Re: Migration from clientLogin to oAuth2

Hi, Did you confirm that you are creating a *native/installed application* in the cloud console? Also, have you gone through the OAuth wiki page for the client library you are using? That page will contain step-by-step instructions for configuring the library for OAuth. Thanks, Josh, AdWords

Re: Migration from clientLogin to oAuth2

I am experiencing the exact same problem and I can't figure out where I'm going wrong. Should I send over my source code? On Monday, 20 October 2014 19:05:08 UTC+1, Josh Radcliff (AdWords API Team) wrote: > > Hi, > > Could you send a screenshot of your application setup from the Developers > C

Re: Migration from clientLogin to oAuth2

Hi, Could you send a screenshot of your application setup from the Developers Console *only to me* by clicking *Reply to Author*? Thanks, Josh, AdWords API Team On Monday, October 20, 2014 1:09:09 PM UTC-4, Shruti wrote: > > Hi, > > I have created the client ID for the native application (same

Re: Migration from clientLogin to oAuth2

Hi, I have created the client ID for the native application (same as installed application, I believe). I have been following the steps shown on - https://www.youtube.com/watch?v=WifY2fFyaMw for the native application. Thanks On Monday, October 20, 2014 12:50:08 PM UTC-4, Josh Radcliff (AdWord

Re: Migration from clientLogin to oAuth2

Hi, I see - I think the problem is that the project you created in the Developers Console is a *Web application*, but OAuthTokenGenerator.exe assumes you have a *Native application*. If you create a *Native application* as described here

Re: Migration from clientLogin to oAuth2

Hi Josh, Thanks for the reply. I have gone through the step by step instructions for generating the refresh token. I'm using the OAuthTokenGenerator.exe, entering my clientID and the client secret after which I can see the consent screen. Once I click the 'Accept' button, I see a screen showin

Re: Migration from clientLogin to oAuth2

Hi, Sorry to hear this process has been frustrating for you. Have you looked at the step-by-step instructions for OAuth2 on the .NET library's wiki pages? https://github.com/googleads/googleads-dotnet-lib/wiki/Using-OAuth2TokenGenerator The *invalid_client* message you received in step 5 usuall

Re: Migration from clientLogin to oAuth2

On Friday, October 17, 2014 3:55:23 PM UTC-4, Shruti wrote: > > Hi, > > I'm trying to migrate an application from using ClientLogin to oAuth2. I > have followed the instructions as given here - > https://developers.google.com/adwords/api/docs/guides/clientlogin-to-oauth2-single-mcc > > and ht

Migration from clientLogin to oAuth2

Hi, I'm trying to migrate an application from using ClientLogin to oAuth2. I have followed the instructions as given here - https://developers.google.com/adwords/api/docs/guides/clientlogin-to-oauth2-single-mcc and https://developers.google.com/adwords/api/docs/guides/authentication As indica