This link came in handy when I ran into a domain that had FIPS turned on by default via GPO. It doesn't matter if it is not a sharepoint app. If you are using any .Net app in an environment like this, you may get the errors described in the link below.
The key is to edit the machine.config file (probably found in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG)
and make sure there is a section like this. *I had to add this section*
<configuration>
<runtime>
<enforceFIPSPolicy enabled="false"/>
</runtime>
</configuration>
<runtime>
<enforceFIPSPolicy enabled="false"/>
</runtime>
</configuration>
Props to the poster of the link below
Also found this information helpfull
I found that even if the global registry key was not set, if you are getting an error like this:
This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
Then just try adding that section above to the machine file. I don't remember if a reboot was necessary but like all things Microsoft, it couldn't hurt...
