Virtualize Enable SSL Proxy
I developed an Android app that connects to a node.js server in the cloud, I've generated a self signed certificate and I have already tested the SSL connection between the app and the server, it works perfectly. Now I'd like to deploy a Virtualize proxy between them, I generated a keystore.p12 from my private key and certificate and setup a http listener to use the .p12 file:
So far so good.
The problem happens when I setup my proxy connection with the http listener:
When I try to deploy the proxy this error occurs:
Does anyone know what this is about?
Comments
-
I generated a keystore.p12 from my private key and certificate and setup a http listener to use the .p12 file
The "does not identify a key entry" suggests the private key is missing, like maybe the .p12 file only has the certificate and not the key pair.
1 -
The "does not identify a key entry" suggests the private key is missing, like maybe the .p12 file only has the certificate and not the key pair.
Which would be quite strange, considering I can extract the private key from the .p12 file using openssl. Could the keystore password protecting the file be causing this? i.e.:
When using this command:
openssl pkcs12 -info -in keystore.p12I'm prompted a screen where I have to input 3 times the keystore password, once for the certificate:
Twice for the private key:
FYI this is the same password I'm using for the port settings.
0 -
It may be an issue with how you build the p12 file. Requirements are the same as what you see here for Apache Tomcat:
https://tomcat.apache.org/tomcat-8.5-doc/ssl-howto.html#Prepare_the_Certificate_Keystore0 -
I'm using a self signed certificate to create the keystore, so basically:
openssl pkcs12 -export -out keystore.p12 -inkey private.key -in certificate.crt
It is generating fine apparently. Not sure what's the problem.0 -
I'd recommend contacting Parasoft support or try posting this question on the Virtualize forum instead since different people monitor that one (this is SOAtest forum).
1 -