Skip to Main Content
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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.


Status Not under consideration
Created by Guest
Created on Oct 5, 2022

New amqrmppa process copy the keystore content from first amqrmppa process

According to the IBM Doc (https://www.ibm.com/docs/en/ibm-mq/9.0?topic=repository-refreshing-queue-managers-key), after changing the contents of a key repository, the queue manager does not immediately pick up the new contents until "REFRESH SECURITY", it is to prevents the situation where multiple running channels could use different versions of a key repository.

However, from the actual case, we see that newly created amqrmppa process will load the cert content from key repository again, that mean by whatever reason if the key repository is updated but "REFRESH SECURITY" not be done, there is a chance that different version of a key repository can be loaded by the queue manager. It violates the idea "As a security control, only one version of a key repository can be loaded by the queue manager at any time".

Suggesting for newly created amqrmppa process copy the keystore content from first amqrmppa process, so that only one version of a key repository is used in the QM.

Idea priority High
  • Admin
    Mark Taylor
    Reply
    |
    Oct 18, 2022

    While we will look at ensuring documentation is clear on the capability, this is not something we would plan to implement - in fact, there are more requirements around making the refresh more automatic like other attributes.