Skip to Main Content

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Created by Guest
Created on Jun 8, 2021

Enhance the IBM MQ managed .NET Core client to connect to an OpenShift queue manager with mutual TLS

System: IBM RPA
Actor: Dev team

IBM RPA is a new offering built ontop of the recently aquired WDG Automation product. As part of the "IBMifying" process we are porting the backend API server (and other services) to OpenShift. Part of this work involves connecting a managed .NET Core client to an IBM MQ queue manager hosted in OpenShift and configured for mTLS communication. The issue is the managed .NET Core client is not sending the Hostname SNI header with the TLS certificate, so the OpenShift route is unable to redirect the connection request to the queue manager service.

The SNI Hostname header is not being set from a managed .NET Core client with mutual TLS configuration. This is due to a limitiation in the managed .NET environment.

Attempting to connect to a queue manager in OpenShift via a Route configured to redirect on SNI Hostname instead redirects the queue manager connection to the default landing page as the managed .NET MQ client is passing an asterisk ("*") instead of the hostname.

The connection information is as follows when testing on a Java queue manager application (note: the host_name):

listening on 2456...
Reading TLS Header. Aiming for 5
Address 0 1 2 3 4 5 6 7 8 9 A B C D E F
------- -------- -------- -------- --------
000000: 16030300 9C .....
------- -------- -------- -------- --------
TLS Header read in 1
Reading TLS record. Aiming for 161
Address 0 1 2 3 4 5 6 7 8 9 A B C D E F
------- -------- -------- -------- --------
000000: 16030300 9C010000 98030360 B0E6A542 ...........`...B
000010: 8EC8E601 65F1B8D0 86C7B139 9DF1C965 ....e......9...e
000020: 9E357FCB 4E4A4033 D2B22500 002C00FF .5..NJ@3..%..,..
000030: C02CC02B C024C023 C00AC009 C008C030 .,.+.$.#.......0
000040: C02FC028 C027C014 C013C012 009D009C ./.(.'..........
000050: 003D003C 0035002F 000A0100 00430000 .=.<.5./.....C..
000060: 00060004 0000012A 000A0008 00060017 .......*........
000070: 00180019 000B0002 0100000D 00120010 ................
000080: 04010201 05010601 04030203 05030603 ................
000090: 00050005 01000000 00001200 00001700 ................
0000A0: 00 .
------- -------- -------- -------- --------
Full TLS Record read in 1
Record version: TLSv1.2
Hello version: TLSv1.2
Found SNI of: type=host_name (0), value=*

Idea priority High
RFE ID 150935
RFE Product IBM MQ
  • Admin
    Mark Taylor
    Jul 27, 2021

    This is available in MQ 9.2.3 and will be provided via APAR IT37223 for the V9.2 LTS release.