Forum Discussion
Apologizing for not responding in a timely fashion to your earlier posting replies, but my soapUI instance and my soapUI Runner component are using the same soapUI settings file.
I too am able to use the soapUI Runner component that specifies a soapUI project that uses a standard HTTP endpoint, however, when specifying any/all soapUI projects that employ a secured HTTP endpoint (https), I generate the javax.net.ssl.SSLHandshakeException exception for each and every project/endpoint specified.
These same soapUI projects that employ secured HTTP endpoints, currently comprise our nightly regression, CI build verification and acceptance testing efforts. So, I know these soapUI projects and their contained secured endpoints are valid since they're executed many times daily.
I don't mean to "pile on".
I too am able to use the soapUI Runner component that specifies a soapUI project that uses a standard HTTP endpoint, however, when specifying any/all soapUI projects that employ a secured HTTP endpoint (https), I generate the javax.net.ssl.SSLHandshakeException exception for each and every project/endpoint specified.
These same soapUI projects that employ secured HTTP endpoints, currently comprise our nightly regression, CI build verification and acceptance testing efforts. So, I know these soapUI projects and their contained secured endpoints are valid since they're executed many times daily.
I don't mean to "pile on".
Related Content
- 8 years ago
Recent Discussions
- 6 hours ago