]> Isode Ltd

14 Castle Mews Hampton Middlesex TW12 2NP UK alexey.melnikov@isode.com

This document updates requirements on implementations of various Salted Challenge Response Authentication Mechanism (SCRAM) Simple Authentication and Security Layer (SASL) mechanisms based on more modern security practices.

The intent of this document is to serve as an implementor's roadmap for implementing various Salted Challenge Response Authentication Mechanism (SCRAM) SASL mechanisms. defined the generic SCRAM framework and described instantiation of a SCRAM mechanism using SHA-1 hash function: SCRAM-SHA-1 (and SCRAM-SHA-1-PLUS). described another instantiation using SHA-256 hash function (SCRAM-SHA-256 and SCRAM-SHA-256-PLUS) and also clarified conditions for using the mandatory-to-implement "tls-unique" channel binding with TLS 1.2. defines the "tls-exporter" channel binding that is to be used when a SCRAM mechanism is used over TLS 1.3 or later. and define further instantiations of SCRAM using SHA-512 and SHA3-512 hash functions respectively. defines an extension to SCRAM for two factor authentication. It is applicable to all instantiations of SCRAM with different hash algorightms.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all

document updated and to use the "tls-exporter" channel binding as the mandatory to implement (instead of "tls-unique") when a SCRAM mechanism is used over TLS 1.3 or later. [[Discuss if rough consensus can be reached on this in the KITTEN WG.]] All SCRAM implementations SHOULD support to allow for two factor authentication with SCRAM. [[Possibly narrow down choices to only one of these. Discuss in the KITTEN WG.]] Unless required for backward compatibility, server and client implementations MUST support SCRAM-SHA-512-PLUS/SCRAM-SHA-512 and/or SCRAM-SHA3-512-PLUS/SCRAM-SHA3-512 instead of SCRAM-SHA-1-PLUS/SCRAM-SHA-1 . describes how SCRAM hashes can be stored in LDAP. The LDAP format has a field for the hash algorithm name used, so it is compatible with all versions of SCRAM described in this document, including SCRAM-SHA-256, SCRAM-SHA-512 and SCRAM-SHA3-512.

The security considerations from still apply. To be secure, SCRAM-*-PLUS MUST be used over a TLS channel that has had the session hash extension negotiated, or session resumption MUST NOT have been used. When using SCRAM over TLS 1.2 , the "tls-unique" channel binding is still the default channel binding to use (see Section 6.1 of ), assuming the above conditions are satisfied. When using SCRAM over TLS 1.3 , the "tls-exporter" channel binding is the default (in the sense specified in Section 6.1 of ) to use. See and for reasons to move from SHA-1 to a strong security mechanism like SHA-512. The strength of this mechanism is dependent in part on the hash iteration-count, as denoted by "i" in . As a rule of thumb, the hash iteration-count should be such that a modern machine will take 0.1 seconds to perform the complete algorithm; however, this is unlikely to be practical on mobile devices and other relatively low- performance systems. At the time this was written, the rule of thumb gives around 15,000 iterations required; however, a hash iteration- count of 10000 takes around 0.5 seconds on current mobile handsets. This computational cost can be avoided by caching the ClientKey (assuming the Salt and hash iteration-count is stable). Therefore, the recommendation of this specification is that the hash iteration- count SHOULD be at least 10000, but careful consideration ought to be given to using a significantly higher value, particularly where mobile use is less important.

IANA is requested to add RFC XXXX as an extra reference for the following SASL SCRAM mechanisms listed in the "SASL SCRAM Family Mechanisms" registry: SCRAM-SHA-1, SCRAM-SHA-1-PLUS, SCRAM-SHA-256 and SCRAM-SHA-256-PLUS.

&RFC2119; &RFC4422; &RFC5246; &RFC5802; &RFC5803; &RFC6234; &RFC7627; &RFC7677; &RFC8174; &RFC8446; &RFC9266; Isode Ltd This specification describes an extension to family of Simple Authentication and Security Layer (SASL; RFC 4422) authentication mechanisms called the Salted Challenge Response Authentication Mechanism (SCRAM), which provides support for 2 factor authentication. This specification also gives an example of how TOTP (RFC 6238) can be used as the second factor. This document registers the Simple Authentication and Security Layer (SASL) mechanisms SCRAM-SHA-512 and SCRAM-SHA-512-PLUS. This document registers the Simple Authentication and Security Layer (SASL) mechanisms SCRAM-SHA3-512 and SCRAM-SHA3-512-PLUS. &RFC4270; &RFC5226; &RFC6194;

This document is based on RFC 7677 by Tony Hansen. Thank you to Ludovic Bocquet for comments and corrections.