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 Submitted
Created by Guest
Created on Nov 3, 2026

Add an intermediate MQ Console / REST role between MQWebAdmin and MQWebAdminRO

The MQ Console and administrative REST API offer only two authorisation levels: MQWebAdmin, which grants full administration of every connected queue manager, and MQWebAdminRO, which is read-only. There is nothing in between.

Application teams need a small set of operations on their own queues in non-production — browse messages while debugging, drain a queue after a bad deployment, check channel status. None are possible under MQWebAdminRO, and MQWebAdmin is far too much: under REST API v3 it permits arbitrary MQSC against every connected queue manager, because the typed per-object resources are superseded by a single generic endpoint, POST /admin/action/qmgr/{qmgrName}/mqsc, that accepts any command in the request body.

So the practical choice today is to over-grant full administration, or to deny self-service and absorb routine requests as platform-team work.


WHAT WE ARE ASKING FOR

A third role granting the messaging REST API plus read-only administrative access, while denying the administrative mqsc resource. The messaging API is already a separate endpoint family, so this needs no new authorisation machinery.


ENDPOINTS IT SHOULD REACH

GET /ibmmq/rest/v*/messaging/qmgr/{qmgrName}/queue/{queueName}/message — browse

DELETE /ibmmq/rest/v*/messaging/qmgr/{qmgrName}/queue/{queueName}/message — destructive get, drain

POST /ibmmq/rest/v*/messaging/qmgr/{qmgrName}/queue/{queueName}/message — put a test message

The CLEAR QLOCAL, DISPLAY QLOCAL and DISPLAY CHSTATUS verbs, currently reachable only through the generic mqsc endpoint

 

ENDPOINTS IT MUST NOT REACH

DEFINE and DELETE of any object, ALTER QMGR, START and STOP CHANNEL, SET AUTHREC, SET CHLAUTH, REFRESH SECURITY — all of which route through that same single mqsc endpoint.


We are also filing a companion idea for per-queue-manager role scoping. The two compound: an intermediate role still applies application-wide, so without scoping it would grant these operations on every connected queue manager.

Idea priority Medium