Skip to Main Content

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portal, please send email describing the issue to for resolution. For more information about IBM's Ideas program visit

Status Future consideration
Workspace App Connect
Created by Guest
Created on Mar 29, 2012

Modify WMB 7 to use of multiple UserIDs within the same Execution group Kerberos setting

ADESA is implementing Kerberos to the Webservices hosted on various platforms (Broker 7.0.0,3, .NET, IBM WAS 7.0 etc)

The kerberos accounts used for these webservices will be different and we are planning to have different kerberos account for different application

Currently the bottleneck is that Broker on AIX 7.1 ( IBM P770) allows only configutaion of singgle user per Execution group in kerberos registry

We have multiple message flows deployed in an Execution group and we will have to invoke different webservices

We need IBM to extend the kerberos registry in broker to allow multiple UserID

Idea priority High
RFE ID 20871
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Jan 15, 2021

    RFE Review. Apologies for the time this enhancement request has been in status Uncommitted Candidate. Unfortunately we have not yet managed to prioritize this feature, and despite it not receiving any additional votes during its lifespan it remains a valuable future area of potential enhancement for more modern product versions. Status of RFE is maintained as 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

  • Guest
    Jun 25, 2012

    Can I get an update on this RFE?

  • Guest
    Jun 20, 2012

    IBM has released Fixpack recently . Will WMB v7.0.0.4 include the changes so that we can add multiple kerberos account/realm to a execution group ?

  • Guest
    Jun 1, 2012

    Thanks for raising this requirement. As you've observed, there is currently a restriction of one user ID per execution group per Kerberos realm. We have done some investigation into the engineering effort required to remove this restriction. Given the size of effort required, it may be too significant a change for the 7.0 release, so would look to schedule this work into a follow-on release or fixpack. In the mean time, you'll need to use different execution groups for each target user ID.

  • Guest
    Apr 9, 2012

    Can I get an update on this RFE?