Closed Andrej-Velevski closed 1 year ago
Hello @Andrej-Velevski ,
sending a SOAP message to port 12122 will not work; this port is used by one of the protocol adapter components and does not use SOAP as a communication protocol.
You will need to create a server certificate and configure Apache HTTPD with this certificate. It is Apache HTTPD that handles the SSL handshake.
The authorization header you are setting is not needed; instead, you will have to use the client certificate for the organization used in your SOAP message.
Hello,
I'm trying to establish a secure connection to the tomcat web server and send a SetLightRequest. This works fine from SoapUI within the VM, however I'm having trouble doing this from outside the VM.
The issue is related to #277
I am trying to replicate the SetLightOn from this SoapUI request:
I have a basic console application that is sending a POST request with the exact data, however I get an SSL handshake failed error:
These are the headers I'm setting, some are automatically set like "Content-Length" in the library I'm using. It also uses OpenSSL which has worked for other APIs requiring a secure connection.
I'm not sure if the issue has something to do with the Authorization header (since I get the same issue if I remove it) or something with certificates.
If I try to use the port 12122 instead of 443 I get the following exception in the tomcat web server:
I've also tried using ReqBin where using the port 443 I get "Error sending request" and using the port 12122 I get "Request timeout".
Any help would be appreciated.
Thank you