IDP 2.4.1 ECP

Brent Putman putmanb at
Wed May 20 00:19:13 EDT 2015

On 5/19/15 11:51 PM, MA Lanxin wrote:
> Restart tomcat and httpd. When I link to

Well, you can't literally "link" to this.  It's an endpoint that
supports/requires the SOAP binding, so an ECP client has to invoke it
in the proper manner for a SOAP binding.

> Caused by: This message decoder only supports the HTTP POST method
>         at org.opensaml.saml2.binding.decoding.HTTPSOAP11Decoder.doDecode( ~[opensaml-2.6.2.jar:na]
>         at org.opensaml.saml2.binding.decoding.HandlerChainAwareHTTPSOAP11Decoder.decode( ~[opensaml-2.6.2.jar:na]
>         at edu.internet2.middleware.shibboleth.idp.profile.saml2.SAML2ECPProfileHandler.decodeRequest( [shibboleth-identityprovider-2.4.1.jar:na]
>         ... 28 common frames omitted

The error is pretty self-explanatory.  The ECP  has to POST the message
to the IdP endpoint.  It can' be an HTTP GET or other HTTP method.  Has
to follow the SAML SOAP binding spec.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the users mailing list