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

[Paul B. Henson]

On Thu, Feb 12, 2026 at 01:24:02AM +0000, Paul B. Henson via users wrote:

> Now I guess I need to narrow down what part of my config for that is
> causing it, I assume other people are using the plugins themselves with
> 5.2 without issues.

I've got a bean defined in conf/global.xml to resolve OIDC client
secrets:

    <util:list id="shibboleth.oidc.ClientSecretValueResolvers">
      <bean parent="shibboleth.oidc.ResolverServiceClientSecretValueResolver"
            p:attributeIds="userPassword" />
    </util:list> 

with that bean present, it tries to load the transcoding rules before
opensaml is initialized:

2026-02-11 17:52:32,024 - / - DEBUG [net.shibboleth.idp.attribute.transcoding.impl.TranscodingRuleLoader:73] - Loading rules from directory (/opt/shibboleth-idp/conf/attributes/custom)
2026-02-11 17:52:34,262 - / - INFO [org.opensaml.core.config.InitializationService:47] - Initializing OpenSAML using the Java Services API

with that bean removed, it initializes opensaml before trying to load
the transcoding rules:

2026-02-11 17:55:33,960 - / - INFO [org.opensaml.core.config.InitializationService:47] - Initializing OpenSAML using the Java Services API
2026-02-11 17:55:35,830 - / - DEBUG [net.shibboleth.idp.attribute.transcoding.impl.TranscodingRuleLoader:73] - Loading rules from directory (/opt/shibboleth-idp/conf/attributes/custom)

Is this a bug? Is there somewhere else other than global.xml I'm
supposed to define this bean now? I don't recall why I defined it there,
other than that's where all my random local custom beans are defined.


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