david_betterton

Think I worked it out, the ClientJdbcDataSource had a version of null, and the createOrUpdate because I wasn't reading the data source first the version was mismatching

I'm upgrading from 7.8.0 to 9.0.0. Because our production is completely containerized - we take this approach: Upgrade in the 7.8.0 postgres container to a new database export the resource using the cmdline export tool bring up a 9.0.0 postgres 12 database import the exported file from above When I try to update a data source I get this exception - what does it mean and how to fix it ? com.jaspersoft.jasperserver.jaxrs.client.core.exceptions.VersionNotMatchException: Update failed: versions not match at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) at com.jaspersoft.jasperserver.jaxrs.client.core.exceptions.handling.DefaultErrorHandler.handleBodyError(DefaultErrorHandler.java:94) at com.jaspersoft.jasperserver.jaxrs.client.core.exceptions.handling.DefaultErrorHandler.handleError(DefaultErrorHandler.java:66) at com.jaspersoft.jasperserver.jaxrs.client.core.JerseyRequest.executeRequest(JerseyRequest.java:217) at com.jaspersoft.jasperserver.jaxrs.client.core.JerseyRequest.put(JerseyRequest.java:159) at com.jaspersoft.jasperserver.jaxrs.client.apiadapters.resources.SingleResourceAdapter.createOrUpdate(SingleResourceAdapter.java:152)

This seemed to get us most of the way Manually added remoteIpValve settings in Tomcat on Jasperserver Container (the jasper server image needs to be recreated with these settings in place) <Valve className=“org.apache.catalina.valves.RemoteIpValve” remoteIpHeader=“x-forwarded-for” proxiesHeader=“x-forwarded-by” protocolHeader=“x-forwarded-proto” />

Setup: In Azure with Azure application gateway - SSL is terminated at the gatewayApplication is using visualize.jsvisualize is downloaded via https request on browserhttps://<domain>/jasperserver-pro/client/visualize.js?1601645389all the needed components are downoaded successfully via https, eghttps://<domain>/jasperserver-pro/runtime/AC91FCAB/optimized-scripts/runtime_dependencies/bi-report/src/bi/report/schema/ReportSearch.jsonauth request is made and returns 200https://<domain>/jasperserver-pro/rest_v2/settings/auththe next request captured by the browser causes a redirect to HTTPrequest - https://<domain>/jasperserver-pro/?pp=gd+HOSrq/DNYTutyiZzI3wCPyN8jNM/+UmD7JDJQ+5968b6eVpxpdtHpruU5d1Qlo793ayZiGXVf4apUI3Tp7ZIGLQwam78cfk+xw4x6aEs=Location response header - http://<domain>/jasperserver-pro/scripts/visualize/auth/loginSuccess.jsonredirect is blocked by the browser as insecure - mixed contentMixed Content: The page at 'https://<domain>/ams-web/Kernel/w_main.jsp?AA_SID=5fc22511-10ef-4a42-b6f1-855f48b28447' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://<domain>/jasperserver-pro/scripts/visualize/auth/loginSuccess.json'. This request has been blocked; the content must be served over HTTPS.This seems like a bug to me - the jasperserver code appears to be issuing a redirect in the wrong protocol The jaspersoft Tomcat server does not know the actual domain - it's running as a kubernetes service behind the Azure Application Gateway Is there a way to force jasperserver to redirect correctly ?