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 Feb 19, 2024

Remove requirement for AUTHSERV security refresh after a user's group permissions are updated in LDAP repository

When using LDAP(S) to manage group access and then permissioning MQ resources by group membership, the authorization cache will never update from the LDAP repository until the "REFRESH SECURITY TYPE(AUTHSERV)" is run on the QM. This introduces a needless manual step to the otherwise decoupled permission model.

Example: TopicA is permissioned with PUBLISH rights for LDAP group "X" and TopicB is permissioned with PUBLISH rights for LDAP group "Y".
User1 initially has membership of group X but not group Y and happily uses TopicA for some period (e.g. months). Later, User1 is granted membership of group Y in the LDAP repository, however they are unable to publish to TopicB until the MQ administrator runs the above refresh security command for the QM. This seems to be because when User1 first connected for TopicA, their group memberships were cached by the authorization service and this authorization service is never updated for a given user.

Some suggestions for improvement:

  • A "lifetime" associated with a user's cache entry, so it is periodically refreshed from the LDAP repo when the user interacts with MQ

  • The ability to schedule a refresh of the whole authorization service for a given QM

Idea priority Medium
  • Admin
    Mark Taylor
    Mar 4, 2024

    Refreshing the internal security cache is not unique to LDAP - the same approach has to be taken for OS-based usersThis is not something we would plan to implement in MQ; instead we would recommend using something like a cron-job or similar, to schedule a refresh at times you know the qmgr is not busy. Or link it to your group-membership change processing.