Lack of secure connection for repository
I had asked via twitter awhile back if your URLhttp://smartbearsoftware.com/repository/maven2/ had an equivalent secure address. I was told no. I work at large company that utilizes many of your libraries. We would request that you buy a certificate and setup secure connection for downloads. As a bonus, it would be even better if every download had a file hash that we can compare against after downloading to make sure we received a legit copy. The first part of request wouldn't take much time at all, and will begin a great start at providing secure downloads of all your libraries. Thoughts Smartbear people? Thanks!Solved3.1KViews0likes3CommentsHow do I enable SSL in TestComplete
I am trying to enable SSL in TestComplete but I am stuck. Note: We are not using ReadyAPI nor are we using SOAPUI for generating our tests. Although I do have both working with SSL enabled. The direction of our development is through TestComplete and we are not using the ReadyAPI or Webservices module within TC. I am able to set up the aqHTTP authentication on each service but I am stuck and how to use and get access to the local Certificate. Suggestions or comments?2.2KViews0likes5CommentsMock Service security protocol control
In soapUI the security protocol can be controlled for client projects with an entry in the vmoptions config file E.G. -Dsoapui.https.protocols=SSLv3,TLSv1.2 However from my testing it looks like this option does not affect mock service projects.If there is currently a way tocontrol the protocol for mock service projects please let me know, if there isn't I will request it as a new feature. Thanks, Steve955Views0likes0CommentsHow to change the TLS version SoapUI uses for MQTT
Hi everyone, I am currently trying to get a "Receive MQTT Message"-TestStep to work which always runs into a timeout. After checking all URLs, ports and changing vmoptions to use TLS 1.2 I still had no success. I found an issue on Github that seems to describe a possible solution for my problem: https://github.com/eclipse/paho.mqtt.java/issues/309 Here the SocketFactory that is required for the MqttClient has been created with "TLSv1". According to the issuer of that ticket changing it to "TLSv1.2" fixed his problem. I took a look into the source code for the MQTT plugin by SmartBear (https://github.com/SmartBear/ready-mqtt-plugin/blob/master/src/main/java/com/smartbear/mqttsupport/connection/ssl/SSLCertsHelper.java) and noticed that "TLSv1" seems to be hardcoded: SSLContext context = SSLContext.getInstance("TLSv1"); Does anyone know if this means that MQTT will always use TLSv1 even if I changed my vmoptions to use TLSv1.2 ? I tried recompiling this plugin after changing TLS to "TLSv1.2" in the code but just replacing it does not seem to work as all testSteps (not only MQTT) are missing afterwards. Best regards Max732Views0likes0Comments