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.
DB2 JCC support for safkeyring in trustStoreLocation and keyStoreLocation properties
The is a requirement for the JCC on z/OS which is not an option under the operating system pulldown.
The DB2 JCC type-4 supports SSL connections to DB2 on z/OS. However, the keyStoreLocation and trustStoreLocation must currently be files in the file system. With a password that is saved in a configuration file.
The customer has decreed that all socket connections between client and server be over SSL connections. However, they want to keep all the security information for SSL connections in the SAF security database. This means that the jcc must support a key store and trust store of the format: safkeyring:/// and also support keyStorType property of JCERACFKS .
Support must be at the datasource level and not the JVM level to enable multiple DB2 subsystems to be accessed with different credentials.
Customer information can be provided but not in a public document.
Do not place IBM confidential, company confidential, or personal information into any field.