In the Signature section select Certificate signing and clear all other options. Select the Extensions tab, highlight Key Usage, and click Edit. On the General tab provide a descriptive name for the certificate template, review and optionally adjust the Validity period if required.
When the Certificate Templates Console opens, right-click the Subordinate Certification Authority template and choose Duplicate Template. Begin by opening the Certification Authority management console, highlighting Certificate Templates and choosing Manage. We’ll need to configure and deploy a certificate template that TMG can use to create its own certificates to issue to users on behalf of public web sites. Preparing the Certificate Templateīefore we begin configuring TMG for HTTPS inspection, we must first prepare our internal PKI Certificate Authority (CA). This month I’ll demonstrate how to configure TMG HTTPS inspection using an internal Windows Server 2008 R2 Enterprise Public Key Infrastructure (PKI) with support for CNG. I also demonstrated how to resolve this shortcoming by using a special script developed by Microsoft to enable support for CNG certificates when using a self-signed HTTPS inspection certificate on the TMG firewall. One of those challenges for TMG today is handling SSL/TLS protected web sites that use Cryptographic Next Generation (CNG) Suite-B cryptography. In last month’s article I described in detail the benefits and challenges associated with HTTPS inspection. The HTTPS inspection feature of Forefront Threat Management Gateway (TMG) 2010 is arguably the single most powerful tool the TMG platform provides for protecting clients accessing the public Internet. If you would like to be notified when Richard Hicks releases the next part of this article series please sign up to the Real time article update newsletter.
0 kommentar(er)
