Skip to Content.
Sympa Menu

mace-opensaml-users - RE: [OpenSAML] Signature Validation Logging

Subject: OpenSAML user discussion

List archive

RE: [OpenSAML] Signature Validation Logging

Chronological Thread 
  • From: Swapna Gupta <>
  • To: "" <>
  • Subject: RE: [OpenSAML] Signature Validation Logging
  • Date: Thu, 26 May 2011 14:58:24 -0500
  • Accept-language: en-US
  • Acceptlanguage: en-US

Thanks. So I added jcl-over-slf4j.jar to the classpath, still no messages. Do
I need to do anything more?


-----Original Message-----

On Behalf Of Brent Putman
Sent: Thursday, May 26, 2011 12:50 PM

Subject: Re: [OpenSAML] Signature Validation Logging


On 5/26/11 12:50 PM, Swapna Gupta wrote:
> Thanks! I have added logback-core and logback-classic jars to the
> classpath. What else should I do to get the Debug messages from
> DigesterOuputStream? Reading the Logback documentation, it appears it is by
> default set to log at debug level to the console. But I don't see any
> messages on the console.

Ah, sorry, I spoke a little too quickly. To get logging from our
OpenSAML classes themselves, you do need to install an slf4j binding,
such as Logback.

To get logging from other libraries which don't use slf4j natively, you
need to address that logging framework's requirements. That
DigesterOutputStream is from Apache XML Security (Santuario) and uses
Apache Jakarta Commons Logging (JCL). So you need to get the actual log
output from JCL.

If you still want to use an SLF4J-based library like Logback as the
actual logging impl in your OpenSAML-based application (which is fine,
it's pretty good), then you need to install the SLF4J JCL to SLF4J
bridge jar. See:

It's the one listed there as jcl-over-slf4j.

Logback does log to the console by default. If you want it to go to a
file, etc. you just need a logback config file. The easiest is to just
put in your classpath. See the logback user manual for details.

Archive powered by MHonArc 2.6.16.

Top of Page