Shibboleth IDP Upgrade from V4.0.1 to V4.1.2

[Reddimalli, Anusha]

I did upgrade from beginning again. I ran install.sh from the V4.1.2 folder. 

This is how my system folder looks like after upgrade. I did not make any changes.

total 4
drwxrwxr-x 2 shibduser shibduser  78 Jun 16 09:31 conf
-r--r--r-- 1 shibduser shibduser 566 Jun 16 09:31 DONOTTOUCH

After upgrade completed I tried to restart the tomcat. I got the below error.

Context initialization failed
org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Failed to import bean definitions from relative location [/var/home/shibduser/shibboleth-idp/conf/global.xml]
Offending resource: class path resource [net/shibboleth/idp/conf/global-system.xml]; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from URL [jar:file:/var/home/shibduser/apache-tomcat-9.0.46/webapps/idp/WEB-INF/lib/idp-conf-impl-4.1.2.jar!/net/shibboleth/idp/conf/var/home/shibduser/shibboleth-idp/conf/global.xml]; nested exception is java.io.FileNotFoundException: JAR entry net/shibboleth/idp/conf/var/home/shibduser/shibboleth-idp/conf/global.xml not found in /var/home/shibduser/apache-tomcat-9.0.46/webapps/idp/WEB-INF/lib/idp-conf-impl-4.1.2.jar

I have made below changes in web.xml

<param-value>classpath*:/META-INF/net.shibboleth.idp/preconfig.xml,${idp.home}/system/conf/global-system.xml,classpath*:/META-INF/net.shibboleth.idp/postconfig.xml</param-value>
<param-value>classpath*:/META-INF/net/shibboleth/idp/mvc/preconfig.xml,${idp.home}/system/conf/mvc-beans.xml,${idp.home}/system/conf/webflow-config.xml,classpath*:/META-INF/net/shibboleth/idp/mvc/postconfig.xml</param-value>

Restared the tomcat again and I got the below error

[ERROR] : org.springframework.web.context.ContextLoader: Context initialization failed
org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Failed to import bean definitions from URL location [classpath:/net/shibboleth/idp/conf/global-system.xml]
Offending resource: file [/var/home/shibduser/shibboleth-idp/system/conf/global-system.xml]; nested exception is org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Failed to import bean definitions from relative location [/var/home/shibduser/shibboleth-idp/conf/global.xml]
Offending resource: class path resource [net/shibboleth/idp/conf/global-system.xml]; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from URL [jar:file:/var/home/shibduser/apache-tomcat-9.0.46/webapps/idp/WEB-INF/lib/idp-conf-impl-4.1.2.jar!/net/shibboleth/idp/conf/var/home/shibduser/shibboleth-idp/conf/global.xml]; nested exception is java.io.FileNotFoundException: JAR entry net/shibboleth/idp/conf/var/home/shibduser/shibboleth-idp/conf/global.xml not found in /var/home/shibduser/apache-tomcat-9.0.46/webapps/idp/WEB-INF/lib/idp-conf-impl-4.1.2.jar



Thanks & Regards
Anusha Reddimalli

-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Cantor, Scott
Sent: Tuesday, June 15, 2021 6:07 PM
To: Shib Users <users at shibboleth.net>; users <users-bounces at shibboleth.net>
Subject: Re: Shibboleth IDP Upgrade from V4.0.1 to V4.1.2

On 6/15/21, 5:33 PM, "users on behalf of Reddimalli, Anusha" <users-bounces at shibboleth.net on behalf of REDDIMAA at mailbox.sc.edu> wrote:

>    I am upgrading IDP V4.0.1 to V4.1.2. 

In place? Without the servlet container running? As documented?

That seems impossible to me given that it's referencing a system file on the file system that doesn't even exist anymore if you had upgraded in place. That system file content is out of date and will not work, and is referencing old classes that don't exist.

An upgrade to 4.1 will leave essentially nothing left in system/ except a few stubbed files for compatibility with the older web.xml file. It removes and replaces them. You have to have deliberately subverted the upgrade process in some way to prevent it from dealing with those files.

Your problem is related to the fact that those system files have been put back after the upgrade completed. You can't "fix" it from there, you need to start over from the beginning and upgrade again, but whatever you did that caused that is what needs to be prevented.

-- Scott


-- 
For Consortium Member technical support, see https://protect2.fireeye.com/v1/url?k=0fcb201c-505018c8-0fcb6edd-8680d8d86cc5-83e47e19be21df3f&q=1&e=3852cb17-347e-4f13-851e-8a7c7b1be1c8&u=https%3A%2F%2Fwiki.shibboleth.net%2Fconfluence%2Fx%2FcoFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net