Hey Currently using googles cloud vision api in an electron app. The

Question

Hey Currently using googles cloud vision api in an electron app. The

docs tell me to create a service account, and that this service account needs appropriate permissions to access the api. Then tells you to give it the owner role (wtf?!!)
It also recommends to then limit the permissions later. But doesn't tell you how and just links to the general IAM docs (thanks)

But when i create a service account with no permissions at all, it can access the cloud vision api just fine. In fact, there is no role at all that related to cloud vision api. So despite the docs saying you have to set permissions, this is totally untrue.

Because of that I don't know if it would be save to ship the key file with the application. All i want that service account to be able to access is the cloud vision api ,which is literally the only thing this gcp project has enabled. But I'm not sure what resources such a service account can access by default, because the docs are clearly lying. Is it safe to embed the key file? Or do I actually have to build a fuckin proxy just So this key can stay safe. Oauth is not an Option and an api key is definitely insecure so not doing that

0

31.10.2021

2 ответов

12 просмотров

palone Автор вопроса

Pedro Aguiar
Oh man it's one of the great mysteries of humanity...

The wrappers I've seen wanted me to use either oauth (which i can't due to business requirements) or an service account keyfile

0

31.10.2021

Pedro Aguiar · Accepted Answer

Pedro Aguiar

Oh man it's one of the great mysteries of humanity. I've never seen anyone who managed to use the official Google API. That is, without the help of a third-party lib because it's just too bureaucratic and the authentication process is badly documented in my option. I wonder if that's a way they found to push for Google Apps Scripts.

0

31.10.2021

Похожие чаты

Hey Currently using googles cloud vision api in an electron app. The

2 ответов

Похожие вопросы