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 Functionality already exists
Workspace DataPower Gateway
Created by Guest
Created on May 20, 2024

Security Enhancement: Enforce the API MIME type declaration at the Gateway level

We have had a security finding with regards to the APIC Gateway not blocking unexpected content-type requests.

Specifically the security finding was that all the endpoints allow a user to send data in XML format, even though the expected, default content type is json.
An authenticated user (with access to the APIs) could craft a malicious XML payload that, when parsed, may cause unexpected behavior by the application or perform an XXE attack.

Idea priority Medium
  • Admin
    Ulas Cubuk
    Jul 3, 2024

    Hi, thanks for raising this request. In order to enforce content-type checks you've been recommended to use parse assembly policy Therefore I am marking this as "Functionality already exist". If there are any requirements that are not covered with the parse policy, please open another Idea.

    If this is not working, this would be better handled as a product issue(raise this through support ) rather than an enhancement request.