Changes

Jump to: navigation, search

Privacy/BestPractices/OAuth

320 bytes added, 22:32, 23 May 2011
Central OAuth Pattern
* authenticating API calls: the consumer uses credentials to authenticate its API calls against the data host.
=== Central OAuth Pattern Establishing Credentials ===
The most common There are a number of variations on the central OAuth patterntheme, in both OAuth 1especially when it comes to establishing credentials.0 and 2.0, works as follows:
* the consumer registers with the data host and obtains a <tt>consumer_key</tt>, which is considered public, and a <tt>consumer_secret</tt>, which should be kept private.
* Establishing Credentials:** a user interacting with a data consumer decides to connect it to her data host.** , triggering the consumer to redirect the user to the data host with a permission request.
* the user is prompted to approve the request from the specified data consumer, at which point the data host redirects the user's browser to the data consumer with a confirmation code. * the data consumer makes a direct API call to   === Making API Calls:** foo===
=== Differences between OAuth 1.0 and 2.0 ===
668
edits

Navigation menu