Upgrade failing for IdP 3.3.1
Rory Larson
rlarson1 at unl.edu
Thu Mar 30 17:24:19 EDT 2017
Hi,
I'm attempting to upgrade a Shibboleth IdP installation to 3.3.1, from 3.2.1, on Linux. I followed the instructions on the confluence, IDP30/Upgrading page. Everything seemed to go smoothly, but Tomcat gave 404 errors when I tried to access the default /idp/shibboleth xml file.
Next, I tried doing a clean install, which again went smoothly. This time, Tomcat worked, but without the content. I managed to get the metadata put into the new system and to modify the metadata-provider.xml file so that Tomcat still worked. But now I'm having trouble recreating the attribute-resolver.xml file with the old modifications. Pretty much anything I add in causes Tomcat to die. It seems that the namespace system has been changed, and that should require extensive modification throughout the file. But so far I haven't been able to get anything to work.
For example, we have an id attribute from our LDAP called unlUNCWID. The original file handled it as:
<resolver:AttributeDefinition id="unlUNCWID" xsi:type="Simple" xmlns="urn:mace:shibboleth:2.0:resolver:ad"
sourceAttributeID="unlUNCWID">
<resolver:Dependency ref="myLDAP" />
<resolver:AttributeEncoder xsi:type="SAML1String" xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
name="urn:mace:dir:attribute-def:unlUNCWID" />
<resolver:AttributeEncoder xsi:type="SAML2String" xmlns="urn:mace:shibboleth:2.0:attribute:encoder"
name="urn:oid:1.3.6.1.4.1.9904.1.1.1.1.8" friendlyName="unlUNCWID" />
<resolver:AttributeEncoder xsi:type="enc:SAML2StringNameID"
nameFormat="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent" />
</resolver:AttributeDefinition>
I modified it, as well as I could work out from examples in the new attribute-resolver.xml file, to be:
<AttributeDefinition id="unlUNCWID" xsi:type="Simple" sourceAttributeID="unlUNCWID">
<Dependency ref="myLDAP" />
<AttributeEncoder xsi:type="SAML1String" name="urn:mace:dir:attribute-def:unlCWID" encodeType="false" />
<AttributeEncoder xsi:type="SAML2String" name="urn:oid:1.3.6.1.4.1.9904.1.1.1.1.8" friendlyName="unlUNCWID" encodeType="false" />
<SourceAttribute>unlUNCWID</SourceAttribute>
</AttributeDefinition>
When this is added to the new default attribute-resolver.xml file, Tomcat dies. The message at the bottom of the idp-process log is:
2017-03-30 13:46:04,491 - ERROR [org.springframework.web.context.ContextLoader:351] - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'shibboleth.metrics.RegisterMetricSets$child#0' defined in file [/opt/shibboleth-idp/system/conf/../../conf/admin/metrics.xml]: Cannot resolve reference to bean 'shibboleth.metrics.AttributeResolverGaugeSet' while setting bean property 'arguments' with key [7]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'shibboleth.metrics.AttributeResolverGaugeSet' defined in file [/opt/shibboleth-idp/system/conf/general-admin-system.xml]: Invocation of init method failed; nested exception is net.shibboleth.utilities.java.support.component.ComponentInitializationException: Injected service was null or not an AttributeResolver
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:359)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'shibboleth.metrics.AttributeResolverGaugeSet' defined in file [/opt/shibboleth-idp/system/conf/general-admin-system.xml]: Invocation of init method failed; nested exception is net.shibboleth.utilities.java.support.component.ComponentInitializationException: Injected service was null or not an AttributeResolver
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1578)
Caused by: net.shibboleth.utilities.java.support.component.ComponentInitializationException: Injected service was null or not an AttributeResolver
at net.shibboleth.idp.attribute.resolver.impl.AttributeResolverServiceGaugeSet.doInitialize(AttributeResolverServiceGaugeSet.java:104)
Any ideas on this? I'm not sure which way to go from here.
Thanks,
Rory
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170330/8852cf8e/attachment.html>
More information about the users
mailing list