moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-21 08:45:04 -05:00
Code Issues Releases Wiki Activity

0.4

Browse Source
This commit is contained in:
stpeter 2011-08-26 14:22:52 -06:00
parent b899fce3c3
commit 63a5976565
1 changed files with 23 additions and 44 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

67
xep-0233.xml
View File

@ -7,7 +7,7 @@
<xep> <xep>
<header> <header>
<title>Domain-Based Service Names in XMPP SASL Negotiation</title> <title>Domain-Based Service Names in XMPP SASL Negotiation</title>
<abstract>This specification defines a method by which a connection manager associated with an XMPP server can inform a connecting client about its domain-based service name.</abstract> <abstract>This specification defines a method by a connecting client can learn the domain-based service name of a Kerberos acceptor principal for SASL authentication using the GSSAPI mechanism.</abstract>
&LEGALNOTICE; &LEGALNOTICE;
<number>0233</number> <number>0233</number>
<status>Experimental</status> <status>Experimental</status>
@ -25,6 +25,12 @@
&linuxwolf; &linuxwolf;
&stpeter; &stpeter;
&hildjj; &hildjj;
<revision>
<version>0.4</version>
<date>2011-08-26</date>
<initials>psa</initials>
<remark><p>Focused the document purely on the Kerberos use case, with the intent of handling the non-Kerberos use case in a separate specification; incremented the protocol version number to prevent confusion with deployed uses of the non-Kerberos functionality.</p></remark>
</revision>
<revision> <revision>
<version>0.3</version> <version>0.3</version>
<date>2011-06-22</date> <date>2011-06-22</date>
@ -58,49 +64,30 @@
</header> </header>
<section1 topic='Introduction' anchor='intro'> <section1 topic='Introduction' anchor='intro'>
<p>In certain kinds of XMPP deployments, multiple connection managers associated with the XMPP server can be used to handle requests from connecting clients. In such an architecture, the connection manager might need to communicate the hostname to which the client has connected, or information about alternative connection managers.</p> <p>In environments that make use of Kerberos V5 (&rfc4120;) and negotiation of Simple Authentication and Security Layer or SASL (&rfc4422;) over XMPP, a connecting client often needs to know the identity of the Kerberos acceptor principal so that it can obtain a proper ticket for authentication. This scenario was not addressed in &rfc3920; or &rfc6120;. However, the problem can be solved using the concept of domain-based service names (&rfc5178;). In particular, when an XMPP server uses the Kerberos V5 ("GSSAPI") SASL mechanism (&rfc4752;), it can communicate the identity of the acceptor principal as a Kerberos V5 service principal name (&rfc5179;). This document defines an XMPP method for such communication.</p>
<p>This is especially true in environments that make use of Kerberos V5 (&rfc4120;) and negotiation of Simple Authentication and Security Layer or SASL (&rfc4422;) over XMPP, because the client might need additional information about the Kerberos principal so that it can obtain a proper ticket for authentication.</p>
<p>This scenario was not addressed in &rfc3920; or &rfc6120;. However, the problem can be solved using the concept of domain-based service names as described in &rfc5178;. In particular, because XMPP servers typically use the Kerberos V5 ("GSSAPI") SASL mechanism as described in &rfc4752;, they can communicate domain-based names as Kerberos V5 service principal names as described in &rfc5179;.</p>
<p>Therefore this document defines a method for communication of authentication hostnames (especially Kerberos V5 domain-based service names) in the context of SASL negotiation by XMPP entities.</p>
</section1> </section1>
<section1 topic='Use with Kerberos' anchor='kerberos'> <section1 topic='Protocol' anchor='proto'>
<p>When a connection manager associated with an XMPP server needs to communicate additional information about its service principal name to a connecting client, it can do so by including a child element of the &lt;mechanisms/&gt; element during SASL negotation, as allowed by <cite>RFC 6120</cite> (see Section 6.3.5 and the schema for the 'urn:ietf:params:xml:ns:xmpp-sasl' namespace in Appendix A.4). In the case of the Kerberos V5 SASL mechanism, the child element is a &lt;hostname/&gt; element qualified by the 'urn:xmpp:domain-based-name:0' namespace &NSNOTE;. In the context of Kerberos, the &lt;hostname/&gt; element MUST include a 'mechanism' attribute, where the value MUST be "GSSAPI". The XML character data of the &lt;hostname/&gt; element shall specify the fully-qualified name of the connection manager (known as the hostname). The client then generates a domain-based service name from the provided hostname, following the format specified in <cite>RFC 5179</cite> (i.e., "protocol/hostname/domainname@REALM") and setting the values as follows:</p> <p>The acceptor principal's hostname is communicated by including a child element of the &lt;mechanisms/&gt; element during SASL negotation, as allowed by <cite>RFC 6120</cite> (see Section 6.3.5 and the schema for the 'urn:ietf:params:xml:ns:xmpp-sasl' namespace in Appendix A.4). In the case of the Kerberos V5 SASL mechanism, the child element is a &lt;hostname/&gt; element qualified by the 'urn:xmpp:domain-based-name:1' namespace &NSNOTE;. The XML character data of the &lt;hostname/&gt; element specifies the fully-qualified name of the acceptor principal. The client then generates a domain-based service name from the provided hostname, following the format specified in <cite>RFC 5179</cite> (i.e., "protocol/hostname/domainname@REALM") and setting the values as follows:</p>
<ul> <ul>
<li>The <strong>protocol</strong> string MUST be "xmpp"</li> <li>The <strong>protocol</strong> string MUST be "xmpp".</li>
<li>The <strong>hostname</strong> string MUST be the XML character data of the &lt;hostname/&gt; element</li> <li>The <strong>hostname</strong> string MUST be the XML character data of the &lt;hostname/&gt; element.</li>
<li>The <strong>domainname</strong> string MUST be the canonical name of the service</li> <li>The <strong>domainname</strong> string MUST be the canonical name of the service, such as typically communicated in the 'to' address of the initial stream header.</li>
<li>The <strong>REALM</strong> string SHOULD be determined according to the network policies in effect (usually the domain name, in an uppercase mapping)</li> <li>The <strong>REALM</strong> string SHOULD be determined according to the network policies in effect (usually the domain name, in an uppercase mapping).</li>
</ul> </ul>
<p>Consider the example of an XMPP service whose canonical name is "example.com". A user might in fact connect to the physical machine "cm7.us.example.com". The hostname would be communicated as follows.</p> <p>Consider the example of an XMPP service whose canonical name is "example.com". A user might make use of an acceptor principal located at "auth42.us.example.com". The hostname would be communicated as follows.</p>
<example caption="Communicating the hostname"><![CDATA[ <example caption="Communicating the hostname"><![CDATA[
<mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'> <mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
<mechanism>GSSAPI</mechanism> <mechanism>GSSAPI</mechanism>
<mechanism>DIGEST-MD5</mechanism> <mechanism>DIGEST-MD5</mechanism>
<required/> <hostname xmlns='urn:xmpp:domain-based-name:1'>auth42.us.example.com</hostname>
<hostname xmlns='urn:xmpp:domain-based-name:0'
mechanism='GSSAPI'>cm7.us.example.com</hostname>
</mechanisms>
]]></example>
<p>The client would then attempt to obtain a ticket for the domain-based principal "xmpp/cm7.us.example.com/example.com@EXAMPLE.COM".</p>
</section1>
<section1 topic='Non-Kerberos Use Cases' anchor='other'>
<p>This protocol can also be used to communicate connection manager hostnames outside the context of Kerberos. In this case, the &lt;hostname/&gt; element MUST NOT include the 'mechanism' attribute, and multiple instances of the &lt;hostname/&gt; element MAY be included. An example follows.</p>
<example caption="Communicating hostnames"><![CDATA[
<mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
<mechanism>GSSAPI</mechanism>
<mechanism>DIGEST-MD5</mechanism>
<required/>
<hostname xmlns='urn:xmpp:domain-based-name:0'>cm3.us.example.com</hostname>
<hostname xmlns='urn:xmpp:domain-based-name:0'>cm5.us.example.com</hostname>
<hostname xmlns='urn:xmpp:domain-based-name:0'>cm9.us.example.com</hostname>
</mechanisms> </mechanisms>
]]></example> ]]></example>
<p>The client would then attempt to obtain a ticket for the domain-based principal "xmpp/auth42.us.example.com/example.com@EXAMPLE.COM".</p>
</section1> </section1>
<section1 topic='Security Considerations' anchor='security'> <section1 topic='Security Considerations' anchor='security'>
<p>The communication of hostnames during SASL negotiation is not known to introduce new security vulnerabilities, as long as it is done after the underlying channel has been secured using Transport Layer Security (TLS; &rfc5246;) as described for XMPP in <cite>RFC 6120</cite>. For additional security considerations, refer to <cite>RFC5178</cite> and <cite>RFC 5179</cite>.</p> <p>The communication of acceptor principal hostname during SASL negotiation is not known to introduce new security vulnerabilities, as long as it is done after the underlying channel has been secured using Transport Layer Security (TLS; &rfc5246;) as described for XMPP in <cite>RFC 6120</cite>. For additional security considerations, refer to <cite>RFC5178</cite> and <cite>RFC 5179</cite>.</p>
</section1> </section1>
<section1 topic='IANA Considerations' anchor='iana'> <section1 topic='IANA Considerations' anchor='iana'>
@ -111,7 +98,7 @@
<section2 topic='Protocol Namespaces' anchor='registrar-ns'> <section2 topic='Protocol Namespaces' anchor='registrar-ns'>
<p>This specification defines the following XML namespace:</p> <p>This specification defines the following XML namespace:</p>
<ul> <ul>
<li>urn:xmpp:domain-based-name:0:0</li> <li>urn:xmpp:domain-based-name:1</li>
</ul> </ul>
<p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p> <p>Upon advancement of this specification from a status of Experimental to a status of Draft, the &REGISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.</p>
</section2> </section2>
@ -126,26 +113,18 @@
<xs:schema <xs:schema
xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:xs='http://www.w3.org/2001/XMLSchema'
targetNamespace='urn:xmpp:domain-based-name:0' targetNamespace='urn:xmpp:domain-based-name:1'
xmlns='urn:xmpp:domain-based-name:0' xmlns='urn:xmpp:domain-based-name:1'
elementFormDefault='qualified'> elementFormDefault='qualified'>
<xs:element name='hostname'> <xs:element name='hostname' type='xs:string'/>
<xs:complexType>
<xs:simpleContent>
<xs:extension base='xs:string'>
<xs:attribute name='mechanism' type='xs:NMTOKEN' use='optional'/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:schema> </xs:schema>
]]></code> ]]></code>
</section1> </section1>
<section1 topic='Acknowledgements' anchor='ack'> <section1 topic='Acknowledgements' anchor='ack'>
<p>Thanks to Owen Friel, Shane Hannon, Seamus Kerrigan, and Alexey Melnikov for their comments.</p> <p>Thanks to Owen Friel, Shane Hannon, Seamus Kerrigan, Eliot Lear, Alexey Melnikov, and Klaas Wierenga for their comments.</p>
</section1> </section1>
</xep> </xep>