<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 2/4/16 4:21 PM, Liam Hoekenga wrote:<br>
</div>
<blockquote
cite="mid:CAH4ZtKSuLe_KnRGr-3RQ1eq8HauNkG7WZt8_+as98eiYm-VQTg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Feb 4, 2016 at 4:05 PM, Brent
Putman <span dir="ltr"><<a moz-do-not-send="true"
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">Hmmm,
ok. But does it also show the actual request body, or can
you get curl to do that? That's really what we want to
know. The IdP is saying that the request body isn't valid
XML.</blockquote>
<div><br>
</div>
<div><S:Envelope xmlns:S="<a moz-do-not-send="true"
href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</a>"
xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"></div>
<div> <S:Body></div>
<div> <samlp:AuthnRequest
xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
AssertionConsumerServiceURL="<a moz-do-not-send="true"
href="https://signin.aws.amazon.com/saml">https://signin.aws.amazon.com/saml</a>"
ID="_6946A4FA43404B198E4BC2AE432EC6B6"
IssueInstant="2016-02-04T21:16:56"
ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
Version="2.0"></div>
<div> <saml:Issuer
xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">urn:amazon:webservices</saml:Issuer></div>
<div> <samlp:NameIDPolicy AllowCreate="1"/></div>
<div> <samlp:Scoping></div>
<div> <samlp:IDPList></div>
<div> <samlp:IDPEntry ProviderID="<a
moz-do-not-send="true"
href="https://shib-idp-test.www.umich.edu/idp/shibboleth"><a class="moz-txt-link-freetext" href="https://shib-idp-test.www.umich.edu/idp/shibboleth">https://shib-idp-test.www.umich.edu/idp/shibboleth</a></a>"/></div>
<div> </samlp:IDPList></div>
<div> </samlp:Scoping></div>
<div> </samlp:AuthnRequest></div>
<div> </S:Body></div>
<div></S:Envelope> </div>
</div>
</div>
<div class="gmail_extra"><br>
</div>
</div>
</blockquote>
<br>
<br>
<br>
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>
<br>
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>
<br>
In any case, if the IdP says it's not valid XML in the body, then I
believe it.<br>
<br>
<br>
</body>
</html>