大网数据广告活动
网络与域名解析

Configure Certificate Templates for PEAP and EAP requirements

· 52CE 我爱测

This article provides information about using certificates with Network Policy Server and Remote Access in Windows Server 2016.

All certificates that are used for network access authentication with Extensible Authentication Protocol-Transport Layer Security (EAP-TLS), Protected Extensible Authentication Protocol-Transport Layer Security (PEAP-TLS), and PEAP-Microsoft Challenge Handshake Authentication Protocol version 2 (MS-CHAP v2) must meet the requirements for X.509 certificates and work for connections that use Secure Socket Layer/Transport Level Security (SSL/TLS). Both client and server certificates have additional requirements.

Important: This article provides instructions for configuring certificate templates. To use these instructions, you must deploy your own Public Key Infrastructure (PKI) with Active Directory Certificate Services (AD CS) as required.

Minimum server certificate requirements

With PEAP-MS-CHAP v2, PEAP-TLS, or EAP-TLS as the authentication method, the NPS must use a server certificate that meets the minimum server certificate requirements.

Client computers can be configured to validate server certificates by using the Validate server certificate option on the client computer or in Group Policy.

The client computer accepts the authentication attempt of the server when the server certificate meets the following requirements:

  • The Subject name contains a value. If you issue a certificate to your server running Network Policy Server (NPS) that has a blank Subject name, the certificate isn't available to authenticate your NPS. To configure the certificate template with a Subject name:

    1. Open Certificate Templates.
    2. In the details pane, right-click the certificate template that you want to change, and then select Properties .
    3. Select the Subject Name tab, and then select Build from this Active Directory information.
    4. In Subject name format, select a value other than None.
  • The computer certificate on the server:

    • Chains to a trusted root certification authority (CA) that includes the Server Authentication purpose in EKU extensions (the object identifier (OID) for Server Authentication is 1.3.6.1.5.5.7.3.1), and passes:

      • The checks performed by CryptoAPI
      • The checks specified in the remote access policy or network policy
  • Configure the server certificate with the required cryptography setting:

    1. Open Certificate Templates.
    2. In the details pane, right-click the certificate template that you want to change, and then select Properties.
    3. Select the Cryptography tab and make sure to configure the following:
      • Provider Category: for example, Key Storage Provider
      • Algorithm Name: for example, RSA
      • Providers: for example, Microsoft Software Key Storage Provider
      • Minimum key size: for example, 2048
      • Hash Algorithm: for example, SHA256
    4. Select Next.
  • The Subject Alternative Name (SubjectAltName) extension, if used, must contain the DNS name of the server. To configure the certificate template with the Domain Name System (DNS) name of the enrolling server:

    1. Open Certificate Templates.
    2. In the details pane, right-click the certificate template that you want to change, and then select Properties .
    3. Select the Subject Name tab, and then select Build from this Active Directory information.
    4. In Include this information in alternate subject name, select DNS name.

When users use PEAP and EAP-TLS, NPS displays a list of all installed certificates in the computer certificate store, with the following exceptions:

  • Certificates that don't contain the Server Authentication purpose in EKU extensions aren't displayed.

  • Certificates that don't contain a Subject name aren't displayed.

  • Registry-based and smart card-logon certificates aren't displayed.

For more information, see Deploy Server Certificates for 802.1X Wired and Wireless Deployments.

Minimum client certificate requirements

With EAP-TLS or PEAP-TLS, the server accepts the client authentication attempt when the certificate meets the following requirements:

  • The client certificate is issued by an enterprise CA or mapped to a user or computer account in Active Directory Domain Services (AD DS).

  • The user or computer certificate on the client:

    • Chains to a trusted root CA that includes the Client Authentication purpose in EKU extensions (the OID for Client Authentication is 1.3.6.1.5.5.7.3.2), and passes:

      • The checks performed by CryptoAPI

      • The checks specified in the remote access policy or network policy

      • The certificate object identifier checks specified in NPS network policy.

  • The 802.1X client doesn't use registry-based certificates that are either smart card-logon or password-protected certificates.

  • For user certificates, the Subject Alternative Name (SubjectAltName) extension in the certificate contains the user principal name (UPN). To configure the UPN in a certificate template:

    1. Open Certificate Templates.
    2. In the details pane, right-click the certificate template that you want to change, and then select Properties.
    3. Select the Subject Name tab, and then select Build from this Active Directory information.
    4. In Include this information in alternate subject name, select User principal name (UPN).
  • For computer certificates, the Subject Alternative Name (SubjectAltName) extension in the certificate must contain the fully qualified domain name (FQDN) of the client, which is also called the DNS name. To configure this name in the certificate template:

    1. Open Certificate Templates.
    2. In the details pane, right-click the certificate template that you want to change, and then select Properties.
    3. Select the Subject Name tab, and then select Build from this Active Directory information.
    4. In Include this information in alternate subject name, select DNS name.

With PEAP-TLS and EAP-TLS, clients display a list of all installed certificates in the Certificates snap-in, with the following exceptions:

  • Wireless clients don't display registry-based and smart card-logon certificates.

  • Wireless clients and VPN clients don't display password-protected certificates.

  • Certificates that don't contain the Client Authentication purpose in EKU extensions aren't displayed.

See also

Source: Microsoft Learn / Windows Server documentation by Microsoft and contributors (upstream author metadata: robinharwood). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Server documentation
适用范围
Windows Server · Source date 01/16/2025
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。