Forum Discussion

dfeagin's avatar
New Contributor
2 years ago

Trouble Connecting to IIS Site/Service Configured with HTTPS Binding Using SNI

We are moving our sites over to HTTPS and we are running into an issue where we cannot get SoapUI to connect when we provide the SOAP WSDL URL. Example of our URL would be:

when this is accessed over HTTP it fetches the WSDL just fine and everything works as expected. Also, when we configure the IIS site without SNI we can get the SSL tunnel established and everything works fine as well (we did have to import our CA certs into cacerts). But as soon as we configure the site using SNI everything comes to a halt. From Wireshark captures it would appear that when the initial call is made to the server the site name is not passed to the server for it match up with the SNI configured in IIS.

From what I have read by default SoapUI supports SNI and has for quite some time but it doesn't appear to be happening.

I should also note that my version of SoapUI is 5.7.0 and this is what my .vmoptions file looks like (when I upgraded I had it upgrade the version that was already in place that is why you will see references to 5.5.0 below):
-Dsoapui.home=C:\Program Files\SmartBear\SoapUI-5.5.0/bin
-Dsoapui.ext.libraries=C:\Program Files\SmartBear\SoapUI-5.5.0/bin/ext
-Dsoapui.ext.listeners=C:\Program Files\SmartBear\SoapUI-5.5.0/bin/listeners
-Dsoapui.ext.actions=C:\Program Files\SmartBear\SoapUI-5.5.0/bin/actions
-Dwsi.dir=C:\Program Files\SmartBear\SoapUI-5.5.0/wsi-test-tools
-Djava.library.path=C:\Program Files\SmartBear\SoapUI-5.5.0/bin



No RepliesBe the first to reply