idp start up warnings after upgrade

Cantor, Scott cantor.2 at osu.edu
Tue Apr 4 10:08:04 EDT 2017


> 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).

What warning? You can't use Nabble (like seriously, don't), omit all the context, and expect me to know what you're talking about.

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

I have no idea what I meant if this is some reference to some comment I made more than a day ago. I don't track these threads, I simply toss off quick answers as fast as possible and move on.

> 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'

You get that warning because Spring does a lot of weird things internally when it does type conversions and it will attempt them before it sees that there's a better constructor to use that doesn't require a bad conversion. Most of the time it goes away if you add a constructor argument name or type that would disambiguate the conversion and prevent it from attempting a conversion that isn't intended.
 
-- Scott



More information about the users mailing list