Logging for an HTTP client bean

Cantor, Scott cantor.2 at osu.edu
Mon Dec 11 20:12:32 UTC 2023


> 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




More information about the users mailing list