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 DataPower Gateway
Created by Guest
Created on Jul 1, 2022

checkbox on tls profiles for tls-info logging

TLS information is quite important, especially if a customer needs to change their supported versions and/or supported ciphers and wants to know which peers do use which TLS version and ciphers, respectively. DataPower provides a context variable to access this information but to log this information you to add an action to your processing rule, either an xfrom action or a gateway action. This is not a convenient solution for several reasons: 1) logging breaks streaming (at least to my knowledge) 2) a processing rule might not be available due to "passthrough" 3) the TLS handshake is usually done by the front side handler i.e. there is no possibility to log anything in the error case I therefore suggest to add a checkbox "activate TLS info logging" to all TLS profiles (client, server, sni server). Once enabled (default is disabled), it would log the used TLS version and cipher suite (preferably on the customizable severity level). In an error case (TLS handshake was not successful due to a mismatch of the version and/or cipher suite) it would be helpful to log the supported TLS version and the list of advertised ciphers. And to give one on the top, it would be helpful to see the subject DN of the peer.
Idea priority Medium