You may use a Service Account which is a special type of Google account that belongs to your application. It is worthwhile to take a look at service account best practices and also this guide shows how to set up authentication for server to server production applications.
--
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 google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
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/dbf82f1b-5aab-465c-b8ca-77669026eee7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi again,
You can either use "GOOGLE_APPLICATION_CREDENTIALS" environment variable for authenticating server to server or use Cloud Identity-Aware Proxy. The difference is that Identity-Aware Proxy (IAP) can be only applied on App Engine and the Cloud HTTPS Load Balancer, but the mentioned environment variable has a project wide scope and can be used for all the resources/APIs you have in your project.
I should also add that “X-Appengine-Inbound-Appid” header is added to the request by the URLFetch service which is only available in App Engine Standard environment.
Hi Narendras,
I should note that Google Groups are reserved for general questions on Google Cloud Platform-end and not for reporting issues. If you think the issue is on GCP side and not from your code/configuration, I recommend to report it to the Issue Tracker so that we would be able to dig into it efficiently