Method of presenting the access token to the resource server as specified in Accessing Protected Resources.
Listener for refresh token results.
OAuth 2.0 credential persistence store interface to provide a fully pluggable storage mechanism.
Thread-safe OAuth 2.0 authorization code flow that manages and persists end-user credentials.
Authorization code flow builder.
OAuth 2.0 URL builder for an authorization web page to allow the end user to authorize the application to access their protected resources and that returns an authorization code, as specified in Authorization Code Grant.
OAuth 2.0 URL parser for the redirect URL after end user grants or denies authorization as specified in Authorization Response.
OAuth 2.0 request for an access token using an authorization code as specified in Access Token Request.
OAuth 2.0 URL builder for an authorization web page to allow the end user to authorize the application to access their protected resources, as specified in Authorization Endpoint.
OAuth 2.0 helper for accessing protected resources using the Bearer Token specification.
Client credentials specified as URL-encoded parameters in the HTTP request body as specified in Client Password
Thread-safe OAuth 2.0 helper for accessing protected resources using an access token, as well as optionally refreshing the access token when it expires using a refresh token.
Thread-safe OAuth 2.0 credential refresh listener that stores the refresh token response in the credential store.
Thread-safe in-memory implementation of a credential store.
OAuth 2.0 request to refresh an access token using a refresh token as specified in Refreshing an Access Token.
OAuth 2.0 parser for an error access token response as specified in Error Response.
OAuth 2.0 request for an access token as specified in Obtaining Authorization.
OAuth 2.0 JSON model for a successful access token response as specified in Successful Response.
Exception thrown when receiving an error response from the token server as specified in Error Response
Before using this library, you will typically need to register your application with the authorization server to receive a client ID and client secret. See Client Registration.
These are the typical steps of the web server flow based on an authorization code, as specified in Authorization Code Grant:
AuthorizationCodeRequestUrlto grant your application access to the end user's protected data.
AuthorizationCodeResponseUrlto parse the authorization code.
Credential. Expired access tokens will automatically be refreshed using the refresh token (if applicable).
These are the typical steps of the the browser-based client flow specified in Implicit Grant:
BrowserClientRequestUrlto grant your browser application access to the end user's protected data.
Warning: this package is experimental, and its content may be changed in incompatible ways or possibly entirely removed in a future version of the library.
Copyright © 2011-2013 Google. All Rights Reserved.