Shibboleth Upgrade from 4.2.1 to 4.3.3 has resulted in the logging to stop working

[Cantor, Scott]

> That's the issue the Jetty/Shibboleth service does start is
> shows as running with no errors in the syslog, but the service
> logs aka idp-*.log files do not log anything.

Once the IdP is running, it logs internally (and I know of no reasons it doesn't). Until then, Jetty is the only source of debugging, and if it isn't logging itself, then that's the primary issue to fix to determine why the IdP webapp didn't start successfully.

Our examples include the material related to leveraging logback to do its logging, but Jetty's logging is ultimately whatever one decides it should be, and no, it's not the easiest. One of the areas Tomcat is a bit better at.

Jetty 12 is a beast because of all the idiotic Java/Jakarta changes and the multiple personality mess, but its logging isn't all that different from 11.

The most obvious point is that Jetty 12 running IdP 4 would have to be using the ee8 deployment modules, since it's pre-Jakarta, and it wouldn't start under ee9+.

-- Scott