11 KiB
title, description, ms.date, appliesto, ms.topic
| title | description | ms.date | appliesto | ms.topic | |
|---|---|---|---|---|---|
| Configure Hybrid Azure AD joined key trust Windows Hello for Business | Configuring Hybrid key trust Windows Hello for Business - Public Key Infrastructure (PKI) | 04/30/2021 |
|
article |
Configure Hybrid Azure AD joined Windows Hello for Business: Public Key Infrastructure
[!INCLUDE hello-hybrid-key-trust]
Windows Hello for Business deployments rely on certificates. Hybrid deployments use publicly issued server authentication certificates to validate the name of the server to which they are connecting and to encrypt the data that flows them and the client computer.
All deployments use enterprise issued certificates for domain controllers as a root of trust.
Certificate Templates
This section has you configure certificate templates on your Windows Server 2012 or later issuing certificate authority.
Domain Controller certificate template
Clients need to trust domain controllers and the best way to do this is to ensure each domain controller has a Kerberos Authentication certificate. Installing a certificate on the domain controller enables the Key Distribution Center (KDC) to prove its identity to other members of the domain. This provides clients a root of trust external to the domain - namely the enterprise certificate authority.
Domain controllers automatically request a domain controller certificate (if published) when they discover an enterprise certificate authority is added to Active Directory. However, certificates based on the Domain Controller and Domain Controller Authentication certificate templates do not include the KDC Authentication object identifier (OID), which was later added to the Kerberos RFC. Inclusion of the KDC Authentication OID in domain controller certificate is not required for key trust authentication from Hybrid Azure AD-joined devices. The OID is required for enabling authentication with Windows Hello for Business to on-premises resources by Azure AD-joined devices. The steps below to update the domain controller certificate to include the KDC Authentication OID may be skipped if you only have Hybrid Azure AD Joined devices in your environment, but we recommend completing these steps if you are considering adding Azure AD-joined devices to your environment in the future.
By default, the Active Directory Certificate Authority provides and publishes the Kerberos Authentication certificate template. However, the cryptography configuration included in the provided template is based on older and less performant cryptography APIs. To ensure domain controllers request the proper certificate with the best available cryptography, use the Kerberos Authentication certificate template a baseline to create an updated domain controller certificate template.
Create a Domain Controller Authentication (Kerberos) Certificate Template
Sign-in a certificate authority or management workstations with Domain Admin equivalent credentials.
- Open the Certificate Authority management console.
- Right-click Certificate Templates and click Manage.
- In the Certificate Template Console, right-click the Kerberos Authentication template in the details pane and click Duplicate Template.
- On the Compatibility tab, clear the Show resulting changes check box. Select Windows Server 2008 R2 from the Certification Authority list. Select Windows 7.Server 2008 R2 from the Certification Recipient list.
- On the General tab, type Domain Controller Authentication (Kerberos) in Template display name. Adjust the validity and renewal period to meet your enterprise's needs.
Note
If you use different template names, you'll need to remember and substitute these names in different portions of the lab.
- On the Subject Name tab, select the Build from this Active Directory information button if it is not already selected. Select None from the Subject name format list. Select DNS name from the Include this information in alternate subject list. Clear all other items.
- On the Cryptography tab, select Key Storage Provider from the Provider Category list. Select RSA from the Algorithm name list. Type 2048 in the Minimum key size text box. Select SHA256 from the Request hash list. Click OK.
- Close the console.
Note
Don't confuse the Request hash algorithm with the hash argorithm of the certificate.
Configure Certificate Superseding for the Domain Controller Authentication (Kerberos) Certificate Template
Many domain controllers may have an existing domain controller certificate. The Active Directory Certificate Services provides a default certificate template for domain controllers--the domain controller certificate template. Later releases provided a new certificate template--the domain controller authentication certificate template. These certificate templates were provided prior to update of the Kerberos specification that stated Key Distribution Centers (KDCs) performing certificate authentication needed to include the KDC Authentication extension.
The Kerberos Authentication certificate template is the most current certificate template designated for domain controllers and should be the one you deploy to all your domain controllers (2008 or later).
The autoenrollment feature in Windows enables you to effortlessly replace these domain controller certificates. You can use the following configuration to replace older domain controller certificates with a new certificate using the Kerberos Authentication certificate template.
Sign-in a certificate authority or management workstations with Enterprise Admin equivalent credentials.
- Open the Certificate Authority management console.
- Right-click Certificate Templates and click Manage.
- In the Certificate Template Console, right-click the Domain Controller Authentication (Kerberos) (or the name of the certificate template you created in the previous section) template in the details pane and click Properties.
- Click the Superseded Templates tab. Click Add.
- From the Add Superseded Template dialog, select the Domain Controller certificate template and click OK. Click Add.
- From the Add Superseded Template dialog, select the Domain Controller Authentication certificate template and click OK.
- From the Add Superseded Template dialog, select the Kerberos Authentication certificate template and click OK.
- Add any other enterprise certificate templates that were previously configured for domain controllers to the Superseded Templates tab.
- Click OK and close the Certificate Templates console.
The certificate template is configured to supersede all the certificate templates provided in the certificate templates superseded templates list. However, the certificate template and the superseding of certificate templates is not active until you publish the certificate template to one or more certificate authorities.
Note
The domain controller's certificate must chain to a root in the NTAuth store. By default, the Active Directory Certificate Authority's root certificate is added to the NTAuth store. If you are using a third-party CA, this may not be done by default. If the domain controller certificate does not chain to a root in the NTAuth store, user authentication will fail. To see all certificates in the NTAuth store, use the following command:
Certutil -viewstore -enterprise NTAuth
Publish Certificate Templates to a Certificate Authority
The certificate authority may only issue certificates for certificate templates that are published to that certificate authority. If you have more than one certificate authority and you want that certificate authority to issue certificates based on a specific certificate template, then you must publish the certificate template to all certificate authorities that are expected to issue the certificate.
Sign-in to the certificate authority or management workstations with enterprise administrator equivalent credentials.
- Open the Certificate Authority management console.
- Expand the parent node from the navigation pane.
- Click Certificate Templates in the navigation pane.
- Right-click the Certificate Templates node. Click New, and click Certificate Template to issue.
- In the Enable Certificates Templates window, select the Domain Controller Authentication (Kerberos) template you created in the previous steps. Click OK to publish the selected certificate templates to the certificate authority.
- If you published the Domain Controller Authentication (Kerberos) certificate template, then you should unpublish the certificate templates you included in the superseded templates list.
- To unpublish a certificate template, right-click the certificate template you want to unpublish in the details pane of the Certificate Authority console and select Delete. Click Yes to confirm the operation.
- Close the console.
Unpublish Superseded Certificate Templates
The certificate authority only issues certificates based on published certificate templates. For defense in depth security, it is a good practice to unpublish certificate templates that the certificate authority is not configured to issue. This includes the pre-published certificate template from the role installation and any superseded certificate templates.
The newly created domain controller authentication certificate template supersedes previous domain controller certificate templates. Therefore, you need to unpublish these certificate templates from all issuing certificate authorities.
Sign-in to the certificate authority or management workstation with Enterprise Admin equivalent credentials.
- Open the Certificate Authority management console.
- Expand the parent node from the navigation pane.
- Click Certificate Templates in the navigation pane.
- Right-click the Domain Controller certificate template in the content pane and select Delete. Click Yes on the Disable certificate templates window.
- Repeat step 4 for the Domain Controller Authentication and Kerberos Authentication certificate templates.
Section Review
[!div class="checklist"]
- Domain Controller certificate template
- Configure superseded domain controller certificate templates
- Publish Certificate templates to certificate authorities
- Unpublish superseded certificate templates s [!div class="step-by-step"] < Configure Azure AD Connect Configure policy settings >
Follow the Windows Hello for Business hybrid key trust deployment guide
- Overview
- Prerequisites
- New Installation Baseline
- Configure Directory Synchronization
- Configure Azure Device Registration
- Configure Windows Hello for Business settings: PKI (You are here)
- Sign-in and Provision