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 Submitted
Workspace MQ, MQ Advanced & MQ Appliance
Created by Guest
Created on Oct 20, 2026

RELATED IDEAS

IBM MQ Web Server (Liberty): Log in and authorize with optional extra LDAP attributes, and add a control to block message-content viewing for read-only (MQWebAdminRO) console users

  1. Only one LDAP identity attribute: The MQ Web Server and the queue manager's LDAP authorization (AUTHINFO type IDPWLDAP) each accept only one attribute for user identity. Client application connections authenticate against LDAP with sAMAccountName usually, so that attribute has to be set in the queue manager's AUTHINFO object (USRFIELD/SHORTUSR). However, MQ Web Console users are identified by their Employee ID (employeeID) or any other parameter, which is their primary, permanent identifier. Because only one attribute is allowed, we can't support both identity types together. Users can't log in to the MQ Console with their Employee ID and have that identity carried through to MQ role mapping and queue manager authorization, while client connections keep using sAMAccountName. It is good to provide multiple optional parameter supported for LDAP authentication.

  2. Read-only users can view message content: Users with only the MQWebAdminRO role can browse queues and see full message payloads in the MQ Console exposing business data. Because console admin operations run as the user that started the mqweb server, queue manager OAM permissions (such as removing +browse) can't restrict this. It is good to have finer-grained role for MQWebAdminRO as well so that we can restrict few of the access types i.e browsing messages from the queues on web console.

We would suggest if these 2 new features can be added to IBM MQ as soon as possible.

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.