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 (

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 Planned for future release
Created by Guest
Created on Jun 23, 2021

Need SSL/TLS support for Global Mailbox to post its events to Control Center

Most other connections are firmly secured in B2Bi/SFG/GM, with one significant exception; the ability to post events and heartbeats from Global Mailbox to Control Center (ICC or CCM). By default, CCM 6.2 disables its non-secure web port, 58082. Since heartbeats often have host names and IPs in them, that event information is considered sensitive by most file transfer teams and their information security groups. It should not be posted through plain HTTP. Additionally, credentials are passed in the clear when authenticating to Control Center without support for TLSv1.2. A suggested set of relevant properties are as follows (

- Non-secure URL to use for posting (already there) to Control Center

- Secure URL to use for posting to Control Center

- Protocol (would contain TLSv1.0 (also default), TLSv1.2, TLSv1.1, TLSv1.3 when available)

- Cipher (specify the preferred cipher between GM and ICC/CCM.

- Trust (establish the same way as dbConfigUtility does (trustAny, chooseTrust) or a path and key store name.

- Passphrase for trust store (should be encrypted like other passphrases in

- Optional: Key store (if client-side TLS is possible between GM/ICC/CCM

- Optional: Key store passphrase (same property type as trust store passphrase)

What is your industry? Travel & Transportation
How will this idea be used?

This idea will be used to secure connections between Global Mailbox and Control Center. Due to the fact IPs and host names, as well as credentials for authorization to post are considered sensitive, this connection should be securable and associated passphrases and passwords encryptable.