仍在遭受Windows NPS 2022年5月更新

Question

在2022年5月，微软的更改客户端证书映射到AD帐户的方式，导致802.1XEAP-TLS计算机帐户认证停止工作.下面是一个有详细背景信息的其他资源，用于Schannel<=>Kerbers S4U2Self身份验证

为此可采取的解决办法如下：

• 使用altSecurityIdentities映射创建强映射
• 使用新的证书扩展szOID_NTDS_CA_SECURITY_EXT
• 通过Schannel<=>Kerberos注册表项暂时禁用S4u2Self并为SAN证书映射设置标志0x4

如果NPS服务器和客户端计算机帐户位于同一域中，则This都能正常工作。但是，在我们的方案中，NPS服务器位于林的根域中，而客户端计算机帐户位于子域中。<#>This导致所有子域中的计算机帐户无法使用原因代码16进行身份验证，事件4625和6273将记录在NPS服务器上。

根域中的计算机帐户(如NPS服务器)可以成功地进行身份验证。

<#>The问题似乎介于Schannel和Kerberos身份验证之间：

• 将所有子域控制器和NPS服务器上的CertificateMappingMethods密钥设置为0x1F可使身份验证工作(不幸的是只有临时解决方案)
• 使用altSecurityIdentities映射创建强映射没有任何效果；没有在DC上记录的事件；在NPS服务器上没有错误更改；没有明显的差异。
• 使用新的证书扩展szOID_NTDS_CA_SECURITY_EXT没有任何效果；身份验证仍然失败

记录在RADIUS服务器上的错误是：

Event 4625

An account failed to log on.

Subject:
    Security ID:        SYSTEM
    Account Name:       $
    Account Domain:     
    Logon ID:       0x3E7

Logon Type:         3

Account For Which Logon Failed:
    Security ID:        NULL SID
    Account Name:       
    Account Domain:     

Failure Information:
    Failure Reason:     Unknown user name or bad password.
    Status:         0xC000006D
    Sub Status:     0xC0000064

Process Information:
    Caller Process ID:  0x278
    Caller Process Name:    C:\Windows\System32\lsass.exe

Network Information:
    Workstation Name:   
    Source Network Address: -
    Source Port:        -

Detailed Authentication Information:
    Logon Process:      Schannel
    Authentication Package: Kerberos
    Transited Services: -
    Package Name (NTLM only):   -
    Key Length:     0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
    - Transited services indicate which intermediate services have participated in this logon request.
    - Package name indicates which sub-protocol was used among the NTLM protocols.
    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

Event 6273

Network Policy Server denied access to a user.

Contact the Network Policy Server administrator for more information.

User:
    Security ID:            \$
    Account Name:           host/
    Account Domain:         
    Fully Qualified Account Name:   \$

Client Machine:
    Security ID:            NULL SID
    Account Name:           -
    Fully Qualified Account Name:   -
    Called Station Identifier:      6E-22-32-2F-19-CF:
    Calling Station Identifier:     84-38-38-86-82-C2

NAS:
    NAS IPv4 Address:       
    NAS IPv6 Address:       -
    NAS Identifier:         6e22322f09cf
    NAS Port-Type:          Wireless - IEEE 802.11
    NAS Port:           1

RADIUS Client:
    Client Friendly Name:       
    Client IP Address:          

Authentication Details:
    Connection Request Policy Name: Secure Wireless Connections
    Network Policy Name:        Secure Wireless Connections
    Authentication Provider:        Windows
    Authentication Server:      
    Authentication Type:        EAP
    EAP Type:           Microsoft: Smart Card or other certificate
    Account Session Identifier:     43323444383435463834444530463634
    Logging Results:            Accounting information was written to the SQL data store.
    Reason Code:            16
    Reason:             Authentication failed due to a user credentials mismatch. Either the user name provided does not map to an existing user account or the password was incorrect.

看起来NPS服务器似乎无法获得子域的Kerberos票证；但我不确定。

总之：身份验证工作，除非客户端是与NPS服务器(或兄弟域)相同林的双向受信任子域。

也曾尝试过：

• 将NPS服务器添加到子域中的"RAS和IAS服务器“组中。

我们缺少哪些配置选项？？

Answer 1

有同样的情况：

因此，需要让NPS服务器(S)执行TSL 1.2，如下所示：

https://warlord0blog.wordpress.com/2017/02/09/tls-and-nps/ https://support.microsoft.com/en-us/topic/microsoft-security-advisory-update-for-microsoft-eap-implementation-that-enables-the-use-of-tls-october-14-2014-d9ba4b83-b4e9-2c01-83a7-e42706e671af

否则，使用2022年12月更新的Win 11 22H2客户端将无法连接。