Symptoms
Consider the following scenario. You have an IBM WebSphere application that has Federal Information Processing Standards (FIPS) enabled. When you use Microsoft SQL Server JDBC Driver 2.0 to connect to SQL Server 2008 from the IBM WebSphere application, the connection fails. Additionally, you receive the following error message:
java.sql.SQLException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: SSLv3 protocol cannot be enabled in FIPS mode.DSRA0010E: SQL State = 08S01, Error Code = 0
at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(Unknown Source)
at com.microsoft.sqlserver.jdbc.TDSChannel.throwSSLConnectionFailed(Unknown Source)
at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(Unknown Source)
Cause
This issue occurs because the IBM WebSphere application requires the TLS protocol for SSL connections when the application has FIPS enabled. However, Microsoft SQL Server JDBC Driver 2.0 requests the SSLv3 protocol. Therefore, the connection fails.
Microsoft SQL Server JDBC Driver 2.0 calls the SSLContext.getInstance function. This function takes a string argument. The string argument determines which protocols the returned context should support. According to the Java Secure Socket Extension (JSSE) reference guide, the SSLContext.getInstance function returns an SSLContext instance that supports the specified protocol. However, the returned SSLContext instance may also support other protocols.
In more detail, when Microsoft SQL Server JDBC Driver 2.0 passes "SSLv3" as the string argument, the Sun JSSE provider returns an SSLContext instance that supports both the SSLv3 protocol and the TLS protocol. However, the IBMJSSE2 provider returns an SSLContext instance that only supports the SSLv3 protocol. When a WebSphere application has FIPS enabled, the IBM Java Runtime Environment (JRE) requires the TLS protocol for SSL connections. Therefore, the connection fails.
Resolution
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.
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, submit a request to 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 website:
http://support.microsoft.com/contactus/?ws=supportNote 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.
Restart requirement
You do not have to restart the computer after you apply this hotfix.
Registry key information
To use one of the hotfixes in this package, you do not have to make any changes to the registry.
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.
32-bit version
|
File name |
File version |
File size |
Date |
Time |
Hashes |
Platform |
|---|---|---|---|---|---|---|
|
Sqljdbc.jar |
Not Applicable |
448,010 |
29-Apr-2010 |
06:56 |
Not Applicable |
Not Applicable |
|
Sqljdbc4.jar |
Not Applicable |
466,304 |
29-Apr-2010 |
06:56 |
Not Applicable |
Not Applicable |
|
Sqljdbc_auth.dll |
2.0.1803.209 |
172,464 |
29-Apr-2010 |
06:56 |
MD5: C8469387C4F00B56A6D01FB2A7EB4AA8 |
IA-64 |
|
Sqljdbc_auth.dll |
2.0.1803.209 |
86,448 |
29-Apr-2010 |
06:56 |
MD5: 12AB590CBA210BDF9D4BA05DB84F6144 |
x64 |
|
Sqljdbc_auth.dll |
2.0.1803.209 |
69,040 |
29-Apr-2010 |
06:56 |
MD5: C58C33FC8C1C4B05BFFA4F1CCC2A1856 |
x86 |
|
Xa_install.sql |
Not Applicable |
3,712 |
29-Apr-2010 |
06:56 |
Not Applicable |
Not Applicable |
|
Sqljdbc_xa.dll |
2.0.1803.209 |
251,824 |
29-Apr-2010 |
06:56 |
MD5: C312A65209D4E2454DA8E60D8A9DEB5D |
IA-64 |
|
Sqljdbc_xa.dll |
2.0.1803.209 |
130,480 |
29-Apr-2010 |
06:56 |
MD5: 1D7E2961C1C956BF792AE9F86C49EC26 |
x64 |
|
Sqljdbc_xa.dll |
2.0.1803.209 |
101,296 |
29-Apr-2010 |
06:56 |
MD5: 749C78CFF95D7A06D6671DCBA827F5CF |
x86 |
x64-based version
|
File name |
File version |
File size |
Date |
Time |
Hashes |
Platform |
|---|---|---|---|---|---|---|
|
Sqljdbc.jar |
Not Applicable |
448,010 |
29-Apr-2010 |
06:56 |
Not Applicable |
Not Applicable |
|
Sqljdbc4.jar |
Not Applicable |
466,304 |
29-Apr-2010 |
06:56 |
Not Applicable |
Not Applicable |
|
Sqljdbc_auth.dll |
2.0.1803.209 |
172,464 |
29-Apr-2010 |
06:56 |
MD5: C8469387C4F00B56A6D01FB2A7EB4AA8 |
IA-64 |
|
Sqljdbc_auth.dll |
2.0.1803.209 |
86,448 |
29-Apr-2010 |
06:56 |
MD5: 12AB590CBA210BDF9D4BA05DB84F6144 |
x64 |
|
Sqljdbc_auth.dll |
2.0.1803.209 |
69,040 |
29-Apr-2010 |
06:56 |
MD5: C58C33FC8C1C4B05BFFA4F1CCC2A1856 |
x86 |
|
Xa_install.sql |
Not Applicable |
3,712 |
29-Apr-2010 |
06:56 |
Not Applicable |
Not Applicable |
|
Sqljdbc_xa.dll |
2.0.1803.209 |
251,824 |
29-Apr-2010 |
06:56 |
MD5: C312A65209D4E2454DA8E60D8A9DEB5D |
IA-64 |
|
Sqljdbc_xa.dll |
2.0.1803.209 |
130,480 |
29-Apr-2010 |
06:56 |
MD5: 1D7E2961C1C956BF792AE9F86C49EC26 |
x64 |
|
Sqljdbc_xa.dll |
2.0.1803.209 |
101,296 |
29-Apr-2010 |
06:56 |
MD5: 749C78CFF95D7A06D6671DCBA827F5CF |
x86 |
Itanium architecture version
|
File name |
File version |
File size |
Date |
Time |
Hashes |
Platform |
|---|---|---|---|---|---|---|
|
Sqljdbc.jar |
Not Applicable |
448,010 |
29-Apr-2010 |
06:56 |
Not Applicable |
Not Applicable |
|
Sqljdbc4.jar |
Not Applicable |
466,304 |
29-Apr-2010 |
06:56 |
Not Applicable |
Not Applicable |
|
Sqljdbc_auth.dll |
2.0.1803.209 |
172,464 |
29-Apr-2010 |
06:56 |
MD5: C8469387C4F00B56A6D01FB2A7EB4AA8 |
IA-64 |
|
Sqljdbc_auth.dll |
2.0.1803.209 |
86,448 |
29-Apr-2010 |
06:56 |
MD5: 12AB590CBA210BDF9D4BA05DB84F6144 |
x64 |
|
Sqljdbc_auth.dll |
2.0.1803.209 |
69,040 |
29-Apr-2010 |
06:56 |
MD5: C58C33FC8C1C4B05BFFA4F1CCC2A1856 |
x86 |
|
Xa_install.sql |
Not Applicable |
3,712 |
29-Apr-2010 |
06:56 |
Not Applicable |
Not Applicable |
|
Sqljdbc_xa.dll |
2.0.1803.209 |
251,824 |
29-Apr-2010 |
06:56 |
MD5: C312A65209D4E2454DA8E60D8A9DEB5D |
IA-64 |
|
Sqljdbc_xa.dll |
2.0.1803.209 |
130,480 |
29-Apr-2010 |
06:56 |
MD5: 1D7E2961C1C956BF792AE9F86C49EC26 |
x64 |
|
Sqljdbc_xa.dll |
2.0.1803.209 |
101,296 |
29-Apr-2010 |
06:56 |
MD5: 749C78CFF95D7A06D6671DCBA827F5CF |
x86 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
For more information about Microsoft JDBC Driver, visit the following Microsoft website:
Overview of the JDBC Driver
For more information about FIPS, visit the following website:
FIPS compliance with WebSphere Portal
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
