You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Unable to delete a file stored in Google Cloud Storage using Parse.Cloud.httpRequest #3837
Service account permissions set to ["Editor", "Storage Admin", "Storage Object Admin"]
Logs/Trace
Parse-server console output:
verbose: REQUEST for [DELETE] /parse/classes/Photo/HDLbppIQpB: {} method=DELETE, url=/parse/classes/Photo/HDLbppIQpB, host=192.168.0.190:1337, connection=keep-alive, content-length=195, origin=http://localhost:3003, user-agent=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36, content-type=text/plain, accept=*/*, referer=http://localhost:3003/, accept-encoding=gzip, deflate, accept-language=en-US,en;q=0.8,
Request failed with error:<?xml version='1.0' encoding='UTF-8'?><Error><Code>AccessDenied</Code><Message>Access denied.</Message><Details>Anonymous users does not have storage.objects.delete access to bucket <my bucket>.</Details></Error>
I've also successfully tested DELETE using Google OAuth 2.0 Playground using my personal gmail account set with same permissions as the service account used by Parse Server. So, I'm reasonably confident that my permissions are set correctly.
Activity
wookiem commentedon May 20, 2017
I've also successfully tested
DELETEusingGoogle OAuth 2.0 Playgroundusing my personal gmail account set with same permissions as the service account used by Parse Server. So, I'm reasonably confident that my permissions are set correctly.flovilmart commentedon May 20, 2017
Can you open the issue on the proper repository? https://github.com/parse-server-modules/Parse-server-gcs-adapter ?
wookiem commentedon May 20, 2017
@flovilmart Ah, sorry about that. I moved it over.
flovilmart commentedon May 20, 2017
No problem! We should probably have somethjng in the issue template to indicate it :)