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 Submitted
Workspace DataPower Gateway
Created by Guest
Created on Jul 15, 2026

Runtime Access to Backend TLS Certificate/Public Key and Support for Standalone Public Keys in IBM DataPower

Currently, IBM DataPower validates the backend server certificate during the TLS handshake using a TLS Client Profile and Validation Credentials. However, there is no supported way to access the backend TLS certificate or its public key from GatewayScript or XSLT in processing policy for additional runtime validation (for example, certificate/public-key pinning, fingerprint validation, or custom security checks).

We request that DataPower expose the backend TLS certificate and its public key to processing policy as an service variables or metadata after the TLS handshake so that applications can perform custom validation when required.

Additionally, we request support for uploading and using standalone public keys (PEM/DER) as native crypto objects. At present, users must wrap a public key in an X.509 certificate before it can be used in DataPower, even when only the public key is needed. Allowing standalone public keys would simplify integrations and common cryptographic use cases.

These enhancements would improve flexibility, simplify secure integrations, and enable customers to implement advanced security requirements beyond the built-in TLS validation mechanisms.

Idea priority Medium