update

v-lianna · web-flow · commit 3f8196d59b2d · 2025-02-11T10:41:05.000+08:00
diff --git a/support/windows-server/networking/certificate-requirements-eap-tls-peap.md b/support/windows-server/networking/certificate-requirements-eap-tls-peap.md
@@ -35,7 +35,6 @@ With either EAP-TLS or PEAP with EAP-TLS, the server accepts the client's authen
 - The user or the computer certificate on the client includes the **Client Authentication** purpose.
 - The user or the computer certificate doesn't fail any one of the checks that are performed by the CryptoAPI certificate store. And the certificate passes requirements in the remote access policy.
 - The user or the computer certificate doesn't fail any one of the certificate OID checks that are specified in the Network Policy Server (NPS) remote access policy.
-
 - The 802.1X client doesn't use registry-based certificates that are either smart-card certificates or certificates that are protected with a password.
 - The Subject Alternative Name (SubjectAltName) extension in the certificate contains the user principal name (UPN) of the user.
 - When clients use EAP-TLS or PEAP with EAP-TLS authentication, a list of all the installed certificates is displayed in the Certificates snap-in, with the following exceptions:
