Original KB number: 4043463
Applies to: Supported versions of Windows Server and Windows Client
User principal name (UPN) mapping is a special case of one-to-one mapping used in Active Directory. This article describes how to use an explicit mapping instead of UPN mapping by disabling the subject alternative name (SAN) through Registry Editor. Performing the following steps will allow the use of an explicit mapping by ignoring the SAN extension of a deployed client certificate.
Server-side
- Open Registry Editor.
- Go to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Kdc\UseSubjectAltName. - Right-click UseSubjectAltName, select Modify Binary data, and then set the Value data to 0.
Note: The value of the UseSubjectAltName registry key must be set to 0 on all key distribution centers (KDC) for the domain.
Client-side
Note: You must also perform steps on the client-side if the following conditions are met:
- Client certificate mapping (AltSecID) is used.
- A UPN is used in the SAN extension of a client certificate.
- No domain hint is used.
Here's how to disable the SAN for the UPN mapping on the client-side:
- Open Registry Editor.
- Go to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters. - Press and hold (right-click) Parameters, select New > DWORD (32-bit) Value, and then name it UseSubjectAltName. Double-click it, set the Value data to 0, and then press Enter.
Reference
For more information about SAN or UPN mapping, see smart card logon flow in Certificate Enumeration.
Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
