Configuring Logging for Debugging

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/log4j.properties file, in the form:

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

For example:

  log4j.logger.org.springframework.security=DEBUG, stdout, fileout

You must restart the server for your changes to take effect. For more information about log configuration, see the 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

org.springframework.security

Subset of Spring Security related to LDAP

org.springframework.security.ldap

Subset of Spring related to LDAP

org.springframework.ldap

CAS

org.jasig.cas

JasperReports Server external authentication API

com.jaspersoft.jasperserver.multipleTenancy.security.externalAuth

Subset of JasperReports Server external authentication API related to single tenancy

com.jaspersoft.jasperserver.api.security.externalAuth

Enabling org.springframework.security.ldap and org.springframework.security together creates duplicate entries in the logs.

Feedback