ee.ashley

I noticed this other question here: http://community.jaspersoft.com/questions/816716/how-pass-login-external-users This sounds similar to what I am experiencing, but the build of JasperServer we have appears to be 5.2 already. Looking through the server logs, logging in via the regular login page appears to go through the vendor's external JAAS authentication provider. However, trying to use the URL parameters on an arbitrary page results in it trying to use the InternalDaoAuthenticationProvider instead.

Sorry to bring back an old question, but what were the symptoms of this particular problem? I am working with a vendor that has integrated jasperserver-pro into their product and after a recent upgrade they did for us, external users are not able to authenticate via the j_username/j_password URL parameters anymore. The JasperServer version looks to be 5.2, but I'm not sure how much customization they have done and if they missed the fix or not. Is it possible to tell if our GET/POST parameter authentication issues are being caused by this same issue, or if it is due to something else? Thanks

The users are being authenticated via a proprietary back-end system from a vendor. The logins work through the main login screen, or if I use the j_username/j_password on the j_spring_security_check URL, but not against arbitrary JasperServer URLs. Is there any configuration that would use different authentication methods depending on the login method used?

When I try to use the j_username and j_password, I get a debug error message like this in the jasperserver.log: 2014-06-02 14:09:21,470 DEBUG RequestParameterAuthenticationFilter,http-80-6:78 - User [uSERNAME] failed to authenticate: com.jaspersoft.jasperserver.api.metadata.user.service.impl.UserIsNotInternalException: User needs to be internal to be authenticated by class com.jaspersoft.jasperserver.multipleTenancy.MTDaoAuthenticationProvider

Thanks olvifsk, when I try this, for some reason, it doesn't log me in. Rather, I just get an error on the login screen: "Invalid credentials supplied. Could not login to JasperReports server." If I use the same j_username and j_password using just the j_spring_security_check URL, it works though. Is there any configuration in JapserServer that may be preventing this from working?

I know that it is possible to automatically log into the Jasper Reports Server using a URL such as: http://hostname/jasperserver-pro/j_spring_security_check?j_username=username&j_password=password This usually takes me directly to the flow.html?_flowId=searchFlow page. However, is it possible to specify a specific page to load in the URL? For example, if I want to embed an automatically generated report into another page, is it possible to be redirected to an arbitrary page after completing the j_spring_security check login? If I'm embedding this into an iframe, for example, I don't want to have the user navigate to the report manually - I want the page to load directly to the relevant report.

I've traced through the Java code and found that there is a hashmap in the session that appears to store references to the images that need to be generated. This hashmap appears to have a max size of 10. If I increased this size in the debugger to a larger number (exceeding the number of charts I try to generate concurrently), then I could get all charts to render without issue. Otherwise, any more than 10 charts resulted in the exceptions being thrown. I saw that this class has a setMaxSize method in the LRUSessionObjectAccessor.java file, but even when I set a breakpoint on this, it never seemed to be called. I also grepped through the Java source files themselves and could not find any calls to setMaxSize either. Does anyone know where the limit of 10 gets set? And is there a way to increase this without necessitating a code change? EDIT: I found that the applicationContext.xml settings file has a maxSize property, which has a comment regarding dashboard image loading problems. I tested updating this setting to a larger number in the community edition and found that it addressed my chart loading issues. I am trying to get this change tested in our production JasperServer Pro installation to see if it helps as well.

With JapserServer 4.5.0, I am experiencing an issue where if I pull a report with a chart multiple times simultaneously (to simulate multiple client requests or to simulate a dashboard with multiple chart reports), often times at least one or two of the charts will fail to render (shows a broken image link place holder in my browser) and the following exception appears in the log: 2013-07-18 15:57:05,966 ERROR errorPage_jsp,http-8080-6:259 - JSException: The JasperPrint object 11355625_1374184619754 cannot be found.2013-07-18 15:57:05,967 ERROR errorPage_jsp,http-8080-6:487 - stack trace of exception that redirected to errorPage.jspcom.jaspersoft.jasperserver.api.JSException: jsexception.jasperprint.not.found at com.jaspersoft.jasperserver.war.control.ReportImageController.handleRequest(ReportImageController.java:99) at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:807) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571) at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:501) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:399) at com.jaspersoft.jasperserver.api.security.IPadSupportFilter.doFilter(IPadSupportFilter.java:67) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:411) at com.jaspersoft.jasperserver.api.security.JSSwitchUserProcessingFilter.doFilterHttp(JSSwitchUserProcessingFilter.java:154) at org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:411) at org.springframework.security.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:109) at org.springframework.security.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:411) at org.springframework.security.ui.ExceptionTranslationFilter.doFilterHttp(ExceptionTranslationFilter.java:101) at org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:411) at org.springframework.security.providers.anonymous.AnonymousProcessingFilter.doFilterHttp(AnonymousProcessingFilter.java:105) at org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:411) at com.jaspersoft.jasperserver.api.metadata.user.service.impl.MetadataAuthenticationProcessingFilter.doFilter(MetadataAuthenticationProcessingFilter.java:139) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:411) at com.jaspersoft.jasperserver.war.util.RequestParameterAuthenticationFilter.doFilter(RequestParameterAuthenticationFilter.java:97) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:411) at org.springframework.security.ui.basicauth.BasicProcessingFilter.doFilterHttp(BasicProcessingFilter.java:174) at org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:411) at com.jaspersoft.jasperserver.war.UserPreferencesFilter.doFilter(UserPreferencesFilter.java:184) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:411) at org.springframework.security.ui.AbstractProcessingFilter.doFilterHttp(AbstractProcessingFilter.java:278) at org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:411) at com.jaspersoft.jasperserver.war.UserPreferencesFilter.doFilter(UserPreferencesFilter.java:184) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:411) at com.jaspersoft.jasperserver.api.logging.filter.BasicLoggingFilter.doFilter(BasicLoggingFilter.java:53) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:411) at com.jaspersoft.jasperserver.api.security.JSCsrfGuardFilter.doFilter(JSCsrfGuardFilter.java:81) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:411) at com.jaspersoft.jasperserver.api.security.WebAppSecurityFilter.doFilter(WebAppSecurityFilter.java:83) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:411) at com.jaspersoft.jasperserver.war.MultipartRequestWrapperFilter.doFilter(MultipartRequestWrapperFilter.java:90) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:411) at org.springframework.security.context.HttpSessionContextIntegrationFilter.doFilterHttp(HttpSessionContextIntegrationFilter.java:235) at org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:411) at org.springframework.security.util.FilterChainProxy.doFilter(FilterChainProxy.java:188) at org.springframework.security.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:99) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.jaspersoft.jasperserver.war.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:67) at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:236) at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:558) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:859) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:579) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1555) at java.lang.Thread.run(Thread.java:619)[/code]When I searched for this error online, it seemed that people were getting this error when using Google Chrome, but they apparently did not experience any other adverse effects for the reports. I tried this under both Chrome and IE8, and the result is the same. We are experiencing this in a third-party product that has Jasperserver Pro 4.5.0 integrated into it, but I am am reproducing this in stock Jasperserver CP 4.5.0 as well (trying to isolate if its the third-party product or Jasperserver itself causing the issue). I am running this under a Windows Server 2008 R2 virtual machine. I've attached the jrxml file for the report, which was created with iReport Designer. Any ideas are greatly appreciated!

I'm new to JasperReports and am using iReport Designer 4.5.0 to play around with how to generate charts. In this case, I am trying to generate a line chart, which in the simple case, might show three lines,Lline1, Line2 and Line3, where line1 and 2 are independant data, and Line3 is perhaps some combination of the two [e.g. an average such as (Line1+Line2)/2)]. I've been trying to familiarize myself with what kind of datasets are required for the charts, and as far as I've found so far, it appears that to accomplish the scenario described above, my database query would at a minimum be required to return three columns of data: Category Line1 Value Line2 Value(Then I can calculate Line3 in a variable, or on the fly in the chart value field). However, due to the nature of my data, this requires me to do multiple joins on the table in order to get Line1 and Line2 data to be two adjacent columns. I'm concerned that this may get out of hand if I need to work with more and more Lines. In fact, in my original data has columns more like this: Category LineNumber ValueHowever, I couldn't seem to get the reporting tool to show two different trend lines based on a dataset like this? Is there a way to do chart based on this type of data?