29 views

Description

No encryption support is present when using a Mid Server with JDBC DB2 database connection.

 

Steps to Reproduce

 

There is no support for an important feature:

It is not possible to create a JDBC connection (DB2) to an encrypted database.
No connections can be made to encrypted databases.

I created the problem because this is essential functionality.

Workaround

This is expected behaviour. This problem can be solved by specifying the required encryption properties in the data source:

  1. In the Data Source form, make the Properties field visible through context-menu/Configure/Form Layout.
  2. Specify any required properties using the following format: key1=value1,key2=value2.

These properties are then passed to the DriverManager whenever a connection is established.

For DB2, it might be helpful to use the suggestion below, where the properties as specified should work, assuming Username and Password are filled in the form.

securityMechanism=com.ibm.db2.jcc.DB2BaseDataSource.ENCRYPTED_USER_AND_PASSWORD_SECURITY,encryptionAlgorithm=2

Ref: https://www.ibm.com/support/knowledgecenter/en/SSEPEK_10.0.0/java/src/tpc/imjcc_cjvjcsen.html


Related Problem: PRB1276568

Seen In

Eureka Patch 11 Hot Fix 2

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-05-21 07:25:28
Published:2018-05-21