View source for OAuth

{{short description|Open standard for authorization}}
{{selfref|For MediaWiki's (the software used by Wikipedia) OAuth support, see [[mw:Help:OAuth]]}}
{{Use dmy dates|date=June 2020}}
{{Multiple issues|
{{Unreliable sources|date=November 2023}}
{{Primary sources|date=November 2023}}
}}
{{Infobox technology standard
| title             =
| long_name         =
| image             = Oauth logo.svg
| image_size        = 100px
| alt               =
| caption           = Unofficial logo designed by [[Chris Messina (open-source advocate)|Chris Messina]]
| abbreviation      =
| native_name       = <!-- Name in local language. If more than one, separate using {{plain list}} -->
| native_name_lang  = <!-- ISO 639-1 code e.g. "fr" for French. If more than one, use {{lang}} inside native_name items instead -->
| status            =
| year_started      = <!-- {{Start date|YYYY|MM|DD|df=y}} -->
| first_published   = <!-- {{Start date|YYYY|MM|DD|df=y}} -->
| version           = 2.0
| version_date      =
| preview           =
| preview_date      =
| organization      = [[Internet Engineering Task Force]]
| committee         =
| series            =
| editors           =
| authors           =
| base_standards    =
| related_standards =
| predecessor       =
| successor         =
| domain            =
| license           =
| copyright         =
| website           = {{cite web|url=https://datatracker.ietf.org/doc/html/rfc6749|title=The OAuth 2.0 Authorization Framework|date=October 2012 |last1=Hardt |first1=Dick }}
}}
'''OAuth''' (short for '''open authorization'''<ref name="NIST">{{cite web |title=Open Authorization - Glossary {{!}} CSRC |url=https://csrc.nist.gov/glossary/term/open_authorization |website=csrc.nist.gov}}</ref><ref name="RFC6749">{{Cite journal|last=Hardt|first=Dick|editor-first1=D |editor-last1=Hardt |date=October 2012|title=RFC6749 - The OAuth 2.0 Authorization Framework|url=https://tools.ietf.org/html/rfc6749|url-status=live|archive-url=https://web.archive.org/web/20121015184712/http://tools.ietf.org/html/rfc6749|archive-date=15 October 2012|access-date=10 October 2012|publisher=[[Internet Engineering Task Force]]|doi=10.17487/RFC6749 }}</ref>) is an open standard for access [[Delegation (computer security)|delegation]], commonly used as a way for internet users to grant websites or applications access to their information on other websites but without giving them the passwords.<ref>{{Cite web |last=Whitson |first=Gordon |title=Understanding OAuth: What Happens When You Log Into a Site with Google, Twitter, or Facebook |url=http://lifehacker.com/5918086/understanding-oauth-what-happens-when-you-log-into-a-site-with-google-twitter-or-facebook |url-status=live |archive-url=https://web.archive.org/web/20140424052409/http://lifehacker.com/5918086/understanding-oauth-what-happens-when-you-log-into-a-site-with-google-twitter-or-facebook |archive-date=24 April 2014 |access-date=15 May 2016 |website=[[Lifehacker]]}}</ref><ref>{{Cite journal|last=Henry|first=Gavin|date=January 2020|title=Justin Richer on OAuth|journal=IEEE Software|volume=37|issue=1|pages=98–100|doi=10.1109/MS.2019.2949648|issn=0740-7459|doi-access=free}}</ref> This mechanism is used by companies such as [[Amazon (company)|Amazon]],<ref>{{Cite web |title=Amazon & OAuth 2.0 |url=https://login.amazon.com/ |url-status=live |archive-url=https://web.archive.org/web/20171208010412/https://login.amazon.com/ |archive-date=8 December 2017 |access-date=15 December 2017}}</ref> [[Google]], [[Meta Platforms]], [[Microsoft]], and [[Twitter]] to permit users to share information about their accounts with third-party applications or websites.
Generally, the OAuth protocol provides a way for resource owners to provide a [[client application]] with secure delegated access to server resources. It specifies a process for resource owners to authorize third-party access to their server resources without providing credentials. Designed specifically to work with [[Hypertext Transfer Protocol]] (HTTP), OAuth essentially allows [[access token]]s to be issued to third-party clients by an authorization server, with the approval of the resource owner. The third party then uses the access token to access the protected resources hosted by the resource server.<ref name="RFC6749" />
== History ==
[[File:Without-oauth.png|alt=Authorization flow without Oauth.|thumb|A hypothetical authorization flow where login information is shared with a third-party application. This poses many security risks which can be prevented by the use of OAuth authorization flows.]]
[[File:Abstract-flow.png|alt=A high-level overview of Oauth 2.0 authorization flow.|thumb|A high-level overview of Oauth 2.0 flow. The resource owner credentials are used only on the authorization server, but not on the client (e.g. the third-party app).]]
OAuth began in November 2006 when [[Blaine Cook (programmer)|Blaine Cook]] was developing the [[Twitter]] [[OpenID]] implementation. Meanwhile, [[Gnolia|Ma.gnolia]] needed a solution to allow its members with OpenIDs to authorize [[Dashboard (macOS)|Dashboard Widgets]] to access their service. Cook, [[Chris Messina (open-source advocate)|Chris Messina]] and Larry Halff from Magnolia met with [[David Recordon]] to discuss using OpenID with the Twitter and Magnolia [[Application Programming Interface|API]]s to delegate authentication. They concluded that there were no open standards for API access delegation.<ref>{{Cite web |title=Introduction |url=https://oauth.net/about/introduction/ |url-status=live |archive-url=https://web.archive.org/web/20181121204056/https://oauth.net/about/introduction/ |archive-date=21 November 2018 |access-date=21 November 2018 |website=oauth.net}}</ref>
The OAuth [[discussion group]] was created in April 2007, for a small group of implementers to write the draft proposal for an open protocol. DeWitt Clinton from [[Google]] learned of the OAuth project, and expressed his interest in supporting the effort. In July 2007, the team drafted an initial specification. Eran Hammer joined and coordinated the many OAuth contributions creating a more formal specification. On 4 December 2007, the OAuth Core 1.0 final draft was released.<ref>{{Cite web |date=4 December 2007 |title=OAuth Core 1.0 |url=http://oauth.net/core/1.0/ |url-status=live |archive-url=https://web.archive.org/web/20151125184848/http://oauth.net/core/1.0/ |archive-date=25 November 2015 |access-date=16 October 2014}}</ref>
At the 73rd [[Internet Engineering Task Force]] (IETF) meeting in [[Minneapolis]] in November 2008, an OAuth [[Birds of a feather (computing)|BoF]] was held to discuss bringing the protocol into the IETF for further standardization work. The event was well attended and there was wide support for formally chartering an OAuth working group within the IETF.
The OAuth 1.0 protocol was published as <nowiki>RFC 5849</nowiki>, an informational [[Request for Comments]], in April 2010. Since 31 August 2010, all third party Twitter applications have been required to use OAuth.<ref>{{Cite web |last=Chris Crum |date=31 August 2010 |title=Twitter Apps Go OAuth Today |url=http://www.webpronews.com/twitter-apps-go-oauth-today-2010-08/ |url-status=live |archive-url=https://web.archive.org/web/20170731164856/http://www.webpronews.com/twitter-apps-go-oauth-today-2010-08/ |archive-date=31 July 2017 |access-date=31 July 2017 |website=WebProNews.com}}</ref>
The OAuth 2.0 framework was published considering additional use cases and extensibility requirements gathered from the wider IETF community. Albeit being built on the OAuth 1.0 deployment experience, OAuth 2.0 is not backwards compatible with OAuth 1.0. OAuth 2.0 was published as <nowiki>RFC 6749</nowiki> and the Bearer Token Usage{{huh|date=January 2023}} as <nowiki>RFC 6750</nowiki>, both standards track Requests for Comments, in October 2012.<ref name="RFC6749" /><ref>{{Cite journal|last1=Jones|first1=Michael|last2=Hardt|first2=Dick|date=October 2012|title=RFC6750 - The OAuth 2.0 Authorization Framework: Bearer Token Usage|url=https://tools.ietf.org/html/rfc6750|url-status=live|archive-url=https://web.archive.org/web/20121015232219/http://tools.ietf.org/html/rfc6750|archive-date=15 October 2012|access-date=10 October 2012|publisher=[[Internet Engineering Task Force]]|doi=10.17487/RFC6750 }}</ref>
The OAuth 2.1 Authorization Framework is in draft stage and consolidates the functionality in the RFCs OAuth 2.0, OAuth 2.0 for Native Apps, Proof Key for Code Exchange, OAuth 2.0 for Browser-Based Apps, OAuth Security Best Current and Bearer Token Usage.<ref name=":0">{{Cite journal|last1=Lodderstedt|first1=Torsten|last2=Hardt|first2=Dick|last3=Parecki|first3=Aaron|title=The OAuth 2.1 Authorization Framework|url=https://tools.ietf.org/html/draft-ietf-oauth-v2-1-00.html|access-date=2020-11-22|website=tools.ietf.org|date=13 October 2012 |language=en}}</ref>
== Security issues ==
=== OAuth 1.0 ===
On 23 April 2009, a [[session fixation]] security flaw in the 1.0 protocol was announced. It affects the OAuth authorization flow (also known as "3-legged OAuth") in OAuth Core 1.0 Section 6.<ref>{{Cite web |date=23 April 2009 |title=OAuth Security Advisory: 2009.1 |url=http://oauth.net/advisories/2009-1 |url-status=live |archive-url=https://web.archive.org/web/20160527002938/http://oauth.net/advisories/2009-1/ |archive-date=27 May 2016 |access-date=23 April 2009 |website=oauth.net}}</ref>
Version 1.0a of the OAuth Core protocol was issued to address this issue.<ref>{{Cite web |title=OAuth Core 1.0a |url=http://oauth.net/core/1.0a |url-status=live |archive-url=https://web.archive.org/web/20090630092220/http://oauth.net/core/1.0a |archive-date=30 June 2009 |access-date=17 July 2009 |website=oauth.net}}</ref>
=== OAuth 2.0 ===
In January 2013, the Internet Engineering Task Force published a threat model for OAuth 2.0.<ref name="RFC6819">{{Cite journal |last1=Lodderstedt |first1=Torsten |last2=McGloin |first2=Mark |last3=Hunt |first3=Phil |editor-first1=T |editor-last1=Lodderstedt |date=January 2013 |title=RFC6819 - OAuth 2.0 Threat Model and Security Considerations |url=https://tools.ietf.org/html/rfc6819.html |url-status=live |archive-url=https://web.archive.org/web/20200630000422/https://tools.ietf.org/html/rfc6819 |archive-date=30 June 2020 |access-date=29 June 2020 |website=[[Internet Engineering Task Force]] |doi=10.17487/RFC6819 |language=en|doi-access=free }}[rfc:6819 OAuth 2.0 Threat Model and Security Considerations]. Internet Engineering Task Force. Accessed January 2015.</ref> Among the threats outlined is one called "Open Redirector"; in early 2014, a variant of this was described under the name "Covert Redirect" by Wang Jing.<ref name="OAuth_Covert_Redirect">{{Cite web |date=4 May 2014 |title=OAuth Security Advisory: 2014.1 "Covert Redirect" |url=http://oauth.net/advisories/2014-1-covert-redirect/ |url-status=live |archive-url=https://web.archive.org/web/20151121111134/http://oauth.net/advisories/2014-1-covert-redirect/ |archive-date=21 November 2015 |access-date=10 November 2014 |website=oauth.net}}</ref><ref name="CNET">{{Cite web |date=2 May 2014 |title=Serious security flaw in OAuth, OpenID discovered |url=http://www.cnet.com/news/serious-security-flaw-in-oauth-and-openid-discovered/ |url-status=live |archive-url=https://web.archive.org/web/20151102002904/http://www.cnet.com/news/serious-security-flaw-in-oauth-and-openid-discovered/ |archive-date=2 November 2015 |access-date=10 November 2014 |website=[[CNET]]}}</ref><ref name="PhysOrg">{{Cite web |date=3 May 2014 |title=Math student detects OAuth, OpenID security vulnerability |url=http://phys.org/news/2014-05-math-student-oauth-openid-vulnerability.html |url-status=live |archive-url=https://web.archive.org/web/20151106024436/http://phys.org/news/2014-05-math-student-oauth-openid-vulnerability.html |archive-date=6 November 2015 |access-date=11 November 2014 |publisher=Phys.org}}</ref><ref name="Covert_Redirect">{{Cite web |date=1 May 2014 |title=Covert Redirect |url=http://tetraph.com/covert_redirect/ |url-status=live |archive-url=https://web.archive.org/web/20160310005903/http://tetraph.com/covert_redirect/ |archive-date=10 March 2016 |access-date=10 November 2014 |publisher=Tetraph}}</ref>
OAuth 2.0 has been analyzed using formal web protocol analysis. This analysis revealed that in setups with multiple authorization servers, one of which is behaving maliciously, clients can become confused about the authorization server to use and may forward secrets to the malicious authorization server (AS Mix-Up Attack).<ref name="ACM">{{Cite book |last1=Fett |first1=Daniel |last2=Küsters |first2=Ralf |last3=Schmitz |first3=Guido |title=Proceedings of the 2016 ACM SIGSAC Conference on Computer and Communications Security |chapter=A Comprehensive Formal Security Analysis of OAuth 2.0 |date=2016 |location=New York, New York, USA |publisher=ACM Press |pages=1204–1215 |arxiv=1601.01229 |bibcode=2016arXiv160101229F |doi=10.1145/2976749.2978385 |isbn=9781450341394|s2cid=1723789 }}</ref> This prompted the creation of a new [[best current practice]] internet draft that sets out to define a new security standard for OAuth 2.0.<ref>{{Cite journal |last1=Bradley |first1=John |last2=Labunets |first2=Andrey |last3=Lodderstedt |first3=Torsten |last4=Fett |first4=Daniel |title=OAuth 2.0 Security Best Current Practice |url=https://tools.ietf.org/html/draft-ietf-oauth-security-topics-13.html |url-status=live |archive-url=https://web.archive.org/web/20200117063230/https://tools.ietf.org/html/draft-ietf-oauth-security-topics-13.html |archive-date=17 January 2020 |access-date=29 July 2019 |website=[[Internet Engineering Task Force]] |date=8 July 2019 |language=en}}</ref> Assuming a fix against the AS Mix-Up Attack in place, the security of OAuth 2.0 has been proven under strong attacker models using formal analysis.<ref name="ACM" />
One implementation of OAuth 2.0 with numerous security flaws has been exposed.<ref>{{Cite web |date=12 February 2013 |title=Hacking Facebook with OAuth 2.0 and Chrome |url=http://homakov.blogspot.co.uk/2013/02/hacking-facebook-with-oauth2-and-chrome.html |url-status=live |archive-url=https://web.archive.org/web/20160423083324/http://homakov.blogspot.co.uk/2013/02/hacking-facebook-with-oauth2-and-chrome.html |archive-date=23 April 2016 |access-date=6 March 2013}}</ref>
In April and May 2017, about one million users of [[Gmail]] (less than 0.1% of users as of May 2017) were targeted by an OAuth-based phishing attack, receiving an email purporting to be from a colleague, employer or friend wanting to share a document on Google Docs.<ref name="bbc1">{{Cite web |date=8 May 2017 |title=Google Docs phishing email 'cost Minnesota $90,000' |url=https://www.bbc.co.uk/news/technology-39845545 |url-status=live |archive-url=https://web.archive.org/web/20200630000812/https://www.bbc.com/news/technology-39845545 |archive-date=30 June 2020 |access-date=29 June 2020 |work=[[BBC News]]}}</ref> Those who clicked on the link within the email were directed to sign in and allow a potentially malicious third-party program called "Google Apps" to access their "email account, contacts and online documents".<ref name="bbc1" /> Within "approximately one hour",<ref name="bbc1" /> the phishing attack was stopped by Google, who advised those who had given "Google Apps" access to their email to revoke such access and change their passwords.
In the draft of OAuth 2.1 the use of the PKCE extension for native apps has been recommended to all kinds of&nbsp;OAuth clients, including web applications and other confidential&nbsp;clients in order to prevent malicious browser extensions from performing OAuth 2.0 code injection attacks.<ref name=":0" />
== Types ==
OAuth framework specifies several grant types for different use cases. Some of the most common OAuth grant types are:<ref>{{Cite web|title=Oauth Grant Types|url=https://oauth.net/2/grant-types/|access-date= 6 December 2023|work=Oauth.net}}</ref>
* Authorization Code
* PKCE
* Client Credentials
* Device Code
* Refresh Token
== Uses ==
[[Facebook]]'s [[Facebook Platform#Graph API|Graph API]] only supports OAuth 2.0.<ref>{{Cite web|title=Authentication - Facebook Developers|url=https://developers.facebook.com/docs/authentication/|url-status=live|archive-url=https://web.archive.org/web/20140123045312/https://developers.facebook.com/docs/authentication/|archive-date=23 January 2014|access-date=5 January 2020|website=Facebook for Developers}}</ref> [[Google]] supports OAuth 2.0 as the recommended authorization mechanism for all of its [[Application Programming Interface|API]]s.<ref>{{Cite web|title=Using OAuth 2.0 to Access Google APIs &#124; Google Identity Platform|url=https://developers.google.com/identity/protocols/OAuth2|url-status=live|archive-url=https://web.archive.org/web/20200104215722/https://developers.google.com/identity/protocols/OAuth2|archive-date=4 January 2020|access-date=4 January 2020|website=Google Developers}}</ref> [[Microsoft]] also supports OAuth 2.0 for various APIs and its Azure Active Directory service,<ref>{{Cite web|title=v2.0 Protocols - OAuth 2.0 Authorization Code Flow|url=https://docs.microsoft.com/en-us/azure/active-directory/active-directory-v2-protocols-oauth-code|url-status=live|archive-url=https://web.archive.org/web/20200629235721/https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow|archive-date=29 June 2020|access-date=29 June 2020|website=Microsoft Docs}}</ref> which is used to secure many Microsoft and third party APIs.
OAuth can be used as an authorizing mechanism to access secured [[RSS]]/[[Atom (standard)|Atom]] feeds. Access to RSS/ATOM feeds that require authentication has always been an issue. For example, an RSS feed from a secured [[Google Sites|Google Site]] could not have been accessed using [[Google Reader]]. Instead, three-legged OAuth would have been used to authorize that RSS client to access the feed from the Google Site.
== OAuth and other standards ==
OAuth is a service that is complementary to and distinct from [[OpenID]]. OAuth is unrelated to [[Initiative For Open Authentication|OATH]], which is a reference architecture for authentication, not a standard for authorization. However, OAuth is directly related to [[OpenID Connect]] (OIDC), since OIDC is an authentication layer built on top of OAuth 2.0. OAuth is also unrelated to [[XACML]], which is an authorization policy standard. OAuth can be used in conjunction with XACML, where OAuth is used for ownership consent and access delegation whereas XACML is used to define the authorization policies (e.g., managers can view documents in their region).
=== OpenID vis-à-vis pseudo-authentication using OAuth ===
OAuth is an ''authorization'' protocol, rather than an ''authentication'' protocol. Using OAuth on its own as an authentication method may be referred to as pseudo-authentication.<ref>{{cite web |title=An Introduction to OAuth2 Authentication |url=https://www.linode.com/docs/guides/oauth2-authentication-an-introduction/ |website=Linode.com |date=22 October 2021 |access-date=18 April 2024}}</ref> The following diagrams highlight the differences between using OpenID (specifically designed as an authentication protocol) and OAuth for authorization.
The communication flow in both processes is similar:
# (Not pictured) The user requests a resource or site login from the application.
# The site sees that the user is not authenticated. It formulates a request for the identity provider, encodes it, and sends it to the user as part of a redirect URL.
# The user's browser makes a request to the redirect URL for the identity provider, including the application's request
# If necessary, the identity provider authenticates the user (perhaps by asking them for their username and password)
# Once the identity provider is satisfied that the user is sufficiently authenticated, it processes the application's request, formulates a response, and sends that back to the user along with a redirect URL back to the application.
# The user's browser requests the redirect URL that goes back to the application, including the identity provider's response
# The application decodes the identity provider's response, and carries on accordingly.
# (OAuth only) The response includes an access token which the application can use to gain direct access to the identity provider's services on the user's behalf.
The crucial difference is that in the OpenID ''authentication'' use case, the response from the identity provider is an assertion of identity; while in the OAuth ''authorization'' use case, the identity provider is also an [[Application Programming Interface|API]] provider, and the response from the identity provider is an access token that may grant the application ongoing access to some of the identity provider's APIs, on the user's behalf. The access token acts as a kind of "valet key" that the application can include with its requests to the identity provider, which prove that it has permission from the user to access those APIs.
Because the identity provider typically (but not always) authenticates the user as part of the process of granting an OAuth access token, it is tempting to view a successful OAuth access token request as an authentication method itself. However, because OAuth was not designed with this use case in mind, making this assumption can lead to major security flaws.<ref>{{Cite web |title=End User Authentication with OAuth 2.0 |url=http://oauth.net/articles/authentication/ |url-status=live |archive-url=https://web.archive.org/web/20151119133521/http://oauth.net/articles/authentication/ |archive-date=19 November 2015 |access-date=8 March 2016 |website=oauth.net}}</ref>
[[File:OpenIDvs.Pseudo-AuthenticationusingOAuth.svg|OpenID vs. pseudo-authentication using OAuth]]
=== OAuth and XACML ===
[[XACML]] is a policy-based, [[attribute-based access control]] authorization framework. It provides:
* An [[XACML#Architecture|access control architecture]].
* A policy language with which to express a wide range of access control policies including policies that can use consents handled / defined via OAuth.
* A request / response scheme to send and receive authorization requests.
XACML and OAuth can be combined to deliver a more comprehensive approach to authorization. OAuth does not provide a policy language with which to define access control policies. XACML can be used for its policy language.
Where OAuth focuses on delegated access (I, the user, grant Twitter access to my Facebook wall), and identity-centric authorization, XACML takes an attribute-based approach which can consider attributes of the user, the action, the resource, and the context (who, what, where, when, how). With XACML it is possible to define policies such as
* Managers can view documents in their department
* Managers can edit documents they own in draft mode
XACML provides more fine-grained access control than OAuth does. OAuth is limited in granularity to the coarse functionality (the scopes) exposed by the target service. As a result, it often makes sense to combine OAuth and XACML together where OAuth will provide the delegated access use case and consent management and XACML will provide the authorization policies that work on the applications, processes, and data.
Lastly, XACML can work transparently across multiple stacks ([[Application Programming Interface|APIs]], web SSO, ESBs, home-grown apps, databases...). OAuth focuses exclusively on HTTP-based apps.
== Controversy ==
Eran Hammer resigned from his role of lead author for the OAuth 2.0 project, withdrew from the [[IETF Working Group|IETF working group]], and removed his name from the specification in July 2012. Hammer cited a conflict between web and enterprise cultures as his reason for leaving, noting that IETF is a community that is "all about enterprise use cases" and "not capable of simple". "What is now offered is a blueprint for an authorization protocol", he noted, "that is the enterprise way", providing a "whole new frontier to sell consulting services and integration solutions".<ref name="Hueniverse">{{Cite web |last=Hammer |first=Eran |date=28 July 2012 |title=OAuth 2.0 and the Road to Hell |url=https://hueniverse.com/oauth-2-0-and-the-road-to-hell-8eec45921529 |url-status=dead |archive-url=https://web.archive.org/web/20130325140509/http://hueniverse.com/2012/07/oauth-2-0-and-the-road-to-hell/ |archive-date=25 March 2013 |access-date=17 January 2018 |website=Hueniverse}}</ref> In comparing OAuth 2.0 with OAuth 1.0, Hammer points out that it has become "more complex, less interoperable, less useful, more incomplete, and most importantly, less secure". He explains how architectural changes for 2.0 unbound tokens from clients, removed all signatures and cryptography at a protocol level and added expiring tokens (because tokens could not be revoked) while complicating the processing of authorization. Numerous items were left unspecified or unlimited in the specification because "as has been the nature of this working group, no issue is too small to get stuck on or leave open for each implementation to decide."<ref name="Hueniverse" />
[[David Recordon]] later also removed his name from the specifications for unspecified reasons.{{cn|date=April 2022}} [[Dick Hardt]] took over the editor role, and the framework was published in October 2012.<ref name="RFC6749" />
David Harris, author of the email client [[Pegasus Mail]], has criticised OAuth 2.0 as "an absolute dog's breakfast", requiring developers to write custom modules specific to each service (Gmail, Microsoft Mail services, etc.), and to register specifically with them.<ref>{{cite web |url=https://www.pmail.com/devnews_archive.htm |title=Pegasus Mail and Mercury Developer News Archives |website=Pegasus Mail|date=October 2021|last=Harris|first=David}}</ref>
== See also ==
* [[List of OAuth providers]]
* [[Data portability]]
* [[IndieAuth]]
* [[Mozilla Persona]]
* [[Security Assertion Markup Language]]
* [[User-Managed Access]]
== References ==
{{reflist|colwidth=30em}}
==External links==
* {{cite web|url=https://datatracker.ietf.org/doc/html/rfc6749|publisher=[[Internet Engineering Task Force]]|title=The OAuth 2.0 Authorization Framework|date=October 2012 |last1=Hardt |first1=Dick }}
{{Authentication APIs}}
[[Category:Cloud standards]]
[[Category:Internet protocols]]
[[Category:Internet properties established in 2007]]
[[Category:Computer access control]]
[[Category:Computer access control protocols]]