Config cleanup

[Wessel, Keith]

I can't help you there since I never ran into that one. There's definitely a reference to it in the services-system.xml on the classpath. Back when the system tree was still on the filesystem, it was a conditional load. It looks like this:

    <util:list id="shibboleth.DefaultManagedBeanResources">
        <value>%{idp.home}/conf/managed-beans.xml</value>
    </util:list>

Do you still have a system dir under your IdP home? If so, you can safely eliminate it assuming you didn't put any customizations in the wrong place, and that might take care of it.

Keith

From: users <users-bounces at shibboleth.net> On Behalf Of Andrew Jason Morgan
Sent: Friday, February 11, 2022 3:55 PM
To: Shib Users <users at shibboleth.net>
Subject: Re: Config cleanup

Thanks Keith!  I removed the references to the system/conf/*.xml files from services.xml.


Do you know how to eliminate the message about skipping conf/managed-beans.xml?

I found it being loaded from conf/services-system.xml (inside idp-conf-impl-*.jar):

    <util:list id="shibboleth.DefaultManagedBeanResources">
        <value>%{idp.home}/conf/managed-beans.xml</value>
    </util:list>

I don't have a copy of this file in my conf, dist/conf, or idp-conf-impl-*.jar anywhere.

Thanks,
Andy

________________________________
From: users <users-bounces at shibboleth.net> on behalf of Wessel, Keith <kwessel at illinois.edu>
Sent: Friday, February 11, 2022 12:25 PM
To: Shib Users <users at shibboleth.net>
Subject: RE: Config cleanup


[This email originated from outside of OSU. Use caution with links and attachments.]

Yes, you can remove those references. Everything has moved to system configs inside idp-conf-impl-*.jar on the classpath.



Keith





From: users <users-bounces at shibboleth.net> On Behalf Of Andrew Jason Morgan
Sent: Friday, February 11, 2022 12:44 PM
To: Shib Users <users at shibboleth.net>
Subject: Config cleanup



I've been upgrading/modernizing our IDP configuration for v4.1.



In the logs during startup, I see the following messages about skipping non-existent resources:



INFO [net.shibboleth.ext.spring.util.ApplicationContextBuilder:346] - Skipping non-existent resource: ServletContext resource [/opt/shibboleth-idp/system/conf/metadata-providers-system.xml]

INFO [net.shibboleth.ext.spring.util.ApplicationContextBuilder:346] - Skipping non-existent resource: ServletContext resource [/opt/shibboleth-idp/system/conf/saml-nameid-system.xml]

INFO [net.shibboleth.ext.spring.util.ApplicationContextBuilder:346] - Skipping non-existent resource: ServletContext resource [/opt/shibboleth-idp/system/conf/relying-party-system.xml]

INFO [net.shibboleth.ext.spring.util.ApplicationContextBuilder:346] - Skipping non-existent resource: ServletContext resource [/opt/shibboleth-idp/system/conf/access-control-system.xml]

INFO [net.shibboleth.ext.spring.util.ApplicationContextBuilder:346] - Skipping non-existent resource: ServletContext resource [/opt/shibboleth-idp/conf/managed-beans.xml]





There is a note in the v4.1.0 release notes about removing "%{idp.home}/system/messages/messages" from conf/services.xml.  Should I remove these other system file references as well?  I'm not sure where managed-beans.xml is referenced.



Thanks,

Andy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20220211/ebf69a5a/attachment.htm>