Signature verification fails when you use SAML tokens and a third-party cryptographic security module if Windows Identity Foundation is installed in Windows Server 2008 or in Windows Server 2008 R2

Article translations Article translations
Article ID: 2599538 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You install Microsoft Windows Identity Foundation on a computer that is running Windows Server 2008 or Windows Server 2008 R2 in a network environment.
  • You use a third-party cryptographic security module on a hardware security module (HSM) in the network environment.
  • The HSM is used to store the private key of a token-signing certificate.
  • You try to use Security Assertion Markup Language (SAML) tokens for authentication in this environment.
In this scenario, signature verification fails when the SAML tokens are being processed. Additionally, you receive the following exception event logs:

Event ID 303
Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event

">
- <System>
<Provider Name="AD FS 2.0" Guid="{20E25DDB-09E5-404B-8A56-EDAE2F12EE81}" />
<EventID>303</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000001</Keywords>
<TimeCreated SystemTime="Time" />
<EventRecordID>19775</EventRecordID>
<Correlation ActivityID="{ActivityID}" />
<Execution ProcessID="ProcessID" ThreadID="ThreadID" />
<Channel>AD FS 2.0/Admin</Channel>
<Computer>FQDN</Computer>
<Security UserID="UserID" />
</System>
- <UserData>
- <Event xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://schemas.microsoft.com/ActiveDirectoryFederationServices/2.0/Events">
- <EventData>
<Data>Microsoft.IdentityModel.Protocols.XmlSignature.SignatureVerificationFailedException: MSIS0038: SAML Message has wrong signature. Issuer: 'http://idp-sts.external.ustest.lmco.com/adfs/services/trust'. at Microsoft.IdentityServer.Protocols.Saml.Contract.SamlContractUtility.CreateSamlMessage(MSISSamlBindingMessage message) at Microsoft.IdentityServer.Service.SamlProtocol.SamlProtocolService.Issue(IssueRequest issueRequest) at Microsoft.IdentityServer.Service.SamlProtocol.SamlProtocolService.ProcessRequest(Message requestMessage)</Data>
</EventData>
</Event>
</UserData>
</Event>

Event ID 364
Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event

">
- <System>
<Provider Name="AD FS 2.0" Guid="{20E25DDB-09E5-404B-8A56-EDAE2F12EE81}" />
<EventID>364</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000001</Keywords>
<TimeCreated SystemTime="Time" />
<EventRecordID>19776</EventRecordID>
<Correlation ActivityID="{ActivityID}" />
<Execution ProcessID="ProcessID" ThreadID="ThreadID" />
<Channel>AD FS 2.0/Admin</Channel>
<Computer>FQDN</Computer>
<Security UserID="UserID" />
</System>
- <UserData>
- <Event xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://schemas.microsoft.com/ActiveDirectoryFederationServices/2.0/Events">
- <EventData>
<Data>Microsoft.IdentityServer.Web.RequestFailedException: MSIS7012: An error occurred while processing the request. Contact your administrator for details. ---> System.ServiceModel.FaultException: The creator of this fault did not specify a Reason. at Microsoft.IdentityServer.Protocols.Saml.Contract.MSISSamlProtocolContractClientManager.ProcessRequest(Message request) at Microsoft.IdentityServer.Protocols.Saml.Contract.MSISSamlProtocolContractClient.ProcessRequest(MSISSamlRequest samlRequest) at Microsoft.IdentityServer.Protocols.Saml.Contract.MSISSamlProtocolContractClient.ProcessRequest[T](MSISSamlRequest samlRequest) at Microsoft.IdentityServer.Protocols.Saml.Contract.MSISSamlProtocolContractClient.Issue(HttpSamlMessage httpSamlMessage, SecurityTokenElement onBehalfOf, String sessionState, String& newSessionState, String& authenticatingProvider) at Microsoft.IdentityServer.Web.FederationPassiveAuthentication.RequestBearerToken(HttpSamlRequestMessage httpSamlRequest, SecurityTokenElement onBehalfOf, String& samlpSessionState, String& samlpAuthenticationProvider) --- End of inner exception stack trace --- at Microsoft.IdentityServer.Web.FederationPassiveAuthentication.RequestBearerToken(HttpSamlRequestMessage httpSamlRequest, SecurityTokenElement onBehalfOf, String& samlpSessionState, String& samlpAuthenticationProvider) at Microsoft.IdentityServer.Web.FederationPassiveAuthentication.BuildSignInResponseCoreWithSerializedToken(String signOnToken, WSFederationMessage incomingMessage) at Microsoft.IdentityServer.Web.FederationPassiveAuthentication.BuildSignInResponseCoreWithSecurityToken(SecurityToken securityToken, WSFederationMessage incomingMessage) at Microsoft.IdentityServer.Web.FederationPassiveAuthentication.BuildSignInResponseForProtocolRequest(FederationPassiveContext federationPassiveContext, SecurityToken securityToken) at Microsoft.IdentityServer.Web.FederationPassiveAuthentication.BuildSignInResponse(SecurityToken securityToken) System.ServiceModel.FaultException: The creator of this fault did not specify a Reason. at Microsoft.IdentityServer.Protocols.Saml.Contract.MSISSamlProtocolContractClientManager.ProcessRequest(Message request) at Microsoft.IdentityServer.Protocols.Saml.Contract.MSISSamlProtocolContractClient.ProcessRequest(MSISSamlRequest samlRequest) at Microsoft.IdentityServer.Protocols.Saml.Contract.MSISSamlProtocolContractClient.ProcessRequest[T](MSISSamlRequest samlRequest) at Microsoft.IdentityServer.Protocols.Saml.Contract.MSISSamlProtocolContractClient.Issue(HttpSamlMessage httpSamlMessage, SecurityTokenElement onBehalfOf, String sessionState, String& newSessionState, String& authenticatingProvider) at Microsoft.IdentityServer.Web.FederationPassiveAuthentication.RequestBearerToken(HttpSamlRequestMessage httpSamlRequest, SecurityTokenElement onBehalfOf, String& samlpSessionState, String& samlpAuthenticationProvider)</Data>
</EventData>
</Event>
</UserData>
</Event>

CAUSE

This issue occurs because the CreateSamlMessage function cannot verify signatures when you use a third-party cryptographic security module.

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:
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 Server 2008 Service Pack 2 (SP2)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
Additionally, you must have AD FS 2.0 installed.

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 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 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 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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Microsoft.identitymodel.dll6.1.7601.218051,093,63202-Sep-201110:59
For all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Microsoft.identitymodel.dll6.1.7601.218051,093,63202-Sep-201110:50
Windows Server 2008 R2 file information notes
  • 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:
    Collapse this tableExpand this table
    VersionProductMilestoneService branch
    6.1.760 0.21xxxWindows Server 2008 R2RTMLDR
    6.1.760 1.21xxxWindows 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 versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Microsoft.identitymodel.dll6.1.7600.210401,093,63231-Aug-201106:34
Microsoft.identitymodel.dll6.1.7601.218051,093,63231-Aug-201108:17

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
Collapse this tableExpand this table
File nameMsil_microsoft.identitymodel_31bf3856ad364e35_7.0.6002.22713_none_69f5c7925e740531.manifest
File versionNot Applicable
File size3,342
Date (UTC)08-Sep-2011
Time (UTC)19:10
File nameX86_9b5f0195f4641e38ea45e8629df5288d_31bf3856ad364e35_7.0.6002.22713_none_cd43532c445ef867.manifest
File versionNot Applicable
File size654
Date (UTC)12-Sep-2011
Time (UTC)07:23
Additional files for all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameAmd64_9b5f0195f4641e38ea45e8629df5288d_31bf3856ad364e35_7.0.6002.22713_none_2961eeaffcbc699d.manifest
File versionNot Applicable
File size656
Date (UTC)12-Sep-2011
Time (UTC)07:23
File nameMsil_microsoft.identitymodel_31bf3856ad364e35_7.0.6002.22713_none_69f5c7925e740531.manifest
File versionNot Applicable
File size3,346
Date (UTC)08-Sep-2011
Time (UTC)15:35

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_343e2fe9947d063eb95271428600775a_31bf3856ad364e35_7.1.7601.21805_none_1b300b4f814b6630.manifest
File versionNot Applicable
File size656
Date (UTC)31-Aug-2011
Time (UTC)11:09
File nameAmd64_cb3249ddaee029936ca1dc0c78998191_31bf3856ad364e35_7.1.7600.21040_none_6fb3702e79aa4e2f.manifest
File versionNot Applicable
File size656
Date (UTC)31-Aug-2011
Time (UTC)11:09
File nameMsil_microsoft.identitymodel_31bf3856ad364e35_7.1.7600.21040_none_681389a3c2802db7.manifest
File versionNot Applicable
File size2,333
Date (UTC)31-Aug-2011
Time (UTC)06:51
File nameMsil_microsoft.identitymodel_31bf3856ad364e35_7.1.7601.21805_none_6a2a518fbf817277.manifest
File versionNot Applicable
File size2,333
Date (UTC)31-Aug-2011
Time (UTC)08:45

Properties

Article ID: 2599538 - Last Review: October 13, 2011 - Revision: 1.0
APPLIES TO
  • Windows Identity Foundation
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseadvanced KB2599538

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com