AWS + ECP?

[Brent Putman]

On 2/4/16 3: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.

Unless we know otherwise, I'd trust that the log is correct and the
request body really isn't valid XML...


>>  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.

Yes, that rings a bell, and sounds correct to me. 

Since we can't even parse the inbound request, there's no way to get the
regular PROTOCOL_MESSAGE output on the IdP side.  But if you can munge
the ECP client script, just adding a "-v" to the curl invocation should
show the actual request on stderr.  And will probably confirm what Scott
said.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160204/8b0e6aeb/attachment-0001.html>