Full API Access does not work for Taskqueue

别说谁变了你拦得住时间么 提交于 2019-12-13 02:07:51

问题


I have a new Debian GCE VM which has full access to Google Cloud services. I'm able to access most of the services from this instance. However I'm unable to access task queues.

host:~/home$ curl 
"https://www.googleapis.com/taskqueue/v1beta2/projects/project/taskqueues/
my-queue/tasks" -H "Authorization":"Bearer xxxxxxxxxxxxxxxxxxxxxxxxxxx"
{
 "error": {
   "errors": [
   {
    "domain": "global",
    "reason": "insufficientPermissions",
    "message": "Insufficient Permission"
   }
 ],
"code": 403,
"message": "Insufficient Permission"
}
}

From my other VM which has fine grained access to individual services, I'm able to access task queue. Is this a known issue?


回答1:


It's not possible, I got the answer from Google about TaskQueue REST API:

The REST API has it's own auth mechanism using access control lists. Since this API is experimental, we have no plans of offering full IAM integration. Instead, we are building a new API which will replace this one with full IAM support.

A workaround is to set export GOOGLE_APPLICATION_CREDENTIALS=/path/to/servicek‌​ey.json.



来源:https://stackoverflow.com/questions/37479204/full-api-access-does-not-work-for-taskqueue

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!