Forum Discussion
11 years ago
I had exactly the same problem. Looks like the route-ca, that issued the server's ssl-certificate was not contained in the "cacerts" that comes with Soapui.
My solution was to import the server's ssl-certificate into cacerts like this:
1) open a http session to the server and download the certificate (eg cer - file)
2) switch to the jre\lib\security - path of soapuim, make a backup of cacerts.
3) Import the cer-File to the cacerts-File like this:
keytool -import -alias <alias> -file <cer> -keystore cacerts -storepass changeit
where <alias> is the hostname (suchandso.com) and
<cer> is the filepath to the cer-file.
I have no idea why this is only an issue when working with a proxy: I didn't have any problem while not working with a proxy.
Hope this is helpful to anyone..
bth: we have been using Soupui 4.6.4.
My solution was to import the server's ssl-certificate into cacerts like this:
1) open a http session to the server and download the certificate (eg cer - file)
2) switch to the jre\lib\security - path of soapuim, make a backup of cacerts.
3) Import the cer-File to the cacerts-File like this:
keytool -import -alias <alias> -file <cer> -keystore cacerts -storepass changeit
where <alias> is the hostname (suchandso.com) and
<cer> is the filepath to the cer-file.
I have no idea why this is only an issue when working with a proxy: I didn't have any problem while not working with a proxy.
Hope this is helpful to anyone..
bth: we have been using Soupui 4.6.4.