AWS + ECP?

[Cantor, Scott]

> I'm not sure how it would even work because the script specifies the HTTP-
> POST binding.. and the AWS metadata doesn't have a POAS (ECP) binding /
> endpoint.  If we try it using the POST binding, the IDP complains
> (unsurprisingly?):

The client/IdP half is SOAP. It's not the POST binding, it's the POST HTTP method.

I think it's complaining because of some weird issue involving the MIME type in Content-Type not being set to text/xml

I literally just rediscovered that myself, working on getting V3 going here. I think that must be Jetty doing something odd, but I mean to try and figure it out. Meantime, it is technically correct to use that content type anyway.

> /Should/ this work?  Seems like it shouldn't... IdP ECP endpoint + SP HTTP-
> POST endpoint?

No, the SP has to have ECP support, which means PAOS, but that isn't why you're getting that error.

-- Scott