AWS + ECP?

[Cantor, Scott]

> I hate flying blind, so I grabbed that aws.plugin.bash script, ripped out what
> wasn't relevant to just making the ECP request, and ran it against my v3 IdP.
> With no explicit content type header, it sends application/x-www-form-
> urlencoded, and that results in the XML parsing error.

That particular behavior is basically what curl does, so that's probaby what's inside it.

I was wondering why that breaks it in that particular way, but your other note answers that. SWF definitely calls getParameter when flows are activated, to determine whether to resume a flow or start a new one. The error is rather odd looking.

Formally speaking, ECP is SOAP and requires that content type. Practically speaking, the decoding class doesn't check, and sending anything that doesn't get in the way will work (I tested with foo/bar, worked fine). I believe the SP is pretty strict about that stuff, just because I don't like having C/C++ code operating on unknown data if I can avoid it.

-- Scott