Databases
StackOverflow2013
Postsdbo
POCreating files go to which account using Google Drive APIs when authenticating with a service account?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCreating files go to which account using Google Drive APIs when authenticating with a service account?
    text
    copied!<p>I'm trying to make use of the Google Drive APIs to send a log file created by our application to our company's Google Drive Account that we share for Android Development. Most of the examples showed how to use oAuth2 to authenticate with the end-user's Google Drive Account, but we want the files to be sent to just our Google Drive Account. </p> <p>After some searching I found that I should create an API project for our app and use a Service account associated with that API Project to generate a key which we include in our project as a raw resource to authenticate using oAuth2 to get a GoogleCredential which is needed to build the Drive service we will use to make our API calls.</p> <p>After authenticating properly, I was able to insert a file using the code example on the Google Drive API site and that appears to work properly, however I cannot see the file in our Google Drive account which created the API Project/Service account. Despite this, if I call Drive.files().list().execute() and output the FileList to a string I was able to see the files our app has previously inserted into the Service account's Google Drive.</p> <p><strong>So my question is:</strong> Is there a new Google Drive account created for the Service account that is separate from the Google Drive account that created the Service account? If so, is there a way to login to that account and view the files using the normal Google Drive Web UI so that we can get to the log files without writing some other application that authenticates with the Service account and then grabs the files?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload