<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 11/11/16 9:33 AM, Roehrl Patrick
      wrote:<br>
    </div>
    <blockquote
cite="mid:DA939594733786428DEDECC8E852AA30B0BF6D31@SWELO05MXS.welo.corp00.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:"\@SimSun";
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;
        color:black;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:#0563C1;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:#954F72;
        text-decoration:underline;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Vorformatiert Zchn";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";
        color:black;}
span.HTMLVorformatiertZchn
        {mso-style-name:"HTML Vorformatiert Zchn";
        mso-style-priority:99;
        mso-style-link:"HTML Vorformatiert";
        font-family:Consolas;
        color:black;}
span.E-MailFormatvorlage19
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
--></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]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Yeah
            the XML contains also the signature information
            (SignatureValue, SignedInfo, KeyInfo) and that makes it so
            big. And the request contains also the signature as
            parameter…so seems like a signature too much.</span></p>
      </div>
    </blockquote>
    <br>
    Ok, that confirms that the SP is broken.  An XML signature on the
    protocol message is not allowed, per the Redirect DEFLATE binding. 
    A signature on an embedded child object (which is very unlikely with
    an AuthnRequest) isn't technically disallowed, but in practice means
    you can't use such a message with the Redirect binding. See SAML 2
    Bindings spec, section 3.4.4.1:<br>
    <br>
    "Any signature on the SAML protocol message, including the
    <ds:Signature> XML element itself,<br>
    MUST be removed. Note that if the content of the message includes
    another signature, such as a<br>
    signed SAML assertion, this embedded signature is not removed.
    However, the length of such a<br>
    message after encoding essentially precludes using this mechanism.
    Thus SAML protocol<br>
    messages that contain signed content SHOULD NOT be encoded using
    this mechanism."<br>
    <br>
    <br>
    <br>
    <blockquote type="cite">
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">So
          our SP uses the wrong binding for Redirect.</span></p>
    </blockquote>
    <br>
    It's more correct to say that their implementation of the Redirect
    DEFLATE binding is broken.  It should not emit a protocol message
    with the XML signature, period.<br>
    <br>
    <blockquote type="cite">
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">POST
          Binding
        </span><span
          style="font-size:11.0pt;font-family:Wingdings;color:#1F497D">à</span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">
          embedded signature in XML<o:p></o:p></span></p>
      <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Redirect
          Binding
        </span><span
          style="font-size:11.0pt;font-family:Wingdings;color:#1F497D">à</span><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">
          signature as request parameter<o:p></o:p></span></p>
      <span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">This
        would be correct?</span></blockquote>
    <br>
    Yes, that's essentially correct. <br>
    <br>
  </body>
</html>