Forum Discussion
boschhi
11 years agoVisitor
Came across the same problem with SoapUI 4.6.4, an https-JIRA 4.4.3 and a company proxy configured.
JIRA uses a CA-signed(!) certificate and if the signing certificate is not available in SoapUI's cacerts, it fails to login to JIRA.
Solution was:
- export the signing certificate from my Firefox certificate store into a file
- add the certificate to SoapUI's cacerts file with keytool -import -alias <alias> -file <cer> -keystore cacerts -storepass changeit
<alias> must be a unique name in the cacerts file (the keystore), but keytool warn you, if you try to overwrite. I chose the same name as my firefox displays it.
<cer> is the file where the export from Firefox has gone to.
SoapUI's cacerts file is in it installation path, on my Win7 machine in C:\Program Files\SoapUI-4.6.4\jre\lib\security
After having the certificate imported, I restarted SoapUI and then it was able to log me in to JIRA without any problems and with a proxy configured.
JIRA uses a CA-signed(!) certificate and if the signing certificate is not available in SoapUI's cacerts, it fails to login to JIRA.
Solution was:
- export the signing certificate from my Firefox certificate store into a file
- add the certificate to SoapUI's cacerts file with keytool -import -alias <alias> -file <cer> -keystore cacerts -storepass changeit
<alias> must be a unique name in the cacerts file (the keystore), but keytool warn you, if you try to overwrite. I chose the same name as my firefox displays it.
<cer> is the file where the export from Firefox has gone to.
SoapUI's cacerts file is in it installation path, on my Win7 machine in C:\Program Files\SoapUI-4.6.4\jre\lib\security
After having the certificate imported, I restarted SoapUI and then it was able to log me in to JIRA without any problems and with a proxy configured.
Related Content
Recent Discussions
- 4 minutes agoLukaszK