Cloud Translation API VS Identity-Aware Proxy

Dude just leave, if you want to know what the snake is saying use https://cloud.google.com/translate. Source: 5 months ago

ChatGPT isn't the only AI in town and there are services optimized for translation that might work better for this use case. Some accept HTML, PDF, etc. And send back a translation of the content. Google's is available here: https://cloud.google.com/translate That being said, taking something in French that is intensely academic and converting it to English might not be a straight-up translation task - having... - Source: Hacker News / about 1 year ago

Also machine translation at scale isn't free. Using Google translate word by word isn't how large translations are done. People pass text to # paid service like the Google Translation API: https://cloud.google.com/translate. Source: over 1 year ago

You need a 2-steps pipeline. First a speech to text. Then text translation. You can use existing Google APIs for both. There are many other options available. Https://cloud.google.com/speech-to-text Https://cloud.google.com/translate. Source: over 1 year ago

I use Google's Translation API: https://cloud.google.com/translate. Source: over 1 year ago

That is not how you do Zero Trust. You want to use an Identity Aware Proxy. There are lots of ways you can implement this with Google as your core auth. For example Pomerium or oauth2-proxy. Source: 5 months ago

It's like this, which may be what you're referring to: https://cloud.google.com/iap. Source: about 1 year ago

If System A is operated by a user in realtime, I would lean toward using strong user or app identity (Firebase Authentication, Firebase App Check or Identity-Aware Proxy). But that would mean major modifications to System A, and you described it as a "closed system" so maybe that's not possible? Source: about 1 year ago

Put Identity-Aware Proxy in front of your application. It will block anyone who is not from the right domain or in your access control list. This option is useful if you only want to allow a list of users known ahead of time, like for a company-internal app. Source: over 1 year ago

You could use IAP but that would require that they sign in i.e. When they try to access the application, it would ask them to sign in and then it will reject any sign in which is not from the email of *@customerdomain.com. If you don't wish to use IAP, you can also include the entry 'login: always' in your app.yaml which then forces users to sign in and your code will check that the email address is from... Source: over 1 year ago