Configuring Logging for Debugging

If your connection is failing, for example, with an “Invalid credentials supplied” error, and you cannot find information in the JasperReports Server logs, you may want to enable logging for Spring Security or JasperReports Server external authentication.

To enable logging, add the corresponding line to the <js‑webapp>/WEB‑INF/ file, in the form:

  log4j.logger.<logger-classname> = <log-level>, <output-type>

For example:, stdout, fileout

You must restart the server for your changes to take effect. For more information about log configuration, see the TIBCO JasperReports Server Administrator Guide.

You can reduce impact on performance by restricting logging to functionality that you are interested in, for example, to a subset of Spring Security instead of all of Spring Security. “Useful Logger Classnames for External Authentication” shows some logger classnames commonly used when debugging authentication.

Useful Logger Classnames for External Authentication

Functionality to Log

Logger Classname

Spring Security

Subset of Spring Security related to LDAP
Useful subsets of Spring Security's LDAP logging
Other LDAP-related Spring Security loggers

Subset of Spring related to LDAP




JasperReports Server external authentication API

Subset of external authentication API related to single tenancy
Subset of external authentication API related to token-based authentication
Subset of external authentication API related to external database authentication

Enabling a logger and a sublogger together creates duplicate entries in the logs. For example, and creates duplicate entries.