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 Future consideration
Created by Guest
Created on Apr 13, 2016

Add object name to Not Auth (Type 4) - Command Not Authorized

API related Not Authorized events give the object name in question. Command Not Authorized events do not. This appears to be a major omission. Request object type and object name be added where available, to the event. Clearly for some commands there will be no such data, e.g. REFRESH CLUSTER, but for many commands it would be very useful to have.

Idea priority Medium
RFE ID 86864
RFE Product IBM MQ
  • Guest
    Oct 19, 2017

    This essential information should be retrofitted to all current versions of MQ, not just some future version.

  • Guest
    Nov 8, 2016

    The responses need to be reviewed to be more intrusion detection friendly. Especially on a generic inquiry.
    A response to a q(*) or qs(*) should not contain any not authorized if there are objects that you are authorized for.

    If you are not authorized, but objects exist a single not authorized would do. If there are no objects that exist ( dis q(abc.*) a single no object (2085) is fine.

    The intent here is to allow access where access has been granted but to avoid enumeration of resources where the access does not exist or is partial.

  • Guest
    Jun 16, 2016

    Will consider for future release.