This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
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.
Do not place IBM confidential, company confidential, or personal information into any field.