SSL enabled mock service
Hello, I am trying to create a mock service and then send request messages to this mock service from within SoapUI. When these request messages are send over http everything works well, but when I ...
Forum Discussion
I've been working on an SSL enabled mock service, but have been seeing a problem that looks like a soapUI bug. When I start the SSL enabled mock service, it sometimes uses HTTP instead of HTTPS. The problem is intermittent, and I haven't yet found a good way to predict whether soapUI (or Jetty?) will use HTTP or HTTPS.
To set up the mock service, I used OpenSSL to generate a host certificate and self-signed CA certificate, and to sign the host certificate using my CA certificate. I used keytool to create a JKS containing the public key portion of the CA certificate, and configured soapUI to use this as the truststore. To create a JKS for the host certificate, I first used OpenSSL to create a PKCS12 file containing the signed host certificate and private key, then used Jetty's PKCS12Import program to create a JKS keystore from the PKCS12 file. (Importantly, the common name of the host certificate matches the fully qualified domain name of the machine running the SSL enabled mock service.)
Depending on how the "Leave MockEngine running when stopping MockServices" preference setting is configured, it is sometimes necessary to restart soapUI (often more than once) to have it switch from HTTP to HTTPS when running the MockService.
Because the soapUI interface doesn't indicate whether a service is using HTTP or HTTPS (i.e. SSL), I've been using Firefox to manually check whether the server responds correctly to http://localhost:8443/ or https://localhost:8443/. It would be nice if soapUI could write a message to the jetty log that indicates whether it is using HTTP or HTTPS for a given MockService.
In soapUI preferences, I have the mock port for SSL set to 8443, so it seems wrong that soapUI/Jetty sometimes runs the service on that port without using SSL.
I've seen this happen in versions 2.5.1 and 3.0.1 of soapUI. Haven't tried 3.5 yet.
To set up the mock service, I used OpenSSL to generate a host certificate and self-signed CA certificate, and to sign the host certificate using my CA certificate. I used keytool to create a JKS containing the public key portion of the CA certificate, and configured soapUI to use this as the truststore. To create a JKS for the host certificate, I first used OpenSSL to create a PKCS12 file containing the signed host certificate and private key, then used Jetty's PKCS12Import program to create a JKS keystore from the PKCS12 file. (Importantly, the common name of the host certificate matches the fully qualified domain name of the machine running the SSL enabled mock service.)
Depending on how the "Leave MockEngine running when stopping MockServices" preference setting is configured, it is sometimes necessary to restart soapUI (often more than once) to have it switch from HTTP to HTTPS when running the MockService.
Because the soapUI interface doesn't indicate whether a service is using HTTP or HTTPS (i.e. SSL), I've been using Firefox to manually check whether the server responds correctly to http://localhost:8443/ or https://localhost:8443/. It would be nice if soapUI could write a message to the jetty log that indicates whether it is using HTTP or HTTPS for a given MockService.
In soapUI preferences, I have the mock port for SSL set to 8443, so it seems wrong that soapUI/Jetty sometimes runs the service on that port without using SSL.
I've seen this happen in versions 2.5.1 and 3.0.1 of soapUI. Haven't tried 3.5 yet.
