IBM DB2 provides several options when it comes to security. IBM refers to these options as Security Mechanisms. Some of them are listed below:
CLEAR_TEXT_PASSWORD_SECURITY (3)
USER_ONLY_SECURITY (4)
ENCRYPTED_PASSWORD_SECURITY (7)
ENCRYPTED_USER_AND_PASSWORD_SECURITY (9)
KERBEROS_SECURITY (11)
ENCRYPTED_USER_AND_DATA_SECURITY (12)
ENCRYPTED_USER_PASSWORD_AND_DATA_SECURITY (13)
PLUGIN_SECURITY (15)
ENCRYPTED_USER_ONLY_SECURITY (16)
- See more at: http://www.techcrony.info/2011/06/14/nitingautam/mainframe-cics-db2-security-mechanism-not-supported/#sthash.K42WvuCD.dpuf
Follow these steps for connecting to an IBM DB2 that is secured by one of the above security mechanisms:
- Install IBM JDK 1.7 or later in the machine where ETL Validator Server is running. IBM JDK comes with the required JCE providers to use the appropriate security mechanism
- Create a new Data Source connection in ETL Validator and choose the 'Custom' option. This will allow for a custom JDBC URL with the Security Mechanism to be given in the connection as shown in an example below.
jdbc:db2://SERVERNAME:50000/DB:securityMechanism=7;