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 Under review
Created by Guest
Created on Jul 14, 2025

Implement per-channel SSL/TLS certificate refresh capability to eliminate queue manager-wide client disconnections during certificate updates.

Currently, when onboarding new clients or updating certificates in IBM MQ, the refresh security type(ssl) command disconnects ALL existing SSL connections across the entire queue manager. This creates significant operational challenges:

  • Service disruption: All SSL-enabled channels disconnect simultaneously, causing application outages
  • Client impact: Existing clients experience unnecessary connection drops even when their certificates remain valid
  • Operational overhead: The all-or-nothing approach makes certificate management disruptive and forces maintenance windows

With the industry moving toward dramatically shorter certificate lifespans (the CA/Browser Forum has officially voted to reduce TLS certificate validity to 47 days by 2029 ), certificate refresh operations will become exponentially more frequent. 

The enhancement should provide two levels of granular SSL refresh control:

  • Channel-specific refresh: Enable refresh security type(ssl) channel(CHANNEL.NAME) to refresh SSL context only for specified channels, leaving other channels unaffected
  • Intelligent refresh timing: Implement automatic SSL refresh when channels are inactive or during natural restart cycles, eliminating the need for forced disconnections and provide an attribute of the channel to identify channel that need to be refreshed manually.
Idea priority Medium