client_secret.json vs client_secrets.json #506

Activity

1. mattwhisenhunt commented on May 18, 2018

   

   mattwhisenhunt

   on May 18, 2018

   Contributor

   More actions

   The name of the file is not important, its the content that counts. Depending on what language you are using and what environment your deploying to, you won't even have that json file.

   https://github.com/youtube is an official source and it appears their api-samples repo is a helpful collection code samples to interact, specifically, with Youtube. I don't think those samples are limited to examples of this client library or its sister client libraries of other languages.

   Google owns all the code, everyone agrees to that before their contribution is accepted: https://cla.developers.google.com/about/google-individual

   I am sorry you are feeling frustrated and I've tried to answer your questions. If you have more specific problems or some code that is not working I would be glad help.
2. mattwhisenhunt

   closed this as completedon May 18, 2018
3. charlesreid1 commented on May 18, 2018

   

   charlesreid1

   on May 18, 2018

   Last edited by charlesreid1

   ContributorAuthor

   More actions

   Thanks for the explanation. Another cause of confusion was that the name of the json file is specified in sample_tools so it isn't clear where that comes from (or that it's arbitrary). The sample_tools import shows up in the samples like the calendar sample but is also used in some documentation examples.

   Things started to click once I saw the Drive API example that explicitly goes through the whole process, where you specify yourself where the application's credentials live and where the Drive credentials will go. That made the 3-legged authentication process easier to see, and figure out why the Calendar API credentials were going in calendar.dat while Drive API credentials were going in credentials.json.

   Just this bit was all I needed:

   # Setup the Drive v3 API
   SCOPES = 'https://www.googleapis.com/auth/drive.metadata.readonly'
   store = file.Storage('credentials.json')
   creds = store.get()
   if not creds or creds.invalid:
       flow = client.flow_from_clientsecrets('client_secret.json', SCOPES)
       creds = tools.run_flow(flow, store)
   service = build('drive', 'v3', http=creds.authorize(Http()))
   

   Personally I don't think the sample_tools magic is necessary, just my 2 cents.
4. yoshi-automation

   added a commit that references this issue on May 29, 2020

   feat: add templates for python samples projects (#506)

   ...

   5b8be3b
5. busunkim96

   added a commit that references this issue on May 29, 2020

   feat: add templates for python samples projects (#506) (#924)

   ...

   c482712
6. gcf-merge-on-green

   added a commit that references this issue on Jun 2, 2020

   chore: release 1.9.0 (#925)

   ...

   cafb9e0
7. JustinBeckwith

   assigned

   mattwhisenhunt

   on Feb 1, 2021