Need to install an SSL certificate for JasperServer plug-in to work?

[cbarlow3]

We recently changed our product so that it can only be reached through SSL with an https:// URL on port 8443 instead of an http:// URL on port 8080.  We're using a self-signed SSL certificate, and it's working fine for our main application.  I also don't have problems with iReport running previews against our database on the AIX server, because the DB2 database connection is on port 50000.

BUT...I've come to rely heavily on the convenience of the Repository Navigator pane provided by the JasperServer plug-in, and that requires that I configure a JasperServer URL to the repository, which used to be http://www.corelationlocal.com:8080/jasperserver-pro/services/repository.  Before I remembered to change anything, I got the following error:

Error:

; nested exception is:

Java.net.ConnectionException: Connection refused: connect

 

 

Not a big surprise, really.  When I try to change only the http to https and the 8080 to 8443, I get the following error:

Error:

; nexted exception is:

Javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.

So I assume that JasperSoft has a problem with the self-signed SSL certificate, and I have no idea what my best course of action is--I have no experience with SSL certificates, by the way.  Is there something I can do on our AIX server to make JaspserSoft/Java happy with our self-signed SSL certificate (if so, how do I do it?) and/or are there reasonably simple steps I can follow to get a non-self-signed SSL certificate installed that will take care of this?

Carl

[cbarlow3]

I'm still unable to use iReport to install reports ever since we switched to an SSL connection.  I can use it to author, but then I have to go into JasperReports Server to install.  The iReport JasperServer plug-in is more convenient when I'm trying to copy a report from one organization to another (although I still have to go in and change the data source and relink any input controls that are organization specific--like those that use a query which in turn use an organization-specific data source).  Any advice?

Post Edited by cbarlow3 at 11/23/2011 16:07