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 Under review
Workspace API Connect
Created by Guest
Created on Jan 12, 2023

Username and Password properties of Invoke policy || can we configure them in APIC and pass them as context variable to the APIC flow || API Connect V10

We want to store/configure Username and Password needed for basicAuth to call a backend securely somewhere inside API Connect.

We will use these values dynamically using a context variable and pass them to INVOKE policy properties of an API while calling a backend.

By doing so we can avoid republish/redeployments of products when there is a change in the security credentials and can also avoid exposing backend(server) credentials in the source file(json/yaml).

Idea priority Urgent
  • Guest
    Mar 22, 2023

    The ability to specify context variables for the username and password for backends secured with Basic Auth also greatly simplifies using environment-specific values. We use catalogs to differentiate environments, and the ability to use catalog-specific properties to specify these credentials would be helpful. Without this ability, we must generate the Authorization header in a separate Gateway script, or abandon the Invoke policy altogether and use URLOpen to access the back end. Both are significantly more complex.