Skip to Main Content
Cloud Platform

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 portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Future consideration
Created by Guest
Created on May 30, 2017

Rational Integration Tester: While importing SOAP/WSDL API's from the IBM APIConnect Registry missing the client ID and Secre

Rational Integration Tester: While importing SOAP/WSDL API's from the IBM APIConnect Registry missing the client ID and Secret.

For the REST API's, the client-id and client-secret are added to the swagger (REST API) definition in API Connect. That is how those security header information are known and automatically added after importing such REST API in RIT.

In opposite, a SOAP API does not contain such security information after being added to API Connect. Because the information is not in such API WSDL, RIT does not automatically add it and that would need to be added manually.

That would be a request for enhancement to have RIT handle such additional API Connect security header information in case of a SOAP API.

Idea priority High
RFE ID 105818
RFE URL
RFE Product Rational Test Workbench
  • Guest
    Jun 9, 2017

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.