XMPP as specified in &rfc3920; and updated in &rfc6120; allows the use of any SASL (&rfc4422;) mechanism in the authentication of XMPP entities. This document specifies a recommended protocol flow for use of the SASL EXTERNAL mechanism with PKIX (&rfc5280;) certificates This specification focuses on the use of the SASL EXTERNAL mechanism with X.509 certificates. Future specifications may document best practices for use of SASL EXTERNAL outside the context of the X.509 infrastructure, for example via Internet Protocol Security (IPSec) as specified in &rfc4301;., expecially when an XMPP service indicates that TLS is mandatory-to-negotiate. The protocol flows when TLS is not required are more complicated (e.g., alternate flows involving server dialback) and may be described in a future version of this document.

As specified in RFC 3920 and updated in RFC 6120, during the stream negotiation process an XMPP client can present a certificate (a "client certificate"). If a JabberID is included in a client certificate, it is encapsulated as an id-on-xmppAddr Object Identifier ("xmppAddr"), i.e., a subjectAltName entry of type otherName with an ASN.1 Object Identifier of "id-on-xmppAddr" as specified in Section 13.7.1.4 of RFC 6120.

There are three possible cases:

1. The certificate includes one xmppAddr.
2. The certificate includes more than one xmppAddr.
3. The certificate includes no xmppAddr.

This specification includes recommendations that address all three cases.

The RECOMMENDED protocol flow for client-to-server use of SASL EXTERNAL with client certificates is as follows:

1. Client initiates stream to server.

   ]]>

2. Server replies with stream header.

   ]]>

3. Server advertises TLS stream feature, which might indicate that TLS is mandatory-to-negotiate.

   ]]>

4. Client sends STARTTLS command to server.

   ]]>

5. Server informs client to proceed.

   ]]>

6. Server requests, and client presents, the client certificate during TLS negotiation.

7. Server and client successfully complete the TLS negotiation and client initiates a new initial stream header to server over the encrypted TCP connection.

   ]]>

8. Server replies with response stream header.

   ]]>

9. Server advertises SASL mechanisms. Because the client presented a client certificate, here the server offers the SASL EXTERNAL mechanism (see Section 6.3.4 of RFC 6120 for recommendations regarding the conditions under which to offer the SASL EXTERNAL mechanism).

   EXTERNAL DIGEST-MD5 ANONYMOUS ]]>

10. Client considers EXTERNAL to be its preferred SASL mechanism so it attempts to complete SASL negotiation using that mechanism. The following paragraphs illustrate several possible paths, depending on whether the client includes an authorization identity (for the official rules regarding when to include the authorization identity, see Section 6.3.8 of RFC 6120).

    1. If the client certificate contains only one JID, then the client MAY include an authorization identity, but only if it desires to be authorized as a JID other than the address in the client certificate; else it MUST NOT include include an authorization identity (this is shown in the following example by setting the XML character data of the <auth/> element to "=").

       = ]]>

    2. If the client certificate contains more than one JID, then the client MUST include an authorization identity so that the server can determine which JID to use (this is shown in the following example by setting the XML character data of the <auth/> element to "anVsaWV0QGV4YW1wbGUuY29t", which is the base 64 encoding for "juliet@example.com").

       anVsaWV0QGV4YW1wbGUuY29t ]]>

    3. If the client certificate does not contain a JID, then the client MAY include an authorization identity, but only if it desires to be authorized as a JID other than the address in the client certificate; else it MUST NOT include include an authorization identity (this is shown in the following example by setting the XML character data of the <auth/> element to "=").

       = ]]>

11. Server determines whether to allow authentication and authorization of user.

    1. If (1) the certificate presented by the client contains only one valid XMPP address that corresponds to a registered account on the server and (2) the client did not pass an authorization identity in the SASL exchange, then the server SHOULD allow authentication and authorization of that JID.

       ]]>

    2. If the certificate contains more than one valid XMPP address that corresponds to a registered account on the server (e.g., because the server offers virtual hosting), then the server SHOULD allow authentication and authorization of the JID specified as the authorization identity in the SASL exchange.

       ]]>

       If no authorization identity is included, then the server SHOULD return a SASL failure case of <invalid-authzid/> and close the stream.

       ]]>

    3. If the certificate does not contain an XMPP address, then the server MAY attempt to determine if there is a registered account associated with the user, for example by performing an LDAP lookup based on the Common Name or other information presented by the client in the certificate; if such a JID mapping is successful and the mapped JID matches the authorization identity provided, then the server SHOULD allow authentication and authorization of that mapped JID.

       ]]>

       If JID mapping is unsuccessful, then the server MUST return a SASL failure condition of <not-authorized/> and close the stream.

       ]]>

       If JID mapping is successful but the mapped JID does not match the authorization identity provided (if any), then the server MUST return a SASL failure condition of <invalid-authzid/> and close the stream.

       ]]>

12. If SASL authentication succeeded, the client opens new stream, then client and server proceed with resource binding as described in RFC 3920 and RFC 6120.

RFC 3920 specified that if a JabberID is included in a certificate intended for use by an XMPP server (a "server certificate"), it shall be encapsulated as an xmppAddr. That recommendation is updated in RFC 6120 through a reference to &rfc6125;, which prefers use of a dNSName and/or SRVName entry in the Subject Alternative Name. The DNS domain name contained in the certificate can be a fully-qualified domain name ("FQDN") or a so-called "wildcard" with the '*' character as the complete left-most label (see RFC 6125 for complete details).

The RECOMMENDED protocol flow for server-to-server use of SASL EXTERNAL with server (domain) certificates is as follows:

1. Server1 initiates stream to server2.

   ]]>

2. Server2 replies with stream header.

   ]]>

3. Server2 advertises TLS stream feature, which might indicate that TLS is mandatory-to-negotiate.

   ]]>

4. Server1 sends STARTTLS command to Server2.

   ]]>

5. Server2 informs Server1 to proceed.

   ]]>

6. Server2 requests, and Server1 presents, Server1's certificate during TLS negotiation.

7. Server2 validates certificate in accordance with the rules from RFC 6120 and RFC 6125.

   1. If certificate is unacceptable for the reasons explained in RFC 6120 and RFC 6125, Server2 closes Server1's TCP connection.

   2. Else Server2 completes successful TLS negotiation and Server1 sends a new initial stream header to Server2 over the encrypted TCP connection.

      ]]>

8. Server2 replies with stream header.

   ]]>

9. Server2 advertises SASL mechanisms. If the 'from' attribute of the stream header sent by Server1 can be matched against one of the identifiers provided in the certificate following the matching rules from RFC 6125, Server2 SHOULD advertise the SASL EXTERNAL mechanism. If no match is found, Server2 closes Server1's TCP connection.

   EXTERNAL ]]>

10. Server1 considers EXTERNAL to be its preferred SASL mechanism. Here it includes a base-64-encoded authorization identity as the XML character data of the <auth/> element, setting it to the same value as the 'from' address on the stream header it sent to Server2.

    Y29uZmVyZW5jZS5leGFtcGxlLm9yZwo= ]]>

    (In this case, the authorization identity is "conference.example.org".)

    Interoperability Note: Previous versions of this specification relied on the authorization identity being present on the receiving server. Even though this is no longer required, the connecting server should include it for backward compability.

11. Server2 determines if hostname is valid.

    1. If the 'from' attribute of stream header sent by Server1 can be matched against one of the identifiers provided in the certificate following the matching rules from RFC 6125, Server2 returns success.

       ]]>

    2. Else server MUST return a ¬authorized; stream error and close the stream.

       ]]>

This document introduces no security considerations or concerns above and beyond those discussed in RFC 6120 and RFC 6125.

This document requires no interaction with &IANA;.

This document requires no interaction with the ®ISTRAR;.

Thanks to Dave Cridland, Philipp Hancke, Joe Hildebrand, Justin Karneges, Chris Newton, Rob Norris, and Matthias Wimmer for their comments.

Peter Millard, co-author of the initial version of this specification, died on April 26, 2006. The remaining author appreciates his assistance in defining the best practices described herein.