Debugging

The IBMSASL provider uses the Logging APIs to provide implementation logging output. This output can be controlled by using the logging configuration file and programmatic API (java.util.logging). The logger name used by the IBMSASL provider is javax.security.sasl. Here is a sample logging configuration file that enables the FINEST logging level for the IBMSASL provider.

    javax.security.sasl.level=FINEST
    handlers=java.util.logging.ConsoleHandler
    java.util.logging.ConsoleHandler.level=FINEST

For more information about this logging function, refer to the Oracle documentation.

The following table shows the mechanisms and the logging output that they generate.

Table 1. Mechanisms and their logging level and information.
Mechanism	Logging Level	Information Logged
CRAM-MD5	`FINE`	Configuration properties; challenge/response messages
DIGEST-MD5	`INFO`	Message discarded due to encoding problem (e.g., unmatched MACs, incorrect padding)
DIGEST-MD5	`FINE`	Configuration properties; challenge/response messages
DIGEST-MD5	`FINER`	More detailed information about challenge/response messages
DIGEST-MD5	`FINEST`	Buffers exchanged at the security layer
GSSAPI	`FINE`	Configuration properties; challenge/response messages
GSSAPI	`FINER`	More detailed information about challenge/response messages
GSSAPI	`FINEST`	Buffers exchanged at the security layer