IBM Sterling Ideas
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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you, 1. Post an idea 2. Upvote ideas that matter most to you 3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
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 (global.properties):
- 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 global.properties
- 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.
Do not place IBM confidential, company confidential, or personal information into any field.