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.


Add a new idea Subscribe
Status Under review
Workspace MQ, MQ Advanced & MQ Appliance
Created by Guest
Created on Aug 28, 2024

RELATED IDEAS

MQ Console is not accessible when Openshift ingress and associated urls use the same certificate

We are running MQ Operator v3.2.3, SC2 image 9.4.0.0-r3 on CP4I 16.1.0 on Openshift 4.14. Currently when the MQ Console is accessed on any browser, it breaks and displays "not found" error.

MQ Console is not accessible when Openshift ingress and associated urls such as keycloak and MQ console use the same certificate. We are using the same/common wildcard certificate for openshift ingress, keycloak url, MQ Console which makes it easy for rotating the single certificate which is kept in the Azure Key Vault, we have a solution to sync certificates as Openshift secrets. We are not in a position to order a separate certificate just for the MQ Console as a fix.

The workaround is to disable HTTP2, but we need a permanent fix. 

The permanent fix would be to terminate TLS at the openshift router so it can pass the traffic around appropriately I think.

Idea priority High

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.