datatracker.ietf.org
Sign in
Version 5.6.2.p3, 2014-07-31
Report a bug

Salted Challenge Response (SCRAM) HTTP Authentication Mechanism
draft-melnikov-httpbis-scram-auth-00

Document type: Expired Internet-Draft (candidate for httpauth WG)
Document stream: IETF
Last updated: 2013-04-10 (latest revision 2012-06-11)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

IETF State: Call For Adoption By WG Issued
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:
http://www.ietf.org/archive/id/draft-melnikov-httpbis-scram-auth-00.txt

Abstract

The secure authentication mechanism most widely deployed and used by Internet application protocols is the transmission of clear-text passwords over a channel protected by Transport Layer Security (TLS). There are some significant security concerns with that mechanism, which could be addressed by the use of a challenge response authentication mechanism protected by TLS. Unfortunately, the HTTP Digest challenge response mechanism presently on the standards track failed widespread deployment, and have had success only in limited use. This specification describes a family of HTTP authentication mechanisms called the Salted Challenge Response Authentication Mechanism (SCRAM), which addresses the security concerns and meets the deployability requirements. When used in combination with TLS or an equivalent security layer, a mechanism from this family could improve the status-quo for application protocol authentication.

Authors

Alexey Melnikov <alexey.melnikov@isode.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)