AWS + ECP?

[John Dennis]

On 02/04/2016 03:53 PM, Cantor, Scott wrote:
>> Thanks. Maybe Brent has an obvious insight, but I haven't figured out why
>> our decoding logic would be behaving that way in this situation. I don't know
>> if we even look at Content-Type, and if we did, we'd have a clear error. All I
>> see is the code passing the request stream from the servlet into the XML
>> parser. I don't understand how that causes that error on both containers yet.
>> It's very odd.
>
> We probably figured this out months ago, the problem is just the script and use of curl, it defaults the Content Type to form-encoded if you don't set it.
>
> I can speculate your AWS issue might be that, but you'd have to sniff it.

Not sure which script you're using but if it's the ecp.sh script that 
was floating around the shibboleth site somewhere I had to make the 
following fix when we were testing ECP.

# The original code just used -d which sets the Content-Type to
# application/x-www-form-urlencoded but this is not correct, the
# Content-Type for SOAP 1.1 should be text/xml

idp_response=`$CURL --fail -X POST -H 'Content-Type:text/xml' -c 
$cookie_file -b $cookie_file --user $login --digest -d "$idp_request" 
$idp_endpoint`

Note, we hacked the script a bit so it may not exactly match what you've 
got but the major point is to pass the -H 'Content-Type:text/xml' header 
in the curl command when posting the SOAP 1.1 message to the IdP.

-- 
John