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 Not under consideration
Created by Guest
Created on Sep 17, 2015

MQ Appliance LDAP Authentication Retention

The new IBM MQ Appliance with IBM MQ Advanced has a feature which allows LDAP for user authorization and authentication. Authoriization for each user is held and cached after each MQ connection and retained for all MQ API calls. However on Authentication is not cached or retained after each connection. Which means that if an MQ Connection to an MQ Object is lost an LDAP query is required for each API all if the application drops the connection due to security and privacy requirements.

Idea priority High
RFE ID 77153
RFE Product IBM MQ
  • Guest
    Dec 15, 2023

    We recognise that this is a valid requirement. However it doesn't fit with our delivery plans for the next couple of years.

    As a result we are declining this Idea. While declined the Idea can still be voted, and commented, upon.

  • Guest
    Oct 22, 2015

    We will consider this for the future, but as it would require keeping in qmgr memory a copy (albeit encrypted in some fashion) of the user's password to revalidate the connection, this is not something that is very attractive.

  • Guest
    Oct 15, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM MQ

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM MQ