Content length of the SOAP request is too long
Cantor, Scott
cantor.2 at osu.edu
Fri Apr 27 21:29:58 BST 2012
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" />
>---
That's, well, kinda odd. ECP, really? Hmm.
And, well, that still makes no sense. There's no SOAP request *to* the SP
in ECP.
>Looks like there's no corresponding ProfileHandler/RequestPath for
>/SAML2/SOAP/ECP
>in my handler.xml/IdP v2.3.3? Is this the issue?
I doubt it. ECP is for non-browser clients. I assume you're using a
browser, so it makes no sense that ECP would be involved. But the reason
it's not there is that your config dates to before 2.3 and doesn't have
additional features added later.
-- Scott
More information about the users
mailing list