You have some client computers that use certificate-based smart card authentication in a Windows Server 2008 R2-based domain environment.
You enable the Authentication Mechanism Assurance feature to specify a certificate issuance policy.
The smart card authentication logon process includes multiple certificate chains.
A user logs on to a computer in the domain by using a smart card.
In this scenario, the Key Distribution Center (KDC) does not set the specific certificate issuance policy, and the user's access token does not contain the expected group membership. Additionally, the KDC validates the certificate with any issuance policy that is available and checks whether the returned certificate chain has the required issuance policy.
This issue occurs because the certificate chain that the KDC selects does not map the client certificate issuance policies to the issuance policies that are mapped in Active Directory. Therefore, the user's access token does not have the expected group membership. This behavior results in an access control failure.
Note A single user’s certificate can have lots of possible certificate chains in a complex public key infrastructure (PKI) situation. In the design of the authentication mechanism assurance feature, the KDC depends on the certificate APIs to select the best chain to request the mapped groups for the user.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
To apply this hotfix, you must be running Windows Server 2008 R2 or Windows Server 2008 R2 Service Pack 1 (SP1).For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Important Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.
After you apply this hotfix, you need to set the DWORD value to 1 for the following registry key on the domain controller where this hotfix is installed:
This needs to be applied only on the domain controllers.
You must restart the domain controller after you set the previously mentioned registry value.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Windows Server 2008 R2
Windows Server 2008 R2
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
The MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MANIFEST files and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about authentication mechanism assurance for Active Directory Domain Services (AD DS) in Windows Server 2008 R2, go to the following Microsoft website:
Windows Server 2008 R2 Service Pack 1, Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Foundation, Windows Web Server 2008 R2