delegation in IDP3

Rod Widdowson rdw at steadingsoftware.com
Fri Jun 10 10:12:34 EDT 2016


So this is a mystery:

> net.shibboleth.utilities.java.support.service.ServiceException:
> org.springframework.beans.factory.BeanDefinitionStoreException:
>  Unexpected exception parsing XML document from file
>  [/usr/local/shibboleth-idp/conf/relying-party.xml]; nested exception is
>  java.lang.IllegalArgumentException:
>  Can not locate BeanDefinitionParser for element:
>  {urn:mace:shibboleth:2.0:relying-party}ProfileConfiguration, carrying
>     xsi:type: {urn:mace:shibboleth:2.0:relying-party:saml}SAML2SSOSProfile
>   at
>
net.shibboleth.ext.spring.service.ReloadableSpringService.doReload(Reloadabl
e
> SpringService.java:334)
> 
> The offending element currently looks like:
> 
>     <ProfileConfiguration xsi:type="saml:SAML2SSOSProfile"
>         maximumTokenDelegationChainLength="1"
>         allowDelegation="true"
>         delegationPredicateRef="testDelegationPredicate"
>         signAssertions="always"
>         encryptNameIds="never" />
 
> Is there something I am missing that can get past this error?

I'm assuming that you are running the latest IdP...

All I can suggest right now is to turn on trace logging for
net.shibboleth.ext.spring.util 

<logger name="net.shibboleth.ext.spring.util" level="TRACE"/>

You should then see in your log:

TRACE [net.shibboleth.ext.spring.util.BaseSpringNamespaceHandler:112] -
Attempting to find parser for element of type:
{urn:mace:shibboleth:2.0:relying-party:saml}SAML2SSOSProfile

But if it is followed by 

TRACE [net.shibboleth.ext.spring.util.BaseSpringNamespaceHandler:119] -
Attempting to find parser with element name:
{urn:mace:shibboleth:2.0:relying-party}ProfileConfiguration

And then the log segment you gave, then there is something very very weird
going on.



More information about the users mailing list