IdP 3.4.3 for Windows - upgrade observations

[Doan, Tommy]

Below are a few observations from our IdP for Windows 3.3.1 upgrade to 3.4.3 using packaged Jetty, for awareness in case they're helpful. After working through these few items, 3.4.3 appears to be working well thus far in pre-production.


  *   JETTY_BASE\start.ini from IdP 3.3 includes module=logging, and attempting to load that module prevents startup of IdP 3.4.3 after an upgrade. We noticed that a default installation of 3.4.3 does not include start.ini, so we just removed it manually.
  *   JETTY_BASE\etc\jetty.xml was removed as part of the upgrade. Our only customization there is to add a ForwardedRequestCustomizer from our load balancer, so not a big deal to recreate.
  *   JETTY_BASE\modules\backchannel.mod was included in IdP 3.3 but not included in a default installation of 3.4.3, but the file is not removed when upgrading from 3.3 to 3.4.3. ProcRun logs an error about it, and since we don't even use a back channel we just removed it manually.
  *   The dist version of conf\c14n\subject-c14n.xml does not comment out <ref bean="c14n/LegacyPrincipalConnector" /> even though there is a deprecation warning about it in the IdP logs.
  *   Also, previously we didn't have to stop the IdP prior to rebuilding the WAR file - we would simply restart it after a rebuild. However, stopping first appears to be a requirement now as the build fails because otherwise ANT cannot delete idp.war. We don't rebuild our WAR file very often at all so this may not be new as of 3.4.3.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20190214/98979e27/attachment.html>