Content length of the SOAP request is too long

[Cantor, Scott]

On 4/27/12 4:17 PM, "Ryan Suarez" <ryan.suarez at sheridanc.on.ca> wrote:
>
>Cisco's guide instructed adding this to IdP metadata:
>---
><SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
>Location="https://<YOUR_SHIBBOLETH_SERVER_FQDN>:8443/idp/profile/SAML2/SOA
>P/ECP" />
>---

And, I should note, this is wrong. While normal SOAP traffic uses that
port, that's for SOAP between the IdP and other SAML systems. ECP is sort
of SOAP-based, but the client is, well,  a client in the user sense, so it
generally goes to port 443.

Also, clients of ECP don't tend to rely on metadata to locate the IdP
endpoint. It's not impossible, and it's perfectly fine to include it for
completeness, but it's not quite like with web endpoints.

-- Scott