{"id":287,"date":"2013-12-18T02:10:23","date_gmt":"2013-12-18T02:10:23","guid":{"rendered":"http:\/\/www.itcrumbs.com\/?p=287"},"modified":"2019-02-07T04:39:45","modified_gmt":"2019-02-07T04:39:45","slug":"exporting-and-importing-ssl-certificate-chains-in-iis-and-tmg","status":"publish","type":"post","link":"http:\/\/www.itcrumbs.com\/?p=287","title":{"rendered":"Exporting and Importing SSL certificate chains in IIS and TMG"},"content":{"rendered":"

http:\/\/fixmyitsystem.com\/2011\/02\/exporting-and-importing-ssl-certificate.html<\/a><\/p>\n

My personal belief nowadays is that any business or corporate application should exclusively be published in HTTPS because really HTTP is just plain text.  Usernames and password, all data etc, all going in plain intercept-able, sniff-able plain text.
This was traditionally offset by the performance penalty associated with the encryption and decryption process.  But that has not been a factor since CPUs hit GHz speeds.  As for the "perceived" size increase for adding SSL encryption it can be called minuscule, and that has not been a factor since the end of the  28,800 modem days.
To publish an Application in TMG with HTTPS you need the certificate to attach to your listener.
Exporting Certificates<\/b>
Exporting and importing certificates is best done from the MMC console.
Typically a certificate is created on an IIS machine by requesting a certificate, submitting the certificate request and receiving the certificate and compling the certificate request process.  The certificate can then be exported.<\/p>\n