2 items
The OAuth 2.0 Playground is a tool for developers that simplifies experimentation with the OAuth 2.0 protocol and APIs. Trying out some requests in the OAuth 2.0 playground can help you understand how the protocol functions and make life easier when the time comes to use OAuth in your own code. With the OAuth 2.0 Playground you can walk through each step of the OAuth 2.0 flow for servers (auth code) and client apps (Implicit): - Authorizing API scopes - Exchanging authorization tokens - Refreshing access tokens - Sending authorized requests to APIs At each step the Playground displays the full HTTP requests and responses. The playground is pre-configured to use with Google's OAuth 2.0 endpoints and APIs so that you can quickly and easily play around with these. It is also configurable (click on the configure icon on the top right) so that you can specify and use any OAuth 2.0 endpoints as long as they implement OAuth 2.0 draft 10 and above. The OAuth 2.0 playground is integrated with Google Drive. You can simulate the open-with flow of a Drive file with the OAuth 2.0 playground, and then finish the OAuth 2.0 flow with the playground and play HTTP requests to the Drive REST API. --- OAuth 2.0 is an open protocol for authorization and authentication that is currently being drafted. Please see http://oauth.net/2/ for more details. The OAuth and OAuth 2.0 logos used in the promotional images and as logos are the work of Chris Messina and are used under the terms of the Creative Commons Attribution ShareAlike 3.0 license. Please see: http://wiki.oauth.net/w/page/12238520/Logo
Aug 24, 2016
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.