Skip to Main Content
Integration


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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - 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 7, 2024

Disable swagger

We kindly request the development of a feature that allows Swagger to be disabled. This could be achieved programmatically, so that we could decide our internal logic the conditions it should be available and exposed, for instance, depending on if it’s running in Production or Staging.

Idea priority Medium
  • Admin
    Ben Thompson
    Reply
    |
    Nov 26, 2024

    Thank you for raising this idea. We also note the further information that was provided through the Service Case which suggests that the motivation for this requirement is really driven from a security point of view related to a desire for different levels of exposure form different environments (dev versus test versus prod etc). We accept the requirement on the basis that some users might want to NOT expose the Swagger document / Open API document via the administration API when the REST API is deployed into a production setting. We think this is likely a low-priority item but we are open to feedback from the community, and if that is forthcoming we understand how it could be implemented whilst maintaining back compatability for the current product externals. Status updated to Future Consideration.