IDP 2.4.1 ECP

[Matthew Slowe]

On Wed, May 20, 2015 at 12:19:13AM -0400, Brent Putman wrote:
>    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: org.opensaml.ws.message.decoder.MessageDecodingException: This message decoder only supports the HTTP POST method
>          at org.opensaml.saml2.binding.decoding.HTTPSOAP11Decoder.doDecode(HTTPSOAP11Decoder.java:119) ~[opensaml-2.6.2.jar:na]
>          at org.opensaml.saml2.binding.decoding.HandlerChainAwareHTTPSOAP11Decoder.decode(HandlerChainAwareHTTPSOAP11Decoder.java:62) ~[opensaml-2.6.2.jar:na]
>          at edu.internet2.middleware.shibboleth.idp.profile.saml2.SAML2ECPProfileHandler.decodeRequest(SAML2ECPProfileHandler.java:319) [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.

https://blogs.kent.ac.uk/unseenit/2013/02/07/simple-shibboleth-ecp-test/
has a "simple" method of testing an ECP endpoint. No idea if it'll work
in your instance but it might help you along the way :-)

-- 
Matthew Slowe | Server Infrastructure Officer
IT Infrastructure, Information Services, University of Kent
Room S21, Cornwallis South
Canterbury, Kent, CT2 7NZ, UK
Tel: +44 (0)1227 824265 

www.kent.ac.uk/is | @UnikentUnseenIT | @UKCLibraryIt