[google-appengine] Re: [cloud-endpoint] [java] deployment and security

You could use Firebase[1] with App Engine to control who and what have access and where on your application. Or you could control the access of your app using the different role available for App Engine[2] [1] https://cloud.google.com/appengine/docs/standard/python/authenticating-users-firebase

[google-appengine] Re: [cloud-endpoint] [java] deployment and security

And how can I configure the same (security constraints ) for Nodejs? Couldn't find the solution yet... On Friday, July 28, 2017 at 10:28:58 PM UTC+3, Yannick (Cloud Platform Support) wrote: > > He

[google-appengine] Re: [cloud-endpoint] [java] deployment and security

Endpoint Protection offers security management which includes adequate securing list of endpoints that includes laptops, smartphones, desktops and other Internet of things. https://360.comodo.com/security-solutions/endpoint-protection/ On Monday, July 31, 2017 at 9:36:38 PM UTC+5:30, Yannick (C

[google-appengine] Re: [cloud-endpoint] [java] deployment and security

If you want to restrict access to your endpoint using an API key you should not have to worry about clients. You say you only want to server requests from a certain domain (eg: domain.com) correct? In that case users of that domain would make requests to it, and the server of domain.com would be

[google-appengine] Re: [cloud-endpoint] [java] deployment and security

Hi Yannick, Namespaces make sense for various environments - Prod / Stage, etc. I'm not 100% clear on the part where I restrict Google Endpoint to serve only the requests coming from domain.com. The thing I am trying to avoid is for "bad guys" calling my API from their machines. I can add cli

[google-appengine] Re: [cloud-endpoint] [java] deployment and security

Hello, welcome to the forums. 1) You can choose which URLs you want to restrict in your Java application using security constraints . That way only someone logged in as a developer or your applicat