ECP help (was Re: Content length of the SOAP request is too long)

[Ryan Suarez]

On 12-04-27 4:29 PM, Cantor, Scott wrote:
>> 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.

oh yes, the config pre-dates v2.3.  For curiosity's sake I tried adding 
it to handler.xml:
----
<ph:ProfileHandler xsi:type="ph:SAML2ECP"
                     
inboundBinding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
                     
outboundBindingEnumeration="urn:oasis:names:tc:SAML:2.0:bindings:SOAP">
<ph:RequestPath>/SAML2/SOAP/ECP</ph:RequestPath>
</ph:ProfileHandler>
----

But I get the error:
ERROR 
[edu.internet2.middleware.shibboleth.common.config.BaseService:187] - 
Configuration was not loaded for shibboleth.HandlerManager service, 
error creating components.  The root cause of this error was: 
org.xml.sax.SAXParseException: cvc-elt.4.2: Cannot resolve 'ph:SAML2ECP' 
to a type definition for element 'ph:ProfileHandler'.

Any ideas?