Hi,
We are using the SOAP ServerCommandService with HTTPS - which works well (we followed the default instructions to install a CA and a Server Certificate). The certificate is also used for the REST APIs and the WebSocket Event API.
However, it seems the SOAP RecorderCommandService is not supporting HTTPS, at least I could not configure it properly.
Can you tell me if the RecorderCommandService is supporting HTTPS at all?
Any help is greatly appreciated!
Hi,
It sure does. Configured using Server Configurator on the machine running the recording server.
Great! Can you point me to a sample application? I was searching through the GitHub repos and did not find anything related to the RecorderCommandService and HTTPS.
I was wondering, since HTTPS is explicitly mentioned at the SOAP ServerCommandService (see https://doc.developer.milestonesys.com/mipsdk/index.html?base=ServerSOAPhelp%2Findex.html&tree=tree_3.html) but not at the SOAP RecorderCommandService (see https://doc.developer.milestonesys.com/mipsdk/index.html?base=RecorderSOAPhelp%2Findex.html&tree=tree_3.html)
Hi @Rie Kiuchi (Milestone Systems) ,
I enabled the certificate in the Server Configurator. I have the same problem as in this post: https://developer.milestonesys.com/s/question/0D5bH00000AL6qrSAD/soap-tls, i.e. when connecting to the RecorderCommandService I get the the following exception:
System.ServiceModel.Security.SecurityNegotiationException: Could not establish trust relationship for the SSL/TLS secure channel with authority '<ip>:7563'
The certificate is used for all encryption. The communication with the ServerCommandService works as expected.
Can you please provide a code sample or example application where the RecorderCommandService is used in conjunction with HTTPS?
I also observed (as in the linked post) that the preview of the camera stream in management client is unavailable.
Also, I think my problem is related to this post: https://developer.milestonesys.com/s/question/0D5bH00000AL6qrSAD/soap-tls
One hunch, if the Recording Server (RS) is a separate server, not shared with the Management Server (MS), then the certificate might work for the MS but not for the RS.
If my hunch doesn’t lead you to a solution, then please ask the question on our Support Community, perhaps emphasizing the observation about the Management Client. I suspect the people working with general support has more experience trouble-shooting encryption / certificate usage.
I think that the observation in the Management Server Client seems to be a side effect of our problem.
Both servers are on the same machine sharing the same ip. Also everything works with using HTTP, i.e. we communicate with the REST API, the WebSocketApi and the SOAP Apis using the same ip address.
With the ServerCommandService communication with HTTPS works as well. It is just the RecorderCommandService which does not.
I posted a related question in the support forum.
Using the support we could identify and resolve the problem - RecorcerCommandService does support https.
Just make sure that the certificate you are using can be accessed by the user running the milestone services. (This has to be checked in the certificate manager on windows).