[EXT] idp 5.2.0 upgrade fails - org.opensaml.core.xml.config.XMLObjectProviderRegistry was unavailable

[Paul B. Henson]

On Wed, Feb 11, 2026 at 10:08:49PM -0500, Scott Cantor wrote:

> As a workaround, adding depends-on="shibboleth.OpenSAMLConfig" might
> fix it, and that could ultimately go into the parent bean to fix it.

Hmm, looks like that caused a different dependency issue:

2026-02-11 19:27:46,529 - / - WARN [net.shibboleth.shared.spring.context.FilesystemGenericApplicationContext:628] - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'shibboleth.AutoWiredNodeProcessingMetadataFilter' defined in class path resource [net/shibboleth/idp/conf/metadata-providers-system.xml]: Unsatisfied dependency expressed through constructor parameter 0: Error creating bean with name 'net.shibboleth.oidc.metadata.impl.ClientInformationNodeProcessor#0' defined in URL [jar:file:/var/lib/jetty/tmp/jetty-127_0_0_1-80-idp_war-_idp-localhost-13140556998189473862/webinf/WEB-INF/lib/idp-plugin-oidc-op-impl-4.3.0.jar!/META-INF/net/shibboleth/idp/service/saml/metadata/postconfig.xml]: Cannot resolve reference to bean 'shibboleth.oidc.DefaultKeyInfoProviders' while setting constructor argument                         
2026-02-11 19:27:46,531 - / - ERROR
[net.shibboleth.shared.service.AbstractReloadableService:179] - Service
'shibboleth.MetadataResolverService': Initial load failed

I'll go ahead and open an issue at this point, hopefully one of the OIDC
guys can help sort it out.

Thanks...


-- 
Paul B. Henson | Operating Systems and Network Analyst
henson at cpp.edu | California State Polytechnic University Pomona