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 Not under consideration
Created by Guest
Created on May 20, 2013
Merged idea
This idea has been merged into another idea. To comment or vote on this idea, please visit MESNS-I-7 Provide information to applications to allow them to validate that AMS was active..

Expose signer and signature information from MQ AMS to applications Merged

AMS enables messages to be signed by the sender, and the policy enforces that only signed messages can be received. However, the receiver does not have access to information about who signed the messages.

Please add the ability for applications to query the information related to signed messages when AMS is in use. This could for example be implemented as message property information using reserved property names (MQAMS_SIGNER_DN, MQAMS_CERTIFICATE_CHAIN, MQAMS_SIGNATURE for example).

The properties supported should allow identification of the message sender (signing certificate DN) and sufficient information to allow the applicating to implement non-repudiation. The non-repudiation requirement is more complex, but I think can be managed if the certificate, certificate trust chain and the message signature are available. It might be that the full signed message content needs to be presented to the application on request.

The data storage requirements for non-repudiation would be an application responsibility, not MQ or AMS.

In order to re-validate the message subsequently, an API which allows a message to be presented to AMS from an application, instead of from a queue would be needed.

Idea priority Medium
RFE ID 35058
RFE URL
RFE Duplicate of 35059
RFE Product IBM MQ
  • Guest
    Reply
    |
    Jul 23, 2019

    Closing as dup of 35059

  • Guest
    Reply
    |
    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