IdP v3.2.1 unable to handle v2.4.0 metadata configuration

[Tom Jordaan]

Hi all,

I'm in the process of attempting an upgrade to IdP v3.2.1, from 2.4.0. At the same time, I've upgraded the Tomcat instance to version 8. The Oracle JDK runtime is 1.7.0 u65, unchanged from the Tomcat 6 install our production IdP is hosted inside.

The upgrade was carried out using the upgrade script, in tree that was a copy of the existing installation. This script completed without errors.

The Tomcat upgrade was successful, and gives me a manager page.

We're using the UK Federation metadata. I've made ensure the v2 compatibility is enabled, but starting up gives me lots of errors, around the metadata resolver. Startup isn't successful. The final exception is:

2016-11-15 11:22:36,141 - ERROR [org.springframework.web.context.ContextLoader:353] - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'shibboleth.MetadataResolverService' defined in file [/usr/local/shibboleth-idp/system/conf/services-system.xml]: Invocation of init method failed; nested exception is net.shibboleth.utilities.java.support.component.ComponentInitializationException: Service 'shibboleth.MetadataResolverService': Unexpected error during initial load
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1578)
Caused by: net.shibboleth.utilities.java.support.component.ComponentInitializationException: Service 'shibboleth.MetadataResolverService': Unexpected error during initial load
        at net.shibboleth.utilities.java.support.service.AbstractReloadableService.doInitialize(AbstractReloadableService.java:189)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ShibbolethMetadata': Cannot create inner bean '(inner bean)#2dea9a99' of type [org.opensaml.saml.metadata.resolver.ChainingMetadataResolver] while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#2dea9a99': Cannot create inner bean '(inner bean)#594ed842' of type [org.opensaml.saml.metadata.resolver.impl.FileBackedHTTPMetadataResolver] while setting bean property 'resolvers' with key [2]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#594ed842': Initialization of bean failed; nested exception is java.lang.UnsupportedOperationException
        at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:313)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#2dea9a99': Cannot create inner bean '(inner bean)#594ed842' of type [org.opensaml.saml.metadata.resolver.impl.FileBackedHTTPMetadataResolver] while setting bean property 'resolvers' with key [2]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#594ed842': Initialization of bean failed; nested exception is java.lang.UnsupportedOperationException
        at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:313)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#594ed842': Initialization of bean failed; nested exception is java.lang.UnsupportedOperationException
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553)
Caused by: java.lang.UnsupportedOperationException: null
        at java.util.AbstractList.add(Unknown Source)

I suspect the failure begins here:

2016-11-15 11:22:28,183 - ERROR [net.shibboleth.utilities.java.support.service.AbstractReloadableService:188] - Service 'shibboleth.MetadataResolverService': Unexpected error during initial load {}
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ShibbolethMetadata': Cannot create inner bean '(inner bean)#3705e722' of type [org.opensaml.saml.metadata.resolver.ChainingMetadataResolver] while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#3705e722': Cannot create inner bean '(inner bean)#228fcdfd' of type [org.opensaml.saml.metadata.resolver.impl.FileBackedHTTPMetadataResolver] while setting bean property 'resolvers' with key [2]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#228fcdfd': Initialization of bean failed; nested exception is java.lang.UnsupportedOperationException
        at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:313)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#3705e722': Cannot create inner bean '(inner bean)#228fcdfd' of type [org.opensaml.saml.metadata.resolver.impl.FileBackedHTTPMetadataResolver] while setting bean property 'resolvers' with key [2]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#228fcdfd': Initialization of bean failed; nested exception is java.lang.UnsupportedOperationException

It's not clear to me which configuration element might be causing this. I don't believe we have an unusual config in production.

Can anyone suggest a possible way forward?

Thanks!

Regards,

--
Tom Jordaan
Infrastructure Systems Engineer, IT Services
Queen Mary, University of London
Tel: 020 7882 6940
Email: t.s.jordaan at qmul.ac.uk

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20161115/6290418e/attachment.html>