You can check the X-Appengine-Inbound-Appid header on requests coming it to your service. On App Engine, it will be set by Google, so you can trust it. Check that it matches the project(s) you expect, and return some HTTP error if it doesn't match. See:
https://cloud.google.com/appengine/docs/go/appidentity/ On Wednesday, January 4, 2017 at 2:39:13 PM UTC-5, Mateusz Haligowski wrote: > > Hi google-appengine, > I started playing with GAE a couple of weeks ago and absolutely love it. I > created a bunch of REST services with Go and deployed them to GAE. I've > also created a webapp that talks to my backend services. > > Now, I want to handle the user authentication with Auth0 on the webapp > side, and came to realization that my backend services are publicly > available. My question is: what is the approach to secure them? Is there > any way to tell GAE "Accept only http(s) calling from other GAE services?". > > Thanks, > Mateusz > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/5badeb18-f819-4f11-acf0-ff55d527eab8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
