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:

For example:

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. the figure “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 LDAP1Enabling org.springframework.security.ldap and org.springframework.security together creates duplicate entries in the logs.

org.springframework.security.ldap[/code]                    

Subset of Spring related to LDAP

org.springframework.ldap[/code]                    

CAS

org.jasig.cas[/code]                    

JasperReports Server external authentication API

com.jaspersoft.jasperserver.multipleTenancy.security.externalAuth[/code]                    

Subset of JasperReports Server external authentication API related to single tenancy

com.jaspersoft.jasperserver.api.security.externalAuth[/code]