SSRS fails until I turn off FIPS

Question

Post reply

SSRS fails until I turn off FIPS

BC Featherstone

SSC-Addicted

Points: 411
More actions
February 10, 2010 at 11:33 am

#216515

I am running:
- Windows Server 2008 R2 EE
- SQL Server 2008 EE - database and RS
- The database is on one server and SSRS is on another
I turned on FIPS on both boxes using the local security policies. Everything works fine on the database server, but SSRS manager site refused to render until I turned off FIPS on the reporting server.
The error message stated that SSRS uses MD5 instead of AES/DES (FIPS standard).
Does anyone out there have any helpfull thoughts on how to run SSRS with FIPS on?
Brad

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 1

Does this help or lead you in the right direction?

http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/f60cbb51-bf6b-4b6a-b30e-db3096355392

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

BC Featherstone SSC-Addicted Points: 411 More actions · Answer 2

Yes, http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/f60cbb51-bf6b-4b6a-b30e-db3096355392 did work.

Here are the instructions that allow SSRS to operate in FIPS compliant mode. They are edited slightly from the original post.

1) In a text editor such as Notepad, open the Report Manager Web.config file which is located in the default path: <driver>:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportManager.

2) In the Web.config file, locate the <system.web> section.

3) Add the following <machineKey> entry to in the <system.web> section:

<machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>

4) Save the Web.config file.

I then:

A) Used the Local Group Policy editor to enable System crytography: Use FIPS compliant algorithms...

B) Stopped and started SSRS via SQL Server Configuration Manager

An it all works just fine

Thank you for your help.

Brad

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 3

Thank you for your contribution. 🙂

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/