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,
Post an idea
Upvote ideas that matter most to you
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.
Enable db2 to use SVCENAME only as a resync port, not allowing connections to this port
We expect that credentials are properly secured on the network. Db2 LUW will allow part of these credentials to be not properly secured in certain situations. Due to this, we need to convert all of our connections to be SSL connections. But in the situation where you have 2 phase commit workloads, Db2 LUW needs to have a SVCENAME port available. By making this port available, it allows users to connect to this db2 with an non-SSL connection and mis-configured client can allow the credentials to not properly be secured. This request is to prevent any non SSL connections from occurring.
We need this to maintain integrity with our security policies. Otherwise we are enabling our users of Db2 to potentially do actions that put them outside of the expected policy.
Do not place IBM confidential, company confidential, or personal information into any field.