Issue DescriptionWhile integrating Jaspersoft with SSO authentication, the code works fine with 6.0.1 and we have upgraded to 6.1.0 and it doesn't seem to work. We can login into the system but when we run any reports it throws "Java NullPopinter Exception" error. | [toc] |
2015-06-20 02:04:17,478 ERROR errorPage_jsp,http-bio-8080-exec-4:578 - stack trace of exception that redirected to errorPage.jsp java.lang.NullPointerException at java.util.Hashtable.<init>(Hashtable.java:296) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.Log4jMdcCompatibleThreadPoolExecutor.execute(Log4jMdcCompatibleThreadPoolExecutor.java:55) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.fillReport(EngineServiceImpl.java:607) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.executeReportUnitRequest(EngineServiceImpl.java:1941) at com.jaspersoft.jasperserver.api.engine.jasperreports.domain.impl.ReportUnitRequest.execute(ReportUnitRequest.java:67) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.execute(EngineServiceImpl.java:493)
Resolution
In applicationContext-externalAuth-preAuth-mt.xml, remove or comment out this line.
<alias name="${bean.authenticationProcessingFilter}"
alias="proxyAuthenticationProcessingFilter"/>
PLEASE NOTE THAT THIS IS A TEMPORARY WORKAROUND. THIS ISSUE IS BEING ADDRESSED BY BUG REPORTS 42523 AND 42616.
This simple workaround is posted here so that you can continue development on v6.1. There are 2 known deficiencies.
Custom implementation of com.jaspersoft.jasperserver.api.common.crypto.CipherI will not work without this filter.
Only existing external users can log in.
Ref. Case 00061170
Recommended Comments
There are no comments to display.