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
Workspace App Connect
Created by Guest
Created on Nov 6, 2019

use security identity on mqsideploy

mqsideploy has -I option to specify remote deployment in the form tcp://user:password@hostname
This exposes the user and password to discovery via an OS process listing (ps -ef). Requested enhancement is to allow a security identity to be provided on the mqsideploy command. mqsideploy will need to be changed to ready the encrypted user name and password from the security identity and use these to request authentication via the remote Integration Node.
The security identity would be created in the usual way with mqsisetdbparms. The same concept should be extended to any command requiring authentication, i.e. web admin security enabled.

Idea priority High
RFE ID 137915
RFE URL
RFE Product IBM App Connect (formerly Cast Iron)
  • Guest
    Reply
    |
    Nov 6, 2020

    RFE Review. Thank you for taking the time to raise this RFE and apologies it has been in submitted status for so long. Although we understand the request, our initial reaction is that in general we suspect users would not be so inclined as to want to use the IIB/ACE options (mqsisetdbparms and mqsivault) for storing userid/password on client machines doing remote mqsideploys. Increasingly we expect users to more likely move towards pipelines for generating "baked" container images where mqsideploy is not needed at all, or potentially smaller "build" images for remote deployment as part of a wider framework providing secure store of data outside the walls of the product. That said, we are open to the suggestion if users agree there would be utility in this request, because as noted we certainly have a defined means of storing the data securely in ACE. Status of the RFE is updated to Uncommitted Candidate.