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 API Connect
Created by Guest
Created on May 25, 2019

Request for encrypted basic authentication details swagger export/import from/to API manager

When API definition is downloaded as swagger definition from API management UI, it contains username and password in plain text.

Also, during swagger import for creating new API , it requires username and password in plain text for invoke/proxy policies.

There is a need to have these credentials details exported/imported as encrypted and not in plain text.

This is required as these swaggers are typically are required to be stored in code repositories such as github for CI-CD pipeline for automated API deployments.

From security perspective, it is better to have passwords in encrypted format rather than plain text when swaggers are loaded to code repository and when it's imported through apic cli into the management server.

Related case was created TS002214630

Idea priority Medium
RFE ID 133315
RFE Product IBM API Connect

Password is displayed as a string in YAML/Debug

When username and password are provided in invoke/proxy for testing an API, the password is being displayed as plain text in YAML file and Debug which is not secure.
over 3 years ago in API Connect 2 Future consideration