RFC 5849: The OAuth 1.0 Protocol
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6749.
Current version: RFC 6749 — The OAuth 2.0 Authorization Framework
In plain English — editorial summary, not part of the RFC
OAuth provides a method for clients to access server resources on behalf of a resource owner (such as a different client or an end-user). It also provides a process for end-users to authorize third-party access to their server resources without sharing their credentials (typically, a username and password pair), using user-agent redirections. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5849
- Published
- April 2010
- Authors
- E. Hammer-Lahav
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 38
- Also known as
- —
- Obsoleted by:
- RFC 6749
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3779X.509 Extensions for IP Addresses and AS IdentifiersCurrent
June 2004
- RFC 5779Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility Anchor Interaction with Diameter ServerCurrent
February 2010
- RFC 6010Cryptographic Message Syntax (CMS) Content Constraints ExtensionCurrent
September 2010
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 6686Resolution of the Sender Policy Framework (SPF) and Sender ID ExperimentsCurrent
July 2012
- RFC 6819OAuth 2.0 Threat Model and Security ConsiderationsUpdated
January 2013
- RFC 4740Diameter Session Initiation Protocol (SIP) ApplicationCurrent
November 2006
- RFC 7155Diameter Network Access Server ApplicationCurrent
April 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?