AD FS 2.0 does not parse non-string XML attribute values in SAML 2.0 assertions in Windows Server 2008 or in Windows Server 2008 R2

Applies to: Windows Server 2008 StandardWindows Server 2008 EnterpriseWindows Server 2008 Datacenter More

Symptoms


Consider the following scenario:
  • You have a computer that is running Windows Server 2008 or Windows Server 2008 R2
  • You deploy Active Directory Federation Services (AD FS) 2.0 on the computer.
  • AD FS 2.0 parses a Security Assertion Markup Language (SAML) 2.0 assertion.
  • The SAML 2.0 assertion includes one or more non-string XML attribute values.
In this scenario, AD FS 2.0 does not parse non-string XML attribute values in the SAML 2.0 assertion. Additionally, an event that has the following description section is added to the AD FS event log:


Note If an SAML assertion includes only one non-string XML attribute, and if the XML attribute is the final attribute, AD FS 2.0 can parse the SAML assertion.

Cause


This issue occurs because AD FS 2.0 uses an incorrect method to read XML attributes in SAML 2.0 assertions.

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 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 Web site: 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 Server 2008 Service Pack 2 (SP2)
  • Windows Server 2008 R2
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008

For more information about how to obtain a Windows 7 or 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

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must 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 Vista and Windows Server 2008 file information 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
    0.
    20xxx
    Windows Server 2008RTMLDR
    6.0.600
    1.
    22xxx
    Windows Server 2008SP1LDR
    6.0.600
    2.
    22xxx
    Windows Server 2008SP2LDR
  • 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
File nameFile versionFile sizeDateTimePlatform
Microsoft.identitymodel.dll6.1.7600.208911,093,63209-Feb-201111:12x86
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Microsoft.identitymodel.dll6.1.7600.208911,093,63209-Feb-201111:05x86
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, 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
    0.
    20xxx
    Windows Server 2008 R2RTMLDR
    6.1.760
    1.
    21xxx
    Windows Server 2008 R2SP1LDR
  • 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 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 x64-based Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Microsoft.identitymodel.dll6.1.7600.208911,093,63229-Jan-201108:20x86
Microsoft.identitymodel.dll6.1.7601.216511,093,63229-Jan-201108:19x86

Status


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

More Information


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

Additional file information

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
File nameMsil_microsoft.identitymodel_31bf3856ad364e35_7.0.6002.22584_none_69ab149c5eabe7d1.manifest
File versionNot applicable
File size3,342
Date (UTC)09-Feb-2011
Time (UTC)19:21
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,675
Date (UTC)09-Feb-2011
Time (UTC)20:44
PlatformNot applicable
File nameX86_61045e7a86163aa75b4d8fe243b0e774_31bf3856ad364e35_7.0.6002.22584_none_24d684a7ab4a4b61.manifest
File versionNot applicable
File size654
Date (UTC)09-Feb-2011
Time (UTC)20:44
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Server 2008
File nameAmd64_61045e7a86163aa75b4d8fe243b0e774_31bf3856ad364e35_7.0.6002.22584_none_80f5202b63a7bc97.manifest
File versionNot applicable
File size656
Date (UTC)09-Feb-2011
Time (UTC)20:44
PlatformNot applicable
File nameMsil_microsoft.identitymodel_31bf3856ad364e35_7.0.6002.22584_none_69ab149c5eabe7d1.manifest
File versionNot applicable
File size3,346
Date (UTC)09-Feb-2011
Time (UTC)17:18
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,685
Date (UTC)09-Feb-2011
Time (UTC)20:44
PlatformNot applicable

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2

File nameAmd64_2f6bb84518f302470714fdfe3a3113c6_31bf3856ad364e35_7.1.7601.21651_none_4a8afcdd9f3f1478.manifest
File versionNot applicable
File size656
Date (UTC)30-Jan-2011
Time (UTC)10:01
PlatformNot applicable
File nameAmd64_3cf6032ce54068868773e64b919863f0_31bf3856ad364e35_7.1.7600.20891_none_648b761149501318.manifest
File versionNot applicable
File size656
Date (UTC)30-Jan-2011
Time (UTC)10:01
PlatformNot applicable
File nameMsil_microsoft.identitymodel_31bf3856ad364e35_7.1.7600.20891_none_67dea049c2a7a25a.manifest
File versionNot applicable
File size2,333
Date (UTC)29-Jan-2011
Time (UTC)08:40
PlatformNot applicable
File nameMsil_microsoft.identitymodel_31bf3856ad364e35_7.1.7601.21651_none_69f03cffbfad9e82.manifest
File versionNot applicable
File size2,333
Date (UTC)29-Jan-2011
Time (UTC)08:36
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,720
Date (UTC)30-Jan-2011
Time (UTC)10:01
PlatformNot applicable