Logging for an HTTP client bean

[Wessel, Keith]

Thanks, Scott. I'm testing with the full running IdP. It sends all of its logs (Tomcat container and Shibboleth) through a pipe to stdout for logging outside of the Docker container. I also tried letting it log to a file inside the Docker container with no difference.

I can, of course, upgrade to V5, but I was trying to knock out this small project first, and if I can't see why my data connector is reporting an unknown or invalid HTTP response from the web service query, I obviously can't do that. Perhaps I can get some log data from the folks running the API on the server side.

If I do try your last resort of adding jcl-over-slf4j to my war file, where would I find the appropriate jar to add?

Keith


-----Original Message-----
From: Cantor, Scott <cantor.2 at osu.edu> 
Sent: Monday, December 11, 2023 2:13 PM
To: Shib Users <users at shibboleth.net>
Cc: Wessel, Keith <kwessel at illinois.edu>
Subject: Re: Logging for an HTTP client bean

> Really? I'm almost positive I've changed logging behavior with properties in
> idp.properties before.

Only ones we specifically embedded into the logback file, and I didn't think that was one of them, probably because my copy is much older and doesn't contain it. I see it in both versions.

Notably that's not dynamically settable since properties aren't, but yes, it should work (though it has to be changed for V5 since the logger category is different).

> No results there, either.
> Rather maddening. Any other suggestions?

I suspect it's a missing logging bridge. The V4 client used commons logging, and that's supposed to be bridged by Spring. How are you actually testing the logging? The full IdP should work because Spring should supply the JCL support but possibly there's more involved, and the container could be interfering somehow. Maybe check your container's log.

With V5, the Apache project moved to slf4j, which obviously is the same as we use so it works out of the box regardless.

Worst case you can try adding jcl-over-slf4j to the warfile, but I don't think that should be necessary.

-- Scott