This sections describes the configuration files required to initialize the Infront Data Manager Connect client libraries.
The following are mandatory parameters that you will be provided with:
- username - user ID to login
- password - password for your login for authentication
- primary URL - Primary URL of our backend system
- secondary URL - Secondary URL of our backend system
App.Config
This is an example of the configuration file included in the Data Manager Connect .Net Version 4.1 - Distribution, in the "DataManagerConnect.Sample" folder:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.6.1" />
</startup>
<!-- Data Manager Connect client configuration -->
<appSettings>
<add key="DMC.UserId" value="--please insert your ID here--" />
<add key="DMC.Password" value="--please insert your serial here--" />
<add key="DMC.PrimaryUrl" value="https://--please insert your primary URL--" />
<add key="DMC.SecondaryUrl" value="https://--please inset your secondary URL--" />
</appSettings>
</configuration>
Proxy server
The Data Manager Connect (DMC) client is capable of using proxy servers for HTTP/HTTPS requests (since version 4.0.3) Following information is required
- Proxy host
- Proxy port
- Authentication required?
- Username (if required)
- Password (if required)
Please note:
- Streaming data via proxy server is NOT supported!
- HTTPS in combination with basic authentication is not supported! If you need to use a proxy server with basic authentication, please contact our customer service.
You have to add following entries to your configuration file
<add key="DMC.Proxy.Enabled" value="true" />
<add key="DMC.Proxy.Host" value="proxy.company.tld" />
<add key="DMC.Proxy.Port" value="8080" />
<!-- AuthenticationType is either None or Basic
<add key="DMC.Proxy.AuthenticationType" value="None" />
<!-- Credentials for Basic Authentication (if set before) -->
<add key="DMC.Proxy.User" value="please insert proxy username" />
<add key="DMC.Proxy.Password" value="please insert proxy userpassword" />
Certificate verification
By default all certificates for HTTPS oder TLS connections are verified (validity of the certificate is checked and also if the CA of certificate is trusted.) If the certificate can not be validated, the connection will be refused. In certain circumstances it may be wanted to override/change this behaviour. This can be done via configuration.
Please note that the fingerprint is a SHA-256 hash of the public key of the certificate, not the certificate chain. So it can't be compared with fingerprints displayed in your web browser for example.
Following parameters are available to configure certificate validation
- Disable certificate verification (is enabled by default)
- Specificy fingerprint for primary certificate (to override builtin default value)
- Specific fingerprint for secondary certificate (to override builtin default value)
<!-- Certificate configuration -->
<add key="DMC.DisableCertificateCheck" value="false" />
<!-- Fingerprint for *.dmc-pri.infrontfinance.com -->
<add key="DMC.PrimaryUrlFingerprint" value="2c:fa:a5:0b:23:f4:9d:62:d1:f9:3a:72:f2:43:f2:67:20:4b:df:eb:c0:64:2a:e1:94:9d:35:30:7a:a2:65:f8" />
<!-- Fingerprint for *.dmc-sec.infrontfinance.com -->
<add key="DMC.SecondaryUrlFingerprint" value="c5:de:c3:1c:69:50:66:a3:1c:9a:fd:ba:b9:c9:81:58:55:91:9a:73:3a:d4:eb:5c:49:75:95:de:b9:d9:7d:03" />
Other parameters
Following enhanced configuration parameters are available. Please use them carefully and only if you are told to configure them. The default values should be sufficient in almost all cases.
- connect timeout value (in ms, default 60000)
- read timeout value (in ms, default 60000)
<!-- request timeout configuration (optional)-->
<add key="DMC.RequestConnectionTimeout" value="60000" />
<add key="DMC.RequestReadTimeout" value="60000" />