Update windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-prereqs.md

Co-Authored-By: Nicole Turner <39884432+nenonix@users.noreply.github.com>
This commit is contained in:
Orlando Rodriguez 2019-05-13 11:58:41 -05:00 committed by GitHub
parent d42a7b0c3b
commit 250089d828
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -60,7 +60,7 @@ Key trust deployments do not need client issued certificates for on-premises aut
The minimum required enterprise certificate authority that can be used with Windows Hello for Business is Windows Server 2012, but you can also use a third-party enterprise certification authority. The detailed requirements for the Domain Controller certificate are shown below. The minimum required enterprise certificate authority that can be used with Windows Hello for Business is Windows Server 2012, but you can also use a third-party enterprise certification authority. The detailed requirements for the Domain Controller certificate are shown below.
* The certificate must have a CRL distribution-point extension that points to a valid certificate revocation list (CRL). * The certificate must have a Certificate Revocation List (CRL) distribution point extension that points to a valid CRL.
* Optionally, the certificate Subject section should contain the directory path of the server object (the distinguished name) * Optionally, the certificate Subject section should contain the directory path of the server object (the distinguished name)
* The certificate Key Usage section must contain: * The certificate Key Usage section must contain:
Digital Signature, Key Encipherment Digital Signature, Key Encipherment