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 Future consideration
Workspace App Connect
Created by Guest
Created on Mar 22, 2013

Allow user to configure multiple security policies using one SOAP input node.

System: Enterprise common services.

Actor: Partners and customers.

Description: ADESA needs to implement many commonly used Webservices using SOAP input node with security enabled in message broker to allow various applications to access them. Part of the requirement is to allow multiple security policies so that the consumer application can call using their native security policy.
With the current version of message broker (v7.0.0.3) we tried to configure WS-Security using username/password token and Kerberos ticket. The configuration allowed the application to use both security policies together and did not choose one based on the incoming message but the requirement is to allow the consumer to call using any one of the security policies and not both.
With a PMR with IBM we learnt that this feature is not supported in the broker yet and we would like to request this feature enabled so that we do not have to expose multiple soap input nodes and different endpoint for each security policy.

Idea priority High
RFE ID 32714
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Sep 20, 2020

    RFE Review. Apologies for the length of time this RFE has been in the status of Under Consideration. Whilst probably not a great inhibitor to the vast majority of users, who would typically define more than one SOAPInput node in the flow and attach a separate security profile to each one, we acknowledge that implementation of this feature would improve the product. We note that this RFE has not gathered votes over the years. Given this profile, it is unlikely that priority will be given to this RFE soon, but we will keep it open for now and continue to monitor. Status of this RFE is updated to Uncommitted Candidate.

  • Guest
    Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB