Thanks for the excelent description of the files and their relations for comunication. In our deployment the HPDM Server, MRC, Console, and Gateway are on the same system. So it's not that important for high security encryption between them. However, I am wondering how the clients fall into this. I know the Thin Clients use the customized certs in IIS for FTPS and the HPDM Embbeded HTTPS server for file transfer. What aboutn commnds from the HPDM server to the clients? I was thinking these would be encrypted with the HPDM Server cert. If so it would be nice to be able to replace it.
Is there any option for changing the default cipher suite or hash that is used for these auto generated certs? I would like to use SHA256 instead of MD5 and RSA 2048 instead of 1024.
Also on a nother not I followed the manual for making a CTL file and included the two CA certs from my organization in it. Our sub ordinate and root CA. These are used for the certs I used in IIS FTPS and the Embeded HTTPS server. However, running the test for thoes protocols for the MRC fails instantly when I have a CTL present. I initial was not aware of the HPDM and MRC certs that were auto generated not useing our CA. Shoud I add the auto generated selfsigned certs to the CTL as well?
Thanks!