anmeldezeug

Is it possible to change the default TLS version for an HTTPS connection to a jasper server in Jaspersoft Studio 6.3? I installed JDK 1.7 where per default it should NOT be TLSv1.2 but the output from wireshark still shows TLS 1.2 during the Client Hello. I also tried adding the following to Jaspersoft.ini -Dhttps.protocols=TLSv1,TLSv1.1 With no results. Any suggestions?

Installing the Certificate into the keystore does not help either. http://community.jaspersoft.com/wiki/using-ssl-certificate-jaspersoft-studio-55

Ok same problem on all the major JAVA SDK's I also found that as soon when you enter a https URL, a lock icon appear next to the URL field. When I click it (it says "view certificate") I directly get the above mentioned error message. So somehow, Jasper Studio can't read the certificate of the server.

Thanks I will try out different JDK's as well since I don't have access to the server directly

Nobody? I tried looking for the error message, but so far I didn't find anything javax.net.ssl.SSLException: Received fatal alert: close_notify[/code]

I am running a Jasper Server Version on 6.3.0 and Jaspersoft Studio 6.3.0 I am using the following port in the server.xml of the Jasper Server: <Connector port="7000" URIEncoding="UTF-8" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" scheme="https" proxyPort="443" />[/code]The Jasper Server can be reached through the browser via https://remoteIP:443/jasperserver However when I am trying to connect to the Server through Jaspersoft Studio on https://remoteIP:443/jasperserver with username and password I get the following error message: AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: javax.net.ssl.SSLException: Received fatal alert: close_notify faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}stackTrace:javax.net.ssl.SSLException: Received fatal alert: close_notifyat sun.security.ssl.Alerts.getSSLException(Alerts.java:208)at sun.security.ssl.Alerts.getSSLException(Alerts.java:154)at sun.security.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:2023)at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1125)at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:290)at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:259)at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125)at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:319)at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)at org.apache.http.client.fluent.Executor.execute(Executor.java:206)at com.jaspersoft.ireport.jasperserver.ws.http.JSSCommonsHTTPSender.invoke(JSSCommonsHTTPSender.java:229)at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)at org.apache.axis.client.Call.invokeEngine(Call.java:2784)at org.apache.axis.client.Call.invoke(Call.java:2767)at org.apache.axis.client.Call.invoke(Call.java:2443)at org.apache.axis.client.Call.invoke(Call.java:2366)at org.apache.axis.client.Call.invoke(Call.java:1812)at com.jaspersoft.ireport.jasperserver.ws.RepositorySoapBindingStub.list(RepositorySoapBindingStub.java:336)at com.jaspersoft.ireport.jasperserver.ws.WSClient.getVersion(WSClient.java:158)at com.jaspersoft.studio.server.protocol.soap.SoapConnection.getServerInfo(SoapConnection.java:113)at com.jaspersoft.studio.server.protocol.soap.SoapConnection.connect(SoapConnection.java:154)at com.jaspersoft.studio.server.protocol.ProxyConnection.connect(ProxyConnection.java:110)at com.jaspersoft.studio.server.WSClientHelper.checkConnection(WSClientHelper.java:100)at com.jaspersoft.studio.server.wizard.ServerProfileWizard.connect(ServerProfileWizard.java:102)at com.jaspersoft.studio.server.wizard.ServerProfileWizard.access$1(ServerProfileWizard.java:97)at com.jaspersoft.studio.server.wizard.ServerProfileWizard$2.run(ServerProfileWizard.java:76)at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) {http://xml.apache.org/axis/}hostname:DV008RJC javax.net.ssl.SSLException: Received fatal alert: close_notifyat org.apache.axis.AxisFault.makeFault(AxisFault.java:101)at com.jaspersoft.ireport.jasperserver.ws.http.JSSCommonsHTTPSender.invoke(JSSCommonsHTTPSender.java:298)at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)at org.apache.axis.client.Call.invokeEngine(Call.java:2784)at org.apache.axis.client.Call.invoke(Call.java:2767)at org.apache.axis.client.Call.invoke(Call.java:2443)at org.apache.axis.client.Call.invoke(Call.java:2366)at org.apache.axis.client.Call.invoke(Call.java:1812)at com.jaspersoft.ireport.jasperserver.ws.RepositorySoapBindingStub.list(RepositorySoapBindingStub.java:336)at com.jaspersoft.ireport.jasperserver.ws.WSClient.getVersion(WSClient.java:158)at com.jaspersoft.studio.server.protocol.soap.SoapConnection.getServerInfo(SoapConnection.java:113)at com.jaspersoft.studio.server.protocol.soap.SoapConnection.connect(SoapConnection.java:154)at com.jaspersoft.studio.server.protocol.ProxyConnection.connect(ProxyConnection.java:110)at com.jaspersoft.studio.server.WSClientHelper.checkConnection(WSClientHelper.java:100)at com.jaspersoft.studio.server.wizard.ServerProfileWizard.connect(ServerProfileWizard.java:102)at com.jaspersoft.studio.server.wizard.ServerProfileWizard.access$1(ServerProfileWizard.java:97)at com.jaspersoft.studio.server.wizard.ServerProfileWizard$2.run(ServerProfileWizard.java:76)at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)Caused by: javax.net.ssl.SSLException: Received fatal alert: close_notifyat sun.security.ssl.Alerts.getSSLException(Alerts.java:208)at sun.security.ssl.Alerts.getSSLException(Alerts.java:154)at sun.security.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:2023)at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1125)at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:290)at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:259)at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125)at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:319)at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)at org.apache.http.client.fluent.Executor.execute(Executor.java:206)at com.jaspersoft.ireport.jasperserver.ws.http.JSSCommonsHTTPSender.invoke(JSSCommonsHTTPSender.java:229)... 19 more

Ok, so apparantly this does not work with REST, but there is a workaround in the new versions of Jasper Server (I am using 6.3) as described here. So I created a new datasource with user attributes Host (required) {attribute('host','User')} etc. I created 2 users, one for production and one for development. For both users I created an attribute called "host" and the value of the host attribute is the server url for your database. You can then do the same for port, databasename, username and password. You can then test the connection to your database by logging in with each user account and hit "test connection" and if everything was entered correctly, the connection can be established.

http:/localhost:8080/jasperserver/rest_v2/reports/reports/example.pdf?PRINTED_BY=ME&DATASOURCE=DEV

I am working on a Jasper Server 5.2 and looking to upgrade it to 6.01. Currently, I am using a direct URL call to generate the xls version of a report with this URL: show url: http://localhost:8080/jasperserver52/report?_repName=integration/v_ab_20151/subfolder/report1&_repFormat=xls&_dataSource=integration&_repLocale=DE_de&_repEncoding=UTF-8&parameter1 The path (integration/v_ab_20151/subfolder/r) is an absolute path on the tomcat server. "report1" is a .jrxml-file with a couple of linked subreports (.jasper files). Is it possible to have such a call (with an absolute path) for Jasper 6.01? I know that it works with a "relative" path when you create the report in the web frontend, but since I do not have permissions to create the reports in the web frontend, I need to replace the files directly.

I am creating Jasper Reports with Jasper Studio 5.5.2 (I also tried 6.0). The published files (.jasper) are deployed on a Jasper Server Version 5.2 and the reports can then be downloaded via a web frontend in XLS-format. Somehow, the Preview from Jasper Studio (attached to the same database) shows different results than the server. Can I use a different Library to publish my files in Jasper Studio so it corresponds with the Jasper Server Version? Unfortunately, I do not have access to the Jasper Server (not even the logfiles) so make some direct comparisons.