<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0cm;
        margin-right:0cm;
        margin-bottom:0cm;
        margin-left:36.0pt;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
.MsoChpDefault
        {mso-style-type:export-only;}
@page Section1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-ZA link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>Has anyone thought about how SAML [Security Assertion Markup
Language] would work in terms of SASL <<a
href="http://en.wikipedia.org/wiki/Saml">http://en.wikipedia.org/wiki/Saml</a>>
and XMPP? This is especially interesting regarding the whole OpenID/SSO
discussion a while back; SAML isn’t bound to HTTP or any other client for
that matter (don’t get the wrong idea from the abundance of HTTP
documentation – it will work in any transport).<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I have been reading a bit about SAML and it looks like they
do B64 the SAML XML, with no explanation. It seems a bit strange to B64 an XML
fragment in a SOAP document (or an XMPP stream for that matter) – maybe it
has to do with the WS-Security schema.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>As far as XMPP 1.0 goes we probably would have to B64 the
fragment; but here are my initial thoughts on XMPP 2.0:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Possibly:<br>
<mechanism type="http://www.w3.org/XML/1998/namespace">SAML</mechanism><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Which gives raise to:<o:p></o:p></p>
<p class=MsoNormal><mechanism type="urn:xmpp:tmp:text-plain">PATHETIC</mechanism><!--
something like [name];[password] --><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>And implicitly:<o:p></o:p></p>
<p class=MsoNormal><mechanism type="urn:xmpp:tmp:base64">DIGEST-MD5</mechanism><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Indeed, we could go as far as to turn it into a feature on
its own. It does support SASL-like mechanism selection itself; it should be
possible to jippo SASL right in there:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><stream:features><o:p></o:p></p>
<p class=MsoNormal> <mechanisms
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><o:p></o:p></p>
<p class=MsoNormal>
<mechanism>DIGEST-MD5</mechanism><o:p></o:p></p>
<p class=MsoNormal>
<mechanism>PLAIN</mechanism><o:p></o:p></p>
<p class=MsoNormal>
<mechanism>EXTERNAL</mechanism><o:p></o:p></p>
<p class=MsoNormal> </mechanisms><o:p></o:p></p>
<p class=MsoNormal> <saml xmlns='http://the/saml/namespace'/><o:p></o:p></p>
<p class=MsoNormal></stream:features><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>-- Jonathan<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>