These servlets will allow an App Engine user to quickly get started with the auth object interface from the main client. They will utilize the App Engine Datastore and Credentials to manage credentials on behalf of users.
Warning: starting with version 1.7, usage of this for OAuth 2.0 is deprecated. Instead use com.google.api.client.extensions.appengine.auth.oauth2.
This servlet fills in some of the required information for the AbstractCallbackServlet with reasonable defaults for App Engine. It will default the servlet to creating UrlFetchTransport objects whenever an HttpTransport is needed. It will also default the user identifier to the logged in App Engine user. This servlet requires that the App Engine user must be logged in to work correctly. This can be accomplished by adding a security constraint in your web.xml for the path at which this servlet will live.
Example that requires login for all pages:
<security-constraint> <web-resource-collection> <web-resource-name>any</web-resource-name> <url-pattern>/*</url-pattern> </web-resource-collection> <auth-constraint> <role-name>*</role-name> </auth-constraint> </security-constraint>
Warning: starting with version 1.7, usage of this for OAuth 2.0 is deprecated. Instead use com.google.api.client.extensions.appengine.auth.oauth2.AbstractAppEngineAuthorizationCodeCallbackServlet.
This class fills in some of the unknowns of the generic AbstractFlowUserServlet with reasonable defaults for App Engine. This servlet requires that the App Engine user must be logged in to work correctly.
Warning: starting with version 1.7, usage of this for OAuth 2.0 is deprecated. Instead use com.google.api.client.extensions.appengine.auth.oauth2.AbstractAppEngineAuthorizationCodeServlet.