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 Delivered
Workspace DataPower Gateway
Created by Guest
Created on Oct 10, 2016

Allow CN/DN only validation on back side connections

Currently the DataPower Validation Credential allows configuration for checking a certificate and/or its issuers on back side connections. There are times when it is advantageous to check only the CN or DN of the back side connection's certificate in combination of the issuer.

Ideally, this match would be a PCRE list match (somewhat like the processing rule matching action when PCRE and OR are enabled).

Idea priority Medium
RFE ID 95607
RFE Product IBM DataPower Gateways
  • Admin
    Ulas Cubuk
    May 8, 2024

    In TLS client profile, you can set the validate server hostname property to validate the hostname in the server certificate and use the Hostname validation flags property on the Advanced tab to fine-tune the validation methods and settings during the handshake.

    Hopefully this meets your requirement, otherwise please feel free to open another idea.

  • Guest
    Jan 24, 2017

    I suspect we could settle for enforcement of RFC6125 6.4 if the exact cert is not present for validation. There are so many requests about this on DeveloperWorks and it is apparently a big issue to many in charge of security compliance. They think if DP doesn't follow the RFC, it is "vulnerable", and sometimes we can't convince them otherwise.

    So, the simplest form of this would be:

    1. In the crypto profile, just have an optional checkbox (default is OFF) "Enforce RFC6125 6.4" or "Enforce Domain Name Checking" or *something*.
    2. If that is on, DataPower would match the CN/SANs of the certificate with that of the request.