Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Certificate mapping rule in IIS does not work for a client certificate that contains more than 64 characters in Windows

Certificate mapping rule in IIS does not work for a client certificate that contains more than 64 characters in Windows

View products that this article applies to.

Symptoms


Consider the following scenario:
  • You install Internet Information Services (IIS) 7 or a later version on a computer that is running Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, or Windows Server 2012.
  • You install the IIS Client Certificate Mapping module.
  • You configure client certificate mappings and certificate mapping rules on the computer.
    Note You can use client certificates for user authentication purposes. For more information about this, go to the "References" section.
  • The client certificate field (compared with the matchCriteria property) is a string that is longer than 64 characters and that includes the terminating NULL. For example, the name of the user ("Issued to") is a string that contains more than 64 characters.
In this scenario, the certificate mapping rule does not work correctly.

↑ Back to the top

Cause

This issue occurs because the Authmap.dll file has a buffer for the client certificate field that compares with the matchCriteria property and that equals 64 characters. When the client certificate field contains more than 64 characters, only the first 64 characters are compared with the string that is set in the matchCriteria property.

↑ Back to the top

Resolution

Hotfix information

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 this specific problem.

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, submit a request to 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:
http://support.microsoft.com/contactus/?ws=support
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.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008 SP2
  • Windows 7 SP1
  • Windows Server 2008 R2
  • Windows 8
  • Windows Server 2012

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information
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 and Windows Vista file information and notes

Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" 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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.600
    2.
    23xxx    		Windows Server 2008 and Windows VistaSP2LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxx version number.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008" section. MUM files and 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 x86-based versions of Windows Server 2008 and Windows Vista
File nameFile versionFile sizeDateTimePlatform
Authmap.dll7.0.6002.2330240,96013-Jan-201408:49x86
For all supported x64-based versions of Windows Server 2008 and Windows Vista
File nameFile versionFile sizeDateTimePlatform
Authmap.dll7.0.6002.2330246,08013-Jan-201409:53x64
Authmap.dll7.0.6002.2330240,96013-Jan-201408:49x86
For all supported IA-64-based versions of Windows Server 2008 and Windows Vista
File nameFile versionFile sizeDateTimePlatform
Authmap.dll7.0.6002.2330299,32813-Jan-201407:11IA-64
Authmap.dll7.0.6002.2330240,96013-Jan-201408:49x86

Windows 7 and Windows Server 2008 R2 file information and 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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    VersionProductSR_LevelService branch
    6.1.760
    1.
    22xxx    		Windows 7 and Windows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7 and Windows Server 2008 R2" section. MUM and 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 x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Authmap.dll7.5.7601.2256541,47213-Jan-201408:27x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Authmap.dll7.5.7601.2256546,08013-Jan-201409:03x64
Authmap.dll7.5.7601.2256541,47213-Jan-201408:27x86
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Authmap.dll7.5.7601.2256599,84013-Jan-201408:15IA-64
Authmap.dll7.5.7601.2256541,47213-Jan-201408:27x86

Windows 8 and Windows Server 2012 file information and notes

Important Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" 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.

    VersionProductMilestoneService branch
    6.2.920 0.16 xxxWindows 8 and Windows Server 2012RTMGDR
    6.2.920 0.20 xxxWindows 8 and Windows Server 2012RTMLDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 8 and Windows Server 2012" section. MUM and 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 x86-based versions of Windows 8
File nameFile versionFile sizeDateTimePlatform
Authmap.dll8.0.9200.2091435,32813-Jan-201423:32x86
For all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Authmap.dll8.0.9200.2091440,96013-Jan-201423:29x64
Authmap.dll8.0.9200.2091435,32813-Jan-201423:32x86

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

Additional file information

Additional file information for Windows Server 2008 and Windows Vista

Additional files for all supported x86-based versions of Windows Server 2008 and Windows Vista
File propertyValue
File nameX86_daa5c6bbb4b2063a442e12b3916c58c4_31bf3856ad364e35_6.0.6002.23302_none_0af0e037bb7d09d5.manifest
File versionNot applicable
File size727
Date (UTC)13-Jan-2014
Time (UTC)20:17
File nameX86_microsoft-windows-i..ppingauthentication_31bf3856ad364e35_6.0.6002.23302_none_ff9498919532ca12.manifest
File versionNot applicable
File size6,378
Date (UTC)13-Jan-2014
Time (UTC)09:38
Additional files for all supported x64-based versions of Windows Server 2008 and Windows Vista
File propertyValue
File nameAmd64_bdb5cc535e39bcc3bc538946268bd1ac_31bf3856ad364e35_6.0.6002.23302_none_0c76b87bdf378a72.manifest
File versionNot applicable
File size1,104
Date (UTC)13-Jan-2014
Time (UTC)20:17
File nameAmd64_microsoft-windows-i..ppingauthentication_31bf3856ad364e35_6.0.6002.23302_none_5bb334154d903b48.manifest
File versionNot applicable
File size6,394
Date (UTC)13-Jan-2014
Time (UTC)10:52
File nameWow64_microsoft-windows-i..ppingauthentication_31bf3856ad364e35_6.0.6002.23302_none_6607de6781f0fd43.manifest
File versionNot applicable
File size3,715
Date (UTC)13-Jan-2014
Time (UTC)09:32
Additional files for all supported IA-64-based versions of Windows Server 2008 and Windows Vista
File propertyValue
File nameIa64_86fc2a4aa1f20561d47d8d726161e2ac_31bf3856ad364e35_6.0.6002.23302_none_c2ad4ae08d01ea97.manifest
File versionNot applicable
File size1,102
Date (UTC)13-Jan-2014
Time (UTC)20:17
File nameIa64_microsoft-windows-i..ppingauthentication_31bf3856ad364e35_6.0.6002.23302_none_ff963c879530d30e.manifest
File versionNot applicable
File size6,386
Date (UTC)13-Jan-2014
Time (UTC)08:19
File nameWow64_microsoft-windows-i..ppingauthentication_31bf3856ad364e35_6.0.6002.23302_none_6607de6781f0fd43.manifest
File versionNot applicable
File size3,715
Date (UTC)13-Jan-2014
Time (UTC)09:32

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File propertyValue
File nameX86_544e1f761cfff684032b38e6053a9b79_31bf3856ad364e35_6.1.7601.22565_none_2d0d577c1989e947.manifest
File versionNot applicable
File size735
Date (UTC)13-Jan-2014
Time (UTC)21:01
File nameX86_microsoft-windows-i..henticationbinaries_31bf3856ad364e35_6.1.7601.22565_none_e0440fa220029152.manifest
File versionNot applicable
File size3,449
Date (UTC)13-Jan-2014
Time (UTC)09:02
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File propertyValue
File nameAmd64_43b9998ec531f5dd586f259a984fe593_31bf3856ad364e35_6.1.7601.22565_none_7279bbad2a4bcc43.manifest
File versionNot applicable
File size1,120
Date (UTC)13-Jan-2014
Time (UTC)21:01
File nameAmd64_microsoft-windows-i..henticationbinaries_31bf3856ad364e35_6.1.7601.22565_none_3c62ab25d8600288.manifest
File versionNot applicable
File size3,455
Date (UTC)13-Jan-2014
Time (UTC)10:11
File nameWow64_microsoft-windows-i..henticationbinaries_31bf3856ad364e35_6.1.7601.22565_none_46b755780cc0c483.manifest
File versionNot applicable
File size3,086
Date (UTC)13-Jan-2014
Time (UTC)08:42
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File propertyValue
File nameIa64_b870cb9d125a082c9c0b839dafdf60a4_31bf3856ad364e35_6.1.7601.22565_none_d2740abf6030d241.manifest
File versionNot applicable
File size1,118
Date (UTC)13-Jan-2014
Time (UTC)21:01
File nameIa64_microsoft-windows-i..henticationbinaries_31bf3856ad364e35_6.1.7601.22565_none_e045b39820009a4e.manifest
File versionNot applicable
File size3,452
Date (UTC)13-Jan-2014
Time (UTC)08:49
File nameWow64_microsoft-windows-i..henticationbinaries_31bf3856ad364e35_6.1.7601.22565_none_46b755780cc0c483.manifest
File versionNot applicable
File size3,086
Date (UTC)13-Jan-2014
Time (UTC)08:42

Additional file information for Windows 8 and for Windows Server 2012

Additional files for all supported x86-based versions of Windows 8
File propertyValue
File nameX86_fb9a7717891903a72ac0b9ce38d6973f_31bf3856ad364e35_6.2.9200.20915_none_e1bf6fe547a4c652.manifest
File versionNot applicable
File size735
Date (UTC)14-Jan-2014
Time (UTC)13:37
File nameX86_microsoft-windows-i..henticationbinaries_31bf3856ad364e35_6.2.9200.20915_none_db6992d392c5c305.manifest
File versionNot applicable
File size3,119
Date (UTC)14-Jan-2014
Time (UTC)00:14
Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012
File propertyValue
File nameAmd64_9bef2a3d3d3d41d70961db18e70585d8_31bf3856ad364e35_6.2.9200.20915_none_747c6a72bdee4a66.manifest
File versionNot applicable
File size1,120
Date (UTC)14-Jan-2014
Time (UTC)13:38
File nameAmd64_microsoft-windows-i..henticationbinaries_31bf3856ad364e35_6.2.9200.20915_none_37882e574b23343b.manifest
File versionNot applicable
File size3,125
Date (UTC)14-Jan-2014
Time (UTC)02:13
File nameWow64_microsoft-windows-i..henticationbinaries_31bf3856ad364e35_6.2.9200.20915_none_41dcd8a97f83f636.manifest
File versionNot applicable
File size3,125
Date (UTC)13-Jan-2014
Time (UTC)23:57

↑ Back to the top

References

For more information about how to configure Many-to-One client certificate mapping for IIS 7 and IIS 7.5, go to the following Microsoft website:

How to configure Many-to-One client certificate mapping for IIS 7 and IIS 7.5
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2895312
Revision : 1
Created on : 1/7/2017
Published on : 4/27/2014
Exists online : False
Views : 291