AD FS cannot process SAML response in Windows Server 2012 R2

View products that this article applies to.

This article describes an issue that occurs when Security Assertions Markup Language (SAML) assertions contain multiple X509Data clauses in Windows Server 2012 R2. A hotfix is available to resolve this issue. The hotfix has a prerequisite.

↑ Back to the top

Symptoms

When this issue occurs, the Active Directory Federation Services (AD FS) server throws an error message that resembles the following:

Exception details:
Microsoft.IdentityServer.Protocols.Saml.SamlProtocolException: MSIS1022: Cannot process SAML Response from ''.
Inner exception: 'Element' is an invalid XmlNodeType. Line 1, position 1.
at Microsoft.IdentityServer.Service.Tokens.SamlMessageSecurityTokenHandler.ReadToken(XmlReader reader)
at Microsoft.IdentityModel.Tokens.SecurityTokenHandlerCollection.ReadToken(XmlReader reader)
at Microsoft.IdentityModel.Tokens.SecurityTokenElement.ReadSecurityToken(XmlElement securityTokenXml, SecurityTokenHandlerCollection securityTokenHandlers)
at Microsoft.IdentityModel.Tokens.SecurityTokenElement.GetSecurityToken()
at Microsoft.IdentityServer.Web.Protocols.Saml.SamlProtocolHandler.GetSecurityTokenFromSignInResponse(ProtocolContext context)
at Microsoft.IdentityServer.Web.PassiveProtocolListener.ProcessProtocolRequest(ProtocolContext protocolContext, PassiveProtocolHandler protocolHandler)
at Microsoft.IdentityServer.Web.PassiveProtocolListener.OnGetContext(WrappedHttpListenerContext context)

↑ Back to the top

Cause

This issue occurs because the ds:X509Data element in SAML assertions contains multiple child elements.

↑ Back to the top

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 have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows Server 2012 R2.

Registry information

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

Restart requirement

You may 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 2012 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 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 8.1/Windows Server 2012 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:

Version Product Milestone Service branch
6.3.960 0.17 xxx Windows Server 2012 R2 RTM GDR
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are

listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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.

Version	Product	Milestone	Service branch
6.3.960 0.17 xxx	Windows Server 2012 R2	RTM	GDR

For all supported x64-based versions of Windows Server 2012 R2

File name	File version	File size	Date	Time	Platform
Microsoft.identityserver.identitymodel.dll	6.3.9600.17664	1,127,424	21-Jan-2015	05:50	x86

Additional file information

Additional file information for Windows Server 2012 R2

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

File property	Value
File name	Amd64_84313360c9c1a0ded24613baac175ac3_31bf3856ad364e35_6.3.9600.17664_none_58cca5c60bebb854.manifest
File version	Not applicable
File size	711
Date (UTC)	21-Jan-2015
Time (UTC)	15:58
Platform	Not applicable
File name	Msil_microsoft.identityserver.identitymodel_31bf3856ad364e35_6.3.9600.17664_none_6205a522de8c8bc8.manifest
File version	Not applicable
File size	3,355
Date (UTC)	21-Jan-2015
Time (UTC)	06:01
Platform	Not applicable