We are posting this to inform you about the ability to encrypt all communication to and from the XProtect Recording Server with the upcoming release of XProtect 2019 R1, which can potentially break backwards compatibility for certain protocol and component integrations.
This information is relevant for everyone that:
• Has integrated with the Milestone XProtect Recording Server using protocols or components.
• Will integrate with XProtect 2019 R1 at customer sites that choose to use encryption for the XProtect Recording Servers.
The encryption technology uses certificates installed on the Windows operating system. Every XProtect Recording Server and all client computers communicating with the recording server assume that the certificates are installed on the Windows operating system. The encryption technique is using standard SSL/TLS and will per default be enabled the XProtect 2019 R1.
What you need to do now if you want your integration to continue to work on systems using the encryption capability:
-
For current integrations built with MIP SDK components, it will require a re-build of the integration with the 2019 R1 MIP SDK. No further code change is required.
-
For current protocol integrations designed to communicate directly with the XProtect Recording Server, it will require support for SSL/TLS. And on the machines executing the integration, the customer needs to register a valid certificate.
Encryption can be disabled/enabled for a Recorder in the TrayManager for the Recorder.