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

[Paul Hethmon]

Hmm, I know I've fiddled with this some and it doesn't complain on load.
My handler.xml starts with these defined:

<ph:ProfileHandlerGroup
xmlns:ph="urn:mace:shibboleth:2.0:idp:profile-handler"
                   
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                        xmlns:cl="com:clareity:shib:login"
                        xmlns:cs="org:clareitysecurity:shib:slo"
                   
xsi:schemaLocation="urn:mace:shibboleth:2.0:idp:profile-handler
classpath:/schema/shibboleth-2.0-idp-profile-handler.xsd
                        com:clareity:shib:login
classpath:/schema/clareity-login-handler.xsd
                        org:clareitysecurity:shib:slo
classpath:/schema/clareity-shib-slo-handler.xsd">

You can ignore my "clareity" ones in there, but one of the others must
define the ECP since I've got this in mine:


<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>

This stuff always tortures my brain when I have to look at it, but it has
to be defined in the default IdP profile handler xsd file. Are you running
this on 2.3.6?


Paul


On 5/1/12 4:37 PM, "Ryan Suarez" <ryan.suarez at sheridanc.on.ca> wrote:

>On 12-05-01 4:09 PM, Paul Hethmon wrote:
>> You've got a namespace issue. Somewhere in the versions there the
>> namespace used in the file changed. Actually I want to say the namespace
>> was added, don't remember exactly. But look at your other ProfileHandler
>> nodes and see if they use the "ph" prefix or not.
>
>Yes, the other ProfileHandler's have the "ph" prefix.  Thoughts?
>
>>>----
>>> <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'.