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

Add possibility to modify the default "x-client-certificate" header

Hello IBM;

We have an API with "application authentication" enabled and the source is set to header:

x-ibm-configuration:
application-authentication:
certificate: true
application-authentication-source:
- header


The expected header name is:"x-client-certificate" and it cannot be modified.

Could this name be configurable?


Amazon Web Services is implementing the ALB with mTLS Passthrough since March 2024, but the ALB is sending the certificate in the "x-amzn-mtls-clientcert" header. This header is not configurable at AWS side either, so it is not possible to take advantage of this new feature:


https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-mtls-for-application-load-balancer/#:~:text=X%2DAmzn%2DMtls%2DClientcert%3A%C2%A0


https://docs.aws.amazon.com/elasticloadbalancing/latest/application/mutual-authentication.html#:~:text=the%20following%20header.-,X%2DAmzn%2DMtls%2DClientcert,-HTTP%20headers%20for


Thank you.

Idea priority Urgent
  • Admin
    Ulas Cubuk
    Reply
    |
    Aug 30, 2024

    HI, thanks for raising this request. Although the header name is not exposed to APIM, it is editable directly from DataPower. https://www.ibm.com/docs/en/datapower-gateway/10.6.0?topic=commands-api-mutual-tls-header-name

    Therefore, modifying api-mutual-tls-header-name attribute with a value other than the default X-Client-Certificate value via gwd_extension might be a possible solution to test for your environment. (see: https://www.ibm.com/docs/en/api-connect/10.0.8?topic=type-api-definition) For example, using an override map like below which will change X-Client-Certificate to a custom header name for an API (such as myapi:1.0.0)

    { "api-definition":{ "_global":{ "_instance":{ "myapi:1.0.0":{ "api-definition":[ "api-mutual-tls-header-name my-custom-tls-header" ] } } } } }

    Given that there is a possible solution, we are closing the request for now. We hope this meets your requirement if not please comment here or open a new Idea. This idea will be kept in IBM's ideas repository and may still be voted on.