Databases
StackOverflow2013
Postsdbo
POCannot get service account authorization to work on GCS script using Python client lib APIs
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCannot get service account authorization to work on GCS script using Python client lib APIs
    primarykey
    data
    text
    <p>In attempting to write a python script to access GCS using service-based authorization, I have come up with the following. Note that 'key' is the contents of my p12 file.</p> <p>I am attempting to just read the list of buckets on my account. I have successfully created one bucket using the web interface to GCS, and can see that with gsutil. </p> <p>When I execute the code below I get a 403 error. At first I thought I was not authorized correctly, but I tried from this very useful web page (which uses web-based authorization), and it works correctly. <a href="https://developers.google.com/apis-explorer/#p/storage/v1beta1/storage.buckets.list?projectId=" rel="nofollow">https://developers.google.com/apis-explorer/#p/storage/v1beta1/storage.buckets.list?projectId=</a>&amp;_h=2&amp;</p> <p>When I look at the headers and query string and compare them to the keaders and query of the website-generated request I see that there is no authorization header, and that there is no key= tag in the query string. I suppose I thought that the credential authorization would have taken care of this for me. </p> <p>What am I doing wrong?</p> <p>code:</p> <pre><code>credentials = SignedJwtAssertionCredentials( 'xxx-my-long-email-from-the-console@developer.gserviceaccount.com', key, scope='https://www.googleapis.com/auth/devstorage.full_control') http = httplib2.Http() http = credentials.authorize(http) service = build("storage", "v1beta1", http=http) # Build the request request = service.buckets().list(projectId="159910083329") # Diagnostic pprint.pprint(request.headers) pprint.pprint(request.to_json()) # Do it! response = request.execute() </code></pre> <p>When I try to execute I get the 403. </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjterrace
    1. USDavid V
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCannot get service account authorization to work on GCS script using Python client lib APIs
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCannot get service account authorization to work on GCS script using Python client lib APIs
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POCannot get service account authorization to work on GCS script using Python client lib APIs
      1. USBrian Dorsey
      1. VTFavorite
    1. COAre you on AppEngine? If not, have you tried using boto like the [docs](https://developers.google.com/storage/docs/gspythonlibrary) suggest?
      singulars
      1. POCannot get service account authorization to work on GCS script using Python client lib APIs
      1. USjterrace
    2. COThanks for fixing my formatting! I took this approach because boto does not support service account authentication. This is for a standalone service running locally on a device (a security camera), it is not an AppEngine use case. The camera uploads its media to GCS.
      singulars
      1. POCannot get service account authorization to work on GCS script using Python client lib APIs
      1. USDavid V
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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