… user controls an identifier. Simple Authentication and Security Layer (SASL) [ RFC4422 ] is used by application protocols such as IMAP [ RFC3501 ], Post Office Protocol (POP) [ RFC1939 ], and Extensible Messaging and Presence Protocol (XMPP) [ RFC6120 ], with the goal of modular…

…mily of mechanisms does not presently include negotiation of a security layer [ RFC4422 ]. It is intended to be used with an external security layer such as that provided by TLS or SSH, with optional channel binding [ RFC5056 ] to the external security layer. SCRAM is specified h…

… for different use cases. The Simple Authentication and Security Layer (SASL) [ RFC4422 ] is a generalized mechanism for identifying and authenticating a user and for optionally negotiating a security layer for subsequent protocol interactions. SASL is used by application protoco…

…of authentication mechanisms. Simple Authentication and Security Layer (SASL) [ RFC4422 ] is a framework to provide authentication and security layers for connection-based protocols, also using a variety of mechanisms. This document describes how to use a GSS-API mechanism as tho…

…le of stringprep [ RFC3454 ]) but can be used by technologies other than SASL [ RFC4422 ], such as HTTP authentication as specified in [ HTTP-BASIC-AUTH ] and [ HTTP-DIGEST-AUTH ]. This document does not modify the handling of internationalized strings in usernames and passwords …

…le user name" construct in the Simple Authentication and Security Layer (SASL) [RFC4422]. Depending on the deployment, a simple user name might take the form of a user's full name (e.g., the user's personal name followed by a space and then the user's family name). Such a simple …

…e user name" construct in the Simple Authentication and Security Layer (SASL) [ RFC4422 ]. Depending on the deployment, a simple user name might take the form of a user's full name (e.g., the user's personal name followed by a space and then the user's family name). Such a simple…

…enable the Simple Authentication and Security Layer (SASL) EXTERNAL mechanism [ RFC4422 ]. An IMAPS server MAY issue a PREAUTH greeting instead of enabling SASL EXTERNAL. 4.3 . Recording TLS Ciphersuite in "Received" Header Field The ESMTPS transmission type [ RFC3848 ] provides …

…mentation Note: XMPP uses the Simple Authentication and Security Layer (SASL) [ RFC4422 ] for authentication. At the time of this writing, some SASL mechanisms use SASLprep [ RFC4013 ] for the handling of usernames and passwords; in the future, these SASL mechanisms will likely t…

… enable the Simple Authentication and Security Layer (SASL) EXTERNAL mechanism [RFC4422]. An IMAPS server MAY issue a PREAUTH greeting instead of enabling SASL EXTERNAL. 4.3. Recording TLS Ciphersuite in "Received" Header Field The ESMTPS transmission type [RFC3848] provides trac…

…enable the Simple Authentication and Security Layer (SASL) EXTERNAL mechanism [ RFC4422 ]. An IMAPS server MAY issue a PREAUTH greeting instead of enabling SASL EXTERNAL. 4.3 . Recording TLS Ciphersuite in "Received" Header Field The ESMTPS transmission type [ RFC3848 ] provides …

…ementation Note: XMPP uses the Simple Authentication and Security Layer (SASL) [RFC4422] for authentication. At the time of this writing, some SASL mechanisms use SASLprep [RFC4013] for the handling of usernames and passwords; in the future, these SASL mechanisms will likely tran…

…mentation Note: XMPP uses the Simple Authentication and Security Layer (SASL) [ RFC4422 ] for authentication. At the time of this writing, some SASL mechanisms use SASLprep [ RFC4013 ] for the handling of usernames and passwords; in the future, these SASL mechanisms will likely t…

…s For clients and servers that support password based authentication using SASL RFC4422 it is RECOMMENDED that the following mechanisms be implemented: SCRAM-SHA-256 RFC7677 SCRAM-SHA-256-PLUS RFC7677 System entities SHOULD NOT invent their own mechanisms that have not been stand…

…mentation Note: XMPP uses the Simple Authentication and Security Layer (SASL) [ RFC4422 ] for authentication. At the time of this writing, some SASL mechanisms use SASLprep [ RFC4013 ] for the handling of usernames and passwords; in the future, these SASL mechanisms will likely t…