Ex: Re: idp 5 disabling RemoteUser/X509 servets

[Paul B. Henson]

On Wed, Mar 27, 2024 at 12:44:20PM +0000, Cantor, Scott wrote:

> In the container log, yes, probably not in the IdP log, it's too early
> for that. That's why we spend time describing the need for managing
> container logging in all those examples.

Hmm, AFAIK I'm getting jetty level logs; both console logs (via
console-capture.ini) and logging-logback with a fairly similar config to
your example in the java-idp-jetty-base repo.

The only instances I see of net.shibboleth.idp.conf.impl are in the
console log, apparently from the output of jetty.server.dumpAfterStart?

jetty-console-2024_03_27.log:|     |  |  |  += ContainerInitializer{net.shibboleth.idp.conf.impl.ServletConfigServletContextInitializer,interested=[],applicable=[],annotated=[]} - STARTED
jetty-console-2024_03_27.log:|     |  |  |  += ContainerInitializer{net.shibboleth.idp.conf.impl.SpringConfigServletContextInitializer,interested=[],applicable=[],annotated=[]} - STARTED
jetty-console-2024_03_27.log:|     |  |  |  += ContainerInitializer{net.shibboleth.idp.conf.impl.RegisterFilterChainServletContextInitializer,interested=[],applicable=[],annotated=[]} - STARTED

Hmm, it looks like I can indirectly check whether the servlets were loaded
from the dump output:

|     |  |  |     |  |  +> [/Authn/X509]=>X509AuthHandler
|     |  |  |     |  |  +> X509AuthHandler==net.shibboleth.shared.spring.servlet.impl.DelegatingServletProxy at 7818dafc{jsp=null,order=-1,inst=true,async=false,src=JAKARTA_API:<null>,STARTED} - STARTED

|     |  |  |     |  |  +> [/Authn/RemoteUser]=>RemoteUserAuthHandler
|     |  |  |     |     +> RemoteUserAuthHandler==net.shibboleth.shared.spring.servlet.impl.DelegatingServletProxy at fa159e71{jsp=null,order=-1,inst=true,async=false,src=JAKARTA_API:<null>,STARTED} - STARTED

Which examples are you referring to? I just saw this in the release notes:

"The new version of web.xml contains a few context parameters that can be used to disable the RemoteUser and X509 servlets if they are not in use, and it is advisable to override those parameters using the container rather than by overriding web.xml."

but I must have missed any examples of actually setting the context
parameters or discussion of logging them.


-- 
Paul B. Henson  |  (909) 979-6361  |  http://www.cpp.edu/~henson/
Operating Systems and Network Analyst  |  henson at cpp.edu
California State Polytechnic University  |  Pomona CA 91768