Closed jkobject closed 5 years ago
Terra has been talking for a while about switching to their own OAuth system, instead of using Google tokens, and apparently they finally made the switch. In their own infinite wisdom, they of course, did not tell anybody. I'll loop @francois-a and @dheiman into this, as this is going to require fixes at both the dalmatian and fiss stack levels. In the meantime, however, it looks like we're totally locked out of the API
right when I am doing my depmap omics release :o. Tell me if there is anything I can do to help.
Best,
It appears that Terra had not actually made the switch yet, but they did have a different backend issue with authentication. The issue is resolved for now, but be on the lookout for their actual transition to their own OAuth system in the future
Hello, I'm facing the exact same issue as OP. What was the solution for successfully making API calls to Terra, if any?
For context, I'm using a VM to do this. So far, I've tried registering the service account with Terra by following Step 2 in this guide. However, I still run into the same error as OP. I've also tried using my personal gcloud account, which works if I'm creating a job submission on my local machine, but not when I do it on the VM and I get the same error message.
Any insights would be appreciated. Thanks!
when trying todo any action on Terra, I get this error message, preventing me from running any pipeline.
Do you have any idea what to do here? I did
gcloud auth application-default login
a bunch and even reinstalled firecloud to the latest version but nothing seems to work.Thanks!