Skip to Main Content
IBM Data and AI Ideas Portal for Customers

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Created by Guest
Created on Jun 29, 2018

Oracle Native Network Encryption in MDM 11.6 Advaced Edition

PMR: TS000948369
MDM Version: MDM V11.6
DB Version: Oracle 12 C
We are using Oracle Native Network Encryption
When we enable OAS at DB level with ‘SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER=‘ as SHA256, the application is not able to connect to DB and the MDM JDBC/ODBC connectivity test is failing.
When we change the “CRYPTO_CHECKSUM” Parameter from SHA256 to SHA1 application is working as expected.
From the article, currently the application supports “MD5 | SHA1 | SHA1, MD5”. It seems SHA1 is deprecated; also MD5 is less secured than SHA1, could you please provide the list of “DataIntegrityTypes” that MDM application supports.
As SHA1 is deprecated due to its vulnerabilities, we wonder why it's still in use by this product/application.
  • Admin
    Marcus Boone
    May 16, 2019

    We have opened an enhancement request with our supplier of third party drivers and will update status accordingly.