!!! Overview
[{$pagename}] is a an open standard scalable [Protocol] for [Delegation] of [Authorization] to [server resources|Resource Server] using [HTTP]

Generally, [{$pagename}] is a solution to the [Password Anti-Pattern].

[{$pagename}] provides an open standard scalable method for [Relying Party] to Grant access to [server resources|Resource Server] on behalf of a [Resource Owner].

[{$pagename}] also provides a process for end-users to authorize [third-party|Relying Party] access to their [server resources|Resource Server] without sharing their credentials using [User-agent] redirections.[1]

!! OAuth 1.0
OAuth 1.0 is defined by the [Informational] [RFC 5849] in April 2010 and was [OBSOLETE]D by [RFC 6749].

!! [OAuth 2.0][2]
[OAuth 2.0] is an evolution of the [{$pagename}] [protocol] and is not backward compatible with OAuth 1.0. [OAuth 2.0] focuses on client developer simplicity while providing specific [authorization] flows for web applications, desktop applications, [Mobile Devices], and living room devices. The specification and associated RFCs are being developed within the [IETF] OAuth WG; the main framework was published in October 2012. 

The [OAuth 2.0 Framework|http://tools.ietf.org/html/rfc6749|target='_blank'] and [Bearer Token Usage|http://tools.ietf.org/html/rfc6750|target='_blank'] were published in October 2012. Other documents are still being worked on within the OAuth working group.

!! Some OAuth Implementations
* Facebook's new Graph API only supports OAuth 2.0. 
* Google supports OAuth 2.0 as the recommended authentication mechanism for all of its APIs. 
* As of 2011 Microsoft has added OAuth 2.0 experimental support to their APIs.

!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]

----
* [#1] - [http://en.wikipedia.org/wiki/OAuth] - Retrieved 2013-03-29
* [#2] - based loosely on [http://en.wikipedia.org/wiki/OAuth] - Retrieved 2013-03-29