Certificates

Infront Data Manager Connect has a "control channel" and a "data channel". Both are TCP/IP connections wrapped with TLS and served with the same certificates (two different certificates in total).

The channels can be viewed and checked here (whitelisted IP required):

https://certcheck.dmc-pri.infrontfinance.com/
https://certcheck.dmc-sec.infrontfinance.com/

Server certificate #1:

subject: CN=*.dmc-pri.infrontfinance.com start date: May 27 00:00:00 2020 GMT
expire date: May 27 23:59:59 2021 GMT
issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA

Server certificate #2:

subject: CN=*.dmc-sec.infrontfinance.com start date: May 27 00:00:00 2020 GMT
expire date: May 27 23:59:59 2021 GMT
issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA

Fingerprints

Please note that the "fingerprint" calculation of a certificate is not a standardised algorithm. We implemented a fingerprint calculation into the DMC Java client, which may differ from the fingerprint that a web browser or other clients will show you.

We calculate an SHA-256 hash of the public key of the certificate (not including the certificate chain). The fingerprint is then converted to a hexadecimal representation of that hash.

These fingerprints are calculated from the public key, therefore they will not change if the certificate is renewed. This is because we normally reuse the same certificate signing request (CSR). We will notify you if the fingerprints on our side changes change.

Fingerprints of our certificates:

*.dmc-pri.infrontfinance.com: e4:bd:8b:fe:cd:fc:d6:6e:05:07:46:b3:29:73:48:33:ee:6d:dd:62:a3:3c:f8:e1:fb:de:11:f3:72:bc:3b:f2
*.dmc-sec.infrontfinance.com: 17:a2:ac:1f:65:9a:ba:59:38:27:fb:03:0d:59:87:24:eb:ff:87:14:67:6c:48:9e:ae:96:8e:e2:78:8e:67:53