
Handlers that provide powerful access to application data and functionality. In the following example, users must be logged in to access the /profile/ URL, and only admin-Users must be administrators of the application in addition to being signed.required-Users must be signed in to access the URL and execute the handler.


If you choose to use the Users API (preferred), be careful with the user ID. Use OAuth or the Users API to keep your application and your dataĪuthentication must be done via the Users API ( Python, Java) or OAuth ( Python, Java). Using a non-standard authentication mechanism is more work than reusing an existing library/API, and almostĪlways results in big security blunders. (formerly Google Apps) accounts that is, no accounts. You must diligently control all three roles.įor applications that process user data, you must limit administrative access to corporate-managed GSuite While Owner and Developer are especially powerfulīecause they can modify the application code, even the Viewer role has access to logs (which may contain data

Also note that this document only applies toĬlassic App Engine, as the App Engine FlexibleĮnvironment may not be used at this time.Īpp Engine Security & Privacy Requirements AdministrationĪpp Engine provides three roles with different levels of access to theĪdministration Console: Viewer, Developer, and Owner. In addition to the requirements specific to App Engine, you must also follow the relevant guidelines in the Google Partner Security Documentation. The audience for this document is external vendors developing applications for Google.
Google app engine sdk for python 2.7 how to#
We include examples that demonstrate how to implement these requirements. This document lists the security requirements for developing applications in Python or Java on the Google AppĮngine platform.
