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 Under review
Workspace Db2
Components Security
Created by Guest
Created on Mar 24, 2022

Monitor element, or audit/diagnostic utility, that identifies TLS version of an active DB2 LUW connection (application or session)

We are on the path now to enforcing TLS 1.2 for all SSL at my company. To make it easier for developers, at this point we have enabled TLS 1.2 but are continuing to allow TLS 1.0 and 1.1 database connections. We are hesitant to simply disable TLS 1.0 and 1.1 in production, as inability to connect to the database could cause a production outage. We would like to identify the application clients that are still backlevel at TLS 1.0/1.1, notify developers and application engineers so that they can fix their jdbc client configurations first before flipping the TLS 1.2 enforcement switch. Do you have any idea if there are utilities out there that can display the TLS version in use by an active connection? We are aware of the ability of openssl to identify the TLS version compliance of an open port, and that’s great for confirming that the DB2 SSL listener can support the protocol. What we are interested in is auditing which app servers are still talking to DB2 via TLS 1.0/1.1. With the recent emphasis in the industry on security, I am surprised that IBM still does not have a utility to accomplish this.
Needed By Quarter