<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 4, 2016 at 4:43 PM, Brent Putman <span dir="ltr"><<a href="mailto:putmanb@georgetown.edu" target="_blank">putmanb@georgetown.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">Is that literally the raw output of the aws.plugin.bash with curl -v
    or whatever?  Just making sure b/c it doesn't look like that script
    indents, pretty-prints, etc.  We need to know the unadulterated raw
    request body<br></div></blockquote><div><br></div><div>My bad.  I like pretty printing.  Here's the un-altered..</div><div><br></div><div><S:Envelope xmlns:S="<a href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</a>" xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"><S:Body><samlp:AuthnRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" AssertionConsumerServiceURL="<a href="https://signin.aws.amazon.com/saml">https://signin.aws.amazon.com/saml</a>" ID="_B62B96DDC6964A70996F92A385759445" IssueInstant="2016-02-04T21:48:00" ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Version="2.0"><saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">urn:amazon:webservices</saml:Issuer><samlp:NameIDPolicy AllowCreate="1"/><samlp:Scoping><samlp:IDPList><samlp:IDPEntry ProviderID="<a href="https://shib-idp-test.www.umich.edu/idp/shibboleth">https://shib-idp-test.www.umich.edu/idp/shibboleth</a>"/></samlp:IDPList></samlp:Scoping></samlp:AuthnRequest></S:Body></S:Envelope><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
    Also confused about the earlier output that was showing the request
    with 'text/xml'.  My testing shows that curl with "-d" sends 
    "Content-Type: application/x-www-form-urlencoded".  Which jibes with
    what we previously thought.  Wondering if there's differences in
    various versions of curl.  Mine is 7.30.0.<br></div></blockquote></div><br>As downloaded, it does use the wrong content type.  I took a hint from John Dennis's message and added </div><div class="gmail_extra">-H "Content-Type: text/xml; charset=utf-8"<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">The unmodified script does use application/x-www-form-urlencoded.  The SOAP request looks the same...</div><div class="gmail_extra"><br></div><div class="gmail_extra"><S:Envelope xmlns:S="<a href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</a>" xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"><S:Body><samlp:AuthnRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" AssertionConsumerServiceURL="<a href="https://signin.aws.amazon.com/saml">https://signin.aws.amazon.com/saml</a>" ID="_7E070E8646BE42AF94FF1B2321F46558" IssueInstant="2016-02-04T21:50:23" ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Version="2.0"><saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">urn:amazon:webservices</saml:Issuer><samlp:NameIDPolicy AllowCreate="1"/><samlp:Scoping><samlp:IDPList><samlp:IDPEntry ProviderID="<a href="https://shib-idp-test.www.umich.edu/idp/shibboleth">https://shib-idp-test.www.umich.edu/idp/shibboleth</a>"/></samlp:IDPList></samlp:Scoping></samlp:AuthnRequest></S:Body></S:Envelope><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">The headers look the same, save the content-type...</div><div class="gmail_extra"><div class="gmail_extra">> POST /idp/profile/SAML2/SOAP/ECP HTTP/1.1</div><div class="gmail_extra">> Host: <a href="http://shib-idp-test.www.umich.edu">shib-idp-test.www.umich.edu</a></div><div class="gmail_extra">> User-Agent: curl/7.46.0</div><div class="gmail_extra">> Accept: */*</div><div class="gmail_extra">> Authorization: Basic *************************</div><div class="gmail_extra">> Content-Length: 735</div><div class="gmail_extra">> Content-Type: application/x-www-form-urlencoded</div><div class="gmail_extra"><br></div></div><div class="gmail_extra">...and both content types result in the IdP throwing a 500 (tho maybe for different reasons?)<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Liam</div></div>