Hi Vanessa,
Technically, this is not a bug. It seems to be caused by changes in the Java runtime that SoapUI uses. SoapUI 4.0 used a rather early version of Java 1.6. In a late update of the JRE, Sun plugged some security vulnerabilities, which meant that certain SSL interactions began to be seen as invalid.
The odd thing is it works for most people, and we haven't been able to identify what factors in the environment causes it to fail for others. However, the fact that SoapUI throws an error could be a sign that something is wrong with your proxy or other infrastructure.
We will continue to investigate it, and I will add your comment to the issue in our tracking system.
Kind regards,
Manne
