Integration
This is an IBM Automation portal for Integration products. 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 updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - Integration
Product - IBM MQ
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Connectivity and Integration
Product - IBM MQ
IBM uses a JKS because that is the Java standard. It is therefore the case that *any* non-MQ Java application needing a keystore has either solved this problem or also has to provide a password. How has the submitter solved this for other Java use cases? for that matter, how have non-MQ Java users in general approached this and are those solutions useable for MQ?
Also, does the submitter wish for this functionality to be provided in a non-IBM JRE? Is there a list of which functionality works only in an IBM JRE that is already being tracked?
Last I heard, IBM was reluctant to distribute GSKit with pure-Java client solutions. Has that changes and would this be a GSKit implementation? Or would it be Java classes that know how to manipulate a KDB? Because a requirement to generate the KDB and keys in one place, them move it to the server where GSKit isn't installed would leave copies of the keys all along the distribution path if not managed with a decent PKI tool. But a pure-Java GSKit would not have the FIPS and other certifications that the compiled GSKit does.
This seemingly simply requirement turns out to have a LOT of texture to it. If implemented, please be sure to document it in sufficient depth as to respond to all the concerns I've raised above.
This appears to be technically possible, so is something we could consider for a future version of MQ.