The last response is correct. The client_id and client_secret identify your
application - in a similar way to the developerToken, but only to the
authorization servers. If you need to permit many users to use your
application then you should look at the Web Server Application OAuth2
Client ID and Client secret are yours, just like developer token. They have
to be provided by your application. You get these when you register an API
Project and its Oauth web client via Google Cloud
Consolehttps://cloud.google.com/console(or Google APIs Console, now
deprecating too).
--
--
HI,
Since ClientLogin is depreciating, there is an issue I will face.
Before I set up an application where any user can login in to it and
download as many reports as possible and all they required was their
adwords email and password. The developer token was hard coded into the
application.
