This is a migrated thread and some comments may be shown as answers.

This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

5 Answers 765 Views

AsyncUpload

This is a migrated thread and some comments may be shown as answers.

Greg asked on 19 Feb 2013, 08:15 PM

As soon as a dropped a RadAsyncUpload control on the page, I started receiving the error above (the title). If I view the application locally it runs just fine. I run it on the server, it displays the error. On the server (Windows Server 2008 R2 Standard, IIS 7.5) the registry key HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > LSA > FipsAlgorithmPolicy is enabled, locally it is not. I read that rad controls are FIPS compatibile and am wondering why this is giving me issues. I have tried adding the machineKey with 3DES and still get error. I have set debug="false" in web.config and still get error. I am unable to remove the registry key. Any guidance on what to do to get this to work?

Application Web.Config
...
<

system.web>
<customErrors mode="Off" />
<compilation debug="true" strict="false" explicit="true" targetFramework="4.5" />
<httpRuntime targetFramework="4.5" />
</system.web>
...

Just updated my control set to the Q3 2012.

5 Answers, 1 is accepted

answered on 12 Mar 2013, 08:07 PM

I have followed the guide provided and it still didn't work. I am also having troubles exporting a radgrid to pdf. Locally I have the registry setting = 0 and it works. When I set it = 1 then I received the error. According to this link, "Starting from Q3 2011, RadControls for ASP.NET AJAX offically supports the FIPS standard." but then the next line in the document is "Please note that PDF export is not FIPS compliant."

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms. at System.Security.Cryptography.MD5CryptoServiceProvider..ctor() --- End of inner exception stack trace --- at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object[] args) at System.Security.Cryptography.MD5.Create() at Telerik.Pdf.Security.SecurityManager.CreateOwnerEntry(SecurityOptions options) at Telerik.Pdf.Security.SecurityManager..ctor(SecurityOptions options, FileIdentifier fileId) at Telerik.Web.Apoc.Pdf.PdfCreator.SetOptions(PdfRendererOptions options) at Telerik.Web.Apoc.Render.Pdf.PdfRenderer.StartRenderer() at Telerik.Web.Apoc.Fo.FOTreeBuilder.Parse(XmlReader reader)

Does the export to pdf use MD5? I'm at a loss on where to go from here. I really do not want to drop these controls from our current and future projects.