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 Delivered
Workspace App Connect
Created by Guest
Created on Jan 14, 2020

Option for WS-Security with Basic Auth header

The SOAPRequest node uses the Security Profile property (in the BAR editor) to specify the security credentials for the outbound request. If a traditional request, this populates the Basic Auth header (ex. Authorization: Basic YWRtaW46cGFzcw==). If you use WS-Security, this populates the UsernameToken of the WSSE header.

As this field represents one or the other, you cannot specify both using the SecurityProfile defined. As a workaround, you can use the option for the WS-Security header and then use ESQL to manually set the Basic Auth header (ex. SET OutputRoot.HTTPRequestHeader.Authorization = 'Basic ' || BASE64ENCODE(username || ':' || password);). But this does not read from the SecurityProfile, so the user/password must be read in plain text or pulled from an external resource.

Idea priority Medium
RFE ID 139423
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Reply
    |
    Aug 1, 2023

    ACEv12.0.9.0 has now added support to access credentials stored in the vault from within JavaCompute node code: https://community.ibm.com/community/user/integration/blogs/ben-thompson1/2023/07/04/ace-12-0-9-0

  • Guest
    Reply
    |
    Aug 10, 2020

    Thank you for raising this RFE, which we agree would make a good enhancement for the product. ACEv11 unified the concepts of Security Policy Sets and Bindings along with other product concepts as part of the introduction of Policies inside Policy Projects and the replacement of configurable services from the latest version of the product. With the introduction of the vault and mqsicredentials command which encrypts user credentials when stored on the file system, we have another building block in place which could potentially help here. The next evolution of these aspects could be a secure ability to access credential information from within code in a flow (which would help with the ESQL aspect of the RFE mentioned) - but we also acknowledge deeper changes to security profiles to allow for more dynamic mapping use cases could be helpful to some users. The status of this RFE is updated to Uncommitted Candidate.