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 Jul 18, 2022

MQSeries caching authentication info

when MQ AUTHINFO is set to LDAP , there seems to be a performance issue when MQ authenticates user credential.

Could you please consider implementing a mechanism such as caching option to improve the performance and minimize the performance overhead ?

We have case TS009966433 open for this

Idea priority High
  • Admin
    Mark Taylor
    Aug 2, 2022

    There is already a lot of caching in the queue manager for LDAP authorisations and knowledge of users to reduce the searches. But the queue manager does not, and will not, try to cache user authentication with passwords - there might be all kinds of processing being done in the LDAP server to validate the user of which the queue manager is unaware. Any authentication mechanism is expected to be reliable and performant; there are timeouts available that will reject connection requests if the LDAP server is too slow responding.