Browse Prior Art Database

A Set of Simple Authentication and Security Layer (SASL) Mechanisms for OAuth (RFC7628)

IP.com Disclosure Number: IPCOM000244960D
Original Publication Date: 2015-Aug-01
Included in the Prior Art Database: 2016-Feb-04
Document File: 42 page(s) / 46K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

W. Mills: AUTHOR [+3]

Abstract

message flow of OAuth 2.0 [RFC6749]. As indicated in the figure, this document impacts the exchange of messages (E) and (F) since SASL is used for interaction between the client and the resource server instead of HTTP.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 6% of the total text.

Internet Engineering Task Force (IETF)                          W. Mills Request for Comments: 7628                                     Microsoft Category: Standards Track                                   T. Showalter ISSN: 2070-1721                                                            H. Tschofenig                                                                 ARM Ltd.                                                              August 2015

   A Set of Simple Authentication and Security Layer (SASL) Mechanisms                                for OAuth

Abstract

   OAuth enables a third-party application to obtain limited access to a    protected resource, either on behalf of a resource owner by    orchestrating an approval interaction or by allowing the third-party    application to obtain access on its own behalf.

   This document defines how an application client uses credentials    obtained via OAuth over the Simple Authentication and Security Layer    (SASL) to access a protected resource at a resource server.  Thereby,    it enables schemes defined within the OAuth framework for non-HTTP-    based application protocols.

   Clients typically store the user's long-term credential.  This does,    however, lead to significant security vulnerabilities, for example,    when such a credential leaks.  A significant benefit of OAuth for    usage in those clients is that the password is replaced by a shared    secret with higher entropy, i.e., the token.  Tokens typically    provide limited access rights and can be managed and revoked    separately from the user's long-term password.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7628.

Mills, et al.                Standards Track                    [Page 1]
 RFC 7628                       SASL OAuth                    August 2015

 Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Tru...