idp start up warnings after upgrade

[Christopher Greiner]

I've also just upgraded our standby server to 3.3.1 from 3.2.1 and running
into this warning too upon restarting my container (tomcat for what it's
worth).

Scott, what do you mean exactly by "when the legacy format is used"?

I updated the configured PrincipalConnector I had in v2 in my attribute
resolver and moved it to the subject-c14n.xml file:

<bean id="shibboleth.NameTransformPredicate"
parent="shibboleth.Conditions.RelyingPartyId">
        <constructor-arg>
            <list>
              <value>https://entityidA/shibboleth</value>
              <value>https://entityidB/shibboleth</value>
              <value>https://entityidC/shibboleth</value>
            </list>
        </constructor-arg>
    </bean>

and I commented the c14n/LegacyPrincipalConnector bean reference in that
file too yet I see this warning in the logs, which mentions only the first
value in the list (no warning for entityidB and C):

2017-04-03 13:30:08,386 - WARN
[net.shibboleth.ext.spring.config.StringBooleanToPredicateConverter:51] - []
- Unrecognized value 'https://entityidA/shibboleth' converted to false; if
intentional, explicitly use 'false'




--
View this message in context: http://shibboleth.1660669.n2.nabble.com/idp-start-up-warnings-after-upgrade-tp7632123p7632416.html
Sent from the Shibboleth - Users mailing list archive at Nabble.com.