Article ID: 935449 - Last Review: May 23, 2007 - Revision: 1.4

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

Hotfix Download Available
View and request hotfix downloads

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

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.

Back to the top

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 "Enable the hotfix" section.

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. 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 (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 Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) installed on the computer.

889100 (http://support.microsoft.com/kb/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 SP1, x86-based versions

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform	SP requirement
Adfsreg.exe	5.2.3790.2912	7,680	05-Apr-2007	16:11	x86	SP1
System.web.security.singlesignon.dll	5.2.3790.2912	581,632	05-Apr-2007	16:36	x86	SP1

Windows Server 2003 SP2, x86-based versions

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform	SP requirement
Adfsreg.exe	5.2.3790.4055	7,680	05-Apr-2007	16:01	x86	SP2
System.web.security.singlesignon.dll	5.2.3790.4055	581,632	05-Apr-2007	16:44	x86	SP2

Windows Server 2003, x64-based versions

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform	SP requirement
Adfsreg.exe	5.2.3790.2912	9,216	05-Apr-2007	01:52	x64	SP1
System.web.security.singlesignon.dll	5.2.3790.2912	581,632	05-Apr-2007	01:52	x86	SP1

Windows Server 2003 SP2, x64-based versions

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform	SP requirement
Adfsreg.exe	5.2.3790.4055	9,216	05-Apr-2007	01:57	x64	SP2
System.web.security.singlesignon.dll	5.2.3790.4055	581,632	05-Apr-2007	01:57	x86	SP2

Back to the top

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:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
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.
Exit Registry Editor.

Back to the top

STATUS

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

Back to the top

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

Back to the top

REFERENCES

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

911722 (http://support.microsoft.com/kb/911722/ ) You may receive an error message when you access ASP.NET Web pages that have ViewState enabled after you upgrade from ASP.NET 1.1 to ASP.NET 2.0

Back to the top