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 Future consideration
Created by Guest
Created on Feb 1, 2019

Enforce AMS configuration from Client

The aim of Advanced Message Security is to provides a high level of protection for sensitive data flowing through the IBM MQ network.

If customer A setup MQ AMS config on the client :
SSLKEYR=
and
keystore.conf

This will have the effect that if the MQServer is configured with an AMS policy, the message will be encrypt on client side.
BUT
if the MQServer has no policy, even if the client side setup his AMS config, it wont apply encryption.

As the target of AMS is enforcing that MQAdmin or any user without the private key can send the encrypted message or alter it, if the MQAdmin just has to remove the policy to have no AMS actvated, it would be useful that the MQClient refuse to send the message or set a warning or an option to enforce the need of the policy.

Idea priority High
RFE ID 129594
RFE URL
RFE Product IBM MQ
  • Guest
    Reply
    |
    Jun 26, 2019

    This is something we will consider implementing in a future release.