Forum Discussion
devnull
10 years agoNew Contributor
The issue has been solved.
The server was accepting only TLS 1.2, while Soap UI was using TLS 1.0.
- gungwald9 years agoNew Contributor
I can't find a way to tell soapUI to use TLS 1.2. So how do you actually fix the problem?
- devnull9 years agoNew Contributor
Indeed the solution was to set the application server to accept also connections using TLS 1.0, so I passed this parameter at the application server startup:
-Dweblogic.security.SSL.minimumProtocolVersion=TLSv1.0
(so the solution was solved on the other side, not on Soap UI)
Regards,
Edit: in my case the application to which I was talking, was deployed on a Weblogic server on which I had the possibility to change the startup System properties.
- nmrao9 years agoChampion Level 3Of course, you can also set in the soapui to use different version, just a java system property.
Add this to java_opts of soapui.bat file
-Dsoapui.https.protocols=SSLv3,TLSv1.2
See this thread here
https://community.smartbear.com/t5/SoapUI-Open-Source/How-to-enable-TLS-1-2-in-SoapUI/td-p/96239
Related Content
- 5 years ago
- 5 years ago
Recent Discussions
- 12 days ago