Servers MUST advertise availability of the sasl capability to any clients which have If cap-notify is an active capability, the client will be notified about statusĬhanges concerning the availability of sasl authentication. The sasl capability is integrated with the new cap-notify framework, such that 3.2).Ĭlients MUST handle the case when the value contains one or more mechanisms Negotiation protocol that allows values (i.e. In CAP LS even though they are attempting to use a version of the capability The value, if present, MUST be a comma ( ,) separated list of SASLĬlients MUST handle the case when there is no value for the sasl capability Value of the sasl client capability in CAP LS.
Servers SHOULD advertise the available SASL authentication mechanisms in the
Then the client MUST disconnect and MAY retry the connection. If a client requires pre-authentication and is unable to obtain the sasl capability, Servers MUST NAK any sasl capability request if the authentication layer is Servers MUST NOT advertise the sasl capability if the authentication layer is This document describes how SASL authenticationĬapability negotiation protocol updates introduced by CAP Version 302,Īnd adds support for reauthentication if authentication is lost via the cap-notifyĪdvertisement of sasl capability when authentication is unavailable 🔗 Unlimited redistribution and modification of this document is allowed provided that the above copyright notice and this permission notice remains intact.
0 kommentar(er)
