Do not use the com.sun.net.ssl.internal.ssl.Provider

This rule flags the use of com.sun.net.ssl.internal.ssl.Provider class. This class should not be used. Instead use com.ibm.jsse2.IBMJSSEProvider2 .

This rule also flags the use of the following classes from the com.sun.net.ssl.internal.ssl package. These classes should not be used. Instead use classes from the com.ibm.jsse2 package.

• com.sun.net.ssl.internal.ssl.Debug
• com.sun.net.ssl.internal.ssl.SSLServerSocketFactoryImpl
• com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl

The automated fix will make these changes:

• References to the com.sun.net.ssl.internal.ssl.Provider class are changed to com.ibm.jsse2.IBMJSSEProvider2 .
• References to the Provider class are changed to IBMJSSEProvider2 .
• References to the com.sun.net.ssl.internal.ssl.Debug class are changed to com.ibm.jsse2.Debug .
• References to the com.sun.net.ssl.internal.ssl.SSLServerSocketFactoryImpl class are changed to com.ibm.jsse2.SSLServerSocketFactoryImpl .
• References to the com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl class are changed to com.ibm.jsse2.SSLSocketFactoryImpl .

Copy the custom configuration to your application build file to enable the fix automation.

For example, code fragments such as

are changed to

You may still have a number of changes to make depending on how the com.sun.net.ssl.internal.ssl.Provider is used. Use the Eclipse Java problem markers to help you work through additional changes needed because of the differences between com.sun.net.ssl.internal.ssl.Provider and com.ibm.jsse2.IBMJSSEProvider2 . In particular some differences are:

• The com.sun.net.ssl.internal.ssl.Provider includes two constructors which take arguments. The com.ibm.jsse2.IBMJSSEProvider2 does not include similar constructors.
• The com.sun.net.ssl.internal.ssl.Provider includes the method isFIPS . The com.ibm.jsse2.IBMJSSEProvider2 does not include this method.

For additional information related to this rule, see:

• IBMJSSE2 Provider