Microsoft KB Archive/935449

= ADFS error message on a Windows Server 2003 R2-based computer: &quot;The implementation is not part of Windows platform FIPS validated cryptographic algorithms&quot; =

Article ID: 935449

Article Last Modified on 5/23/2007

-

APPLIES TO


 * Microsoft Windows Server 2003 R2 Enterprise x64 Edition
 * Microsoft Windows Server 2003 R2 Datacenter Edition (32-Bit x86)
 * Microsoft Windows Server 2003 R2 Datacenter x64 Edition
 * Microsoft Windows Server 2003 R2 Enterprise Edition (32-Bit x86)
 * Microsoft Windows Server 2003 R2 Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003 R2 Standard x64 Edition

-



SYMPTOMS
Consider the following scenario on a Windows Server 2003 R2-based computer:
 * A Federal Information Processing Standard (FIPS)-compliant algorithm that is mentioned in the Microsoft Knowledge Base article 911722 is enabled.
 * You turn off the debugging switch in the Web.config file.

In this scenario, Active Directory Federation Services (ADFS) cannot handle the exception in the following class and assembly:
 * SHA1Managed class
 * System.Web.Security.SingleSignOn.dll assembly

In addition, you receive the following error message:

The implementation is not part of Windows platform FIPS validated cryptographic algorithms.



RESOLUTION
To resolve this problem, install the hotfix that is mentioned in this article, and then create the FipsAlgorithmPolicy registry entry. To create the registry entry and to enable the hotfix, see the &quot;Enable the hotfix&quot; section.

Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only 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 Windows Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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.

Prerequisites
To apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) installed on the computer.

889100 How to obtain the latest service pack for Windows Server 2003

Restart requirement
You must restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.

Windows Server 2003 SP2, x64-based versions


Enable the hotfix
After you install the hotfix, create the FipsAlgorithmPolicy registry entry to enable the hotfix. To do this, follow these steps:  Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey:

 On the Edit menu, point to New, and then click DWORD Value. In the details pane, type FipsAlgorithmPolicy, and then press ENTER. Right-click FipsAlgorithmPolicy, and then click Modify. In the Edit DWORD Value dialog box, under Base, click Decimal. In the Value data box, type 1, and then click OK.</li> Exit Registry Editor.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
When this problem occurs, a stack trace that resembles the following is generated. [InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.] System.Security.Cryptography.SHA1Managed..ctor +1482194 System.Web.Security.SingleSignOn.FederationServerService.RequestSecurityTokenWithClaimsWorker(Boolean isProxyRequest, TrustPolicy t...  System.Web.Security.SingleSignOn.FederationServerService.RequestSecurityTokenWithClaims(TokenIssuanceAudit audit, TrustPolicy trust...   System.Web.Security.SingleSignOn.FederationServerService.ProcessVerifiedCredentials(TrustPolicy trustPolicy, Byte[] cookie, TokenIs...   System.Web.Security.SingleSignOn.FederationServerService.InternalRSTWithSids(String userSamName, String usersid, String[] groupsids...   System.Web.Security.SingleSignOn.FederationServerInProcessProxy.BeginRequestSecurityTokenWithSids(String userSamName, String usersi...   System.Web.Security.SingleSignOn.LSAuthenticationOBject.BeginLogonClientWorker(WindowsIdentity identity, AsyncCallback cb, Object s... System.Web.Security.SingleSignOn.LSAuthenticationOBject.BeginLogonCLient(WindowsIdentity identity, AsyncCallback cb, Object s) +31 ASP.ls_auth_integrated_clientlogon_aspx.BeginAsyncLogon(Object sender, EventArgs args, AsyncCallback cb, Object state) +112 System.Web.UI.PageAsyncInfo.CallHandlersPossiblyUnderLock(Boolean onPageThread) +378 System.Web.UI.PageAsyncInfo.CallHandlersCancellableCallback(Object state) +67 System.Web.HttpContext.InvokeCancellableCallback(WaitCallback callback, Object state) +71 System.Web.UI.PageAsyncInfo.CallHandlers(Boolean onPageThread) +68

[HttpException (0x80004005): Exception of type 'System.Web.HttpExecption' was thrown.] System.Web.HttpAsyncResult.End +3284555 System.Web.UI.Page.AsyncPageEndProcessRequest(IAsyncResult result) +21 ASP.ls_auth_integrated_clientlogon_aspx.EndProcessRequest(IAsyncResult ar) +4 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute +3291213 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) + 155

<div class="references_section">