RESTful Authentication Pattern for the Hypertext Transport Protocol (HTTP)
draft-ietf-httpauth-rest-auth-01
| Document | Type |
Expired Internet-Draft
(httpauth WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Nicolás Williams | ||
| Last updated | 2014-02-15 (Latest revision 2013-08-14) | ||
| Replaces | draft-httpauth-rest-auth | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document proposes a "RESTful" pattern of authentication for HTTP/1.0, 1.1, and 2.0. The goal is to make it easy to add authentication mechanisms to HTTP applications and to make it easy to implement them even without much help from the HTTP stack (though it is best to integrate authentication into the stack, of course). Another goal is to make it easy to reuse existing authentication mechanisms by allowing the user (that is, the server's operators) to choose what concrete authentication mechanism(s) to use. Among other benefits of RESTauth: it is orthogonal to "HTTP routers" and proxies, it results in session Uniform Resource Identifiers (URIs) that can be DELETEd to logout, naturally supports multi-legged authentication schemes, naturally supports clustering, and can be universally implemented on the server side with such server<->application interfaces as the Common Gateway Interface (CGI) and FastCGI, among others.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)