Requirements
DMC client
First download the latest client of the Infront Data Manager Connect (DMC) from the Protected Area on our website. The first version to support encrypted streaming data is version 4.1.0. If you are upgrading from an already existing implementation, replace the JAR files with the latest versions provided in the download and make sure they are in the corresponding path for your project. The new libraries are fully backwards compatible to previous 4.0.x versions of the client so you don’t have to change anything in your implementation to make use of encryption.
To enable encryption of streaming data, you do not need to change the configuration because the default is already set to use encryption.
Java
Due to high security requirements, we make use of strong encryption with only the most secure ciphers which are only supported by up-to-date versions of the Java JDK/JRE. We support the two latest Java LTS (Long Term Support) versions 8 and 11. The minimum required Java versions are:
- Java 8.0.274
- Java 11.0.6
We test our distributed clients very thoroughly. For this purpose, we always take the latest Java 8 and 11 version. To get the best experience on your side and minimise the risk of security issues, we recommend you to also update regularly.
To find the Java version of your installation, go to your favourite CLI (command-line interface) and type java -version . Older Java versions are not supported.
As a matter of principle, known security gaps should be closed as soon as possible. Therefore, we recommend keeping the Java Runtime Environment (JRE) and the Java Development Kit (JDK) up to date as much as possible. This should be done within the framework of a centralised and coordinated patch management, which takes into account fundamental security aspects such as the trustworthiness of the installation source. Please note that you are responsible for taking care of an adequate patch management of your JRE/JDK to ensure security overall and TLS security in particular.
If you are using our DMC client with an older version of Java, you will most probably not be able to establish a TLS-enabled connection at all. Any connection using TLS version before 1.2 (TLS 1.0, TLS 1.1, SSLv3) will be rejected by our servers.
.NET
Due to high security requirements, we make use of strong encryption with only the most secure ciphers which are only supported by up-to-date versions of the .NET framework. We support .NET 4.7.2 and later versions.
We test our distributed clients very thoroughly. We always use the latest .NET framework for this. To get the best experience on your side and minimise the risk of security issues, we recommend you to also update your .NET version regularly. The update is carried out via Windows Updates.
As a matter of principle, known security gaps should be closed as soon as possible. Therefore, we recommend keeping the .NET environment up to date whenever possible. This should be done within the framework of a centralised and coordinated patch management, which takes into account fundamental security aspects such as the trustworthiness of the installation source. Please note that you are responsible for taking care of an adequate patch management of your .NET framework to ensure security overall and TLS security in particular.
If you are using our DMC client with an older .NET version, you will most probably not be able to establish a TLS-enabled connection at all. Any connection using TLS version before 1.2 (TLS 1.0, TLS 1.1, SSLv3) will be rejected by our servers.