Security Identity Mapping format is not homogeneous with the Schannel certificate mapper format in Windows Server 2003 (831789)
The information in this article applies to:
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Standard Edition
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, 64-Bit Enterprise Edition
SYMPTOMSSecurity Identity Mapping uses a specific format to store the Issuer name and the Subject name in the AltSecurityIdenties property. This format and the format that is used in the Schannel certificate mapper are not homogeneous. This format inconsistency may cause certificate-based authentication to fail.
CAUSE
The Schannel authentication may fail if the certificate that is used for the name mapping contains a plus character (+) either in the Issuer or in the Subject part. For example, if the following *.cer file contains a plus character in the AltSecurityIdenties property that is used for name mappings, the Schannel authentications based on this certificate will fail:
X509:<I>C=FR,O=ORG-TEST,OU=OU-TEST<S>C=FR,O=ORG-TEST,L=Paris (75),OU=OU-TEST,CN=CN-TEST + SN=TEST ANNUAIRE + G=CARTE 2
The Schannel certificate mapper expects the following string (without the plus character) in the AltSecurityIdenties property:
X509:<I>C=FR,O=ORG-TEST,OU=OU-TEST<S>C=FR,O=ORG-TEST,L=Paris (75),OU=OU-TEST,CN=CN-TEST SN=TEST ANNUAIRE G=CARTE 2
This problem occurs because the Microsoft Management Console (MMC) snap-in that creates the mapping does not
use the same format (logic) that is used by the SSL handshake when the Schannel authentication tries to
map the certificate to a user.
RESOLUTIONHotfix InformationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Windows Server 2003 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. PrerequisitesNo prerequisites are required. Restart requirementYou must restart your computer after you apply this hotfix. Hotfix replacement informationThis hotfix does not replace any other hotfixes. File information The English version of this hotfix has the file
attributes (or later) that are listed in the following table. The dates and
times for these files are listed in coordinated universal time (UTC). When you
view the file information, it is converted to local time. To find the
difference between UTC and local time, use the Time Zone tab
in the Date and Time tool in Control Panel.
Date Time Version Size File name
--------------------------------------------------------------
13-Nov-2003 01:08 5.2.3790.101 462,848 Certmgr.dll
13-Nov-2003 01:08 5.2.3790.101 83,456 Domadmin.dll
13-Nov-2003 01:08 5.2.3790.101 607,232 Dsadmin.dll
13-Nov-2003 01:08 5.2.3790.97 153,088 Schannel.dll
WORKAROUND To work around this problem, use a custom script to set the X509 AltSecurityIdentities property for the user account. Do not use the MMC snap-in. STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section of this article.
Modification Type: | Minor | Last Reviewed: | 10/27/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbBug kbfix kbQFE kbWinServ2003preSP1fix KB831789 kbAudDeveloper |
---|
|