Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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 Under review
Categories APIs & SDKs
Created by Guest
Created on May 1, 2025

EPSDK API should allow caller to specify keystore and truststore for SSL/TLS connections

When Control Center is configured for SSL, an application using the EPSDK should be able to specify the keystore and truststore to use for SSL connections.

Currently the EPSDK does a few things that don't work well

1. The SDK sets up a Trust Manager that trusts All SSL certificates. This is very insecure.

2. The SDK uses the APIs HttpsURLConnection.setDefaultHostnameVerifier(..) and HttpsURLConnection.setDefaultSSLSocketFactory(..). These set SSL settings for ALL HTTPs connections in the application. If there are other parts of the application that rely on these APIs, they could override the settings the EPSDK wants to use and cause problems. We have seen this in our application and it took days to figure out why our Control Center events were not being sent.


The ask is:

1. Do not Trust All SSL Certificates. The API should provide an option to provide a keystore and trust store that should be used for HTTPs connections to Control Center. Additionally some other options like the ability to control hostname verification would be good.

2. Do not use HttpsURLConnection.setDefaultHostnameVerifier(..) and HttpsURLConnection.setDefaultSSLSocketFactory(..). The EPSDK should set SSL settings only for the connection it is making. Any SSL settings for the EPSDK should not affect SSL settings for other HTTP connections.


What is your industry? Other
How will this idea be used?

This is required for IBM Global Mailbox which is part of the B2Bi/SFG product.