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 Nov 30, 2023

Enable http/bearer security in RESTRequest nodes calling APIs defined by OpenAPI V3

OpenAPI V3 updated, from Swagger V2,  the available security schemes that can be defined for a Rest API.  Most notable a securityScheme of type http can use a scheme of 'basic' or 'bearer'. There is also the apiKey type.  It appears that ACE V12 only recognizes the http/basic and apiKey schemes where the RESTRequest node will build the appropriate HTTP Header (or Query) parameters to satisfy these calls, provided that the Username/Password and/or APIKey information is available to the flow via credentials, identity propagation, or set in the LocalEnvironment. 

We are finding that more and more, the APIs that we call from ACE are using bearer authorization with a JWT.  To enable this to work, we need to modify the OpenAPI document to add an apiKey securityScheme definition were we set the key to be a header parameter named 'Authorization' and then set the JWT as the LocalEnvironment.Destination.REST.Request.APIKey value.  While this works, it is inconvenient to have to do this "trick" every time we import an update to the API. 

We would like to have the RESTRequest node fully support the identifying and using a http/bearer securityScheme, if defined in the OpenAPI document.  The value for the bearer token should come from LocalEnvironment.Destination.REST.Request.Bearer.  (or BearerToken).   The node should also examine value of the token and append 'Bearer ' to the beginning if not already present. 


Idea priority Medium
  • Admin
    Ben Thompson
    Jan 12, 2024

    Hi Steve ... Thank you for taking the time to raise this suggestion, which we agree would absolutely be of benefit. As luck would have it, this functional area has recently been discussed by the engineering team in the context of some work we have been doing analysing some niche areas where Designer flows and Toolkit flows operate slightly differently. We're keen to drive greater consistency in to our architecture (hence the discussion I refer to above) aside from the core benefit that you would obviously inherit by having us supply a solution to this enhancement idea. So we currently have a positive outlook for this area. Status of the idea is updated to Future Consideration.