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.
SSH User Identity Key > 2,048 bit
Partner ask to generate a auth key of 4,096-bit or larger, however Sterling menu doesn't allow for any key size except 1,024, 1,536 or 2,048. Also, there does not appear to be a documented and supported method to generate a key pair using a comman...
Enable FIPS support for HSMs in Sterling B2B Integrator
Sterling B2B Integrator does not support FIPS enabled HSMs. As it is a security requirement that FIPS mode is enabled in HSMs, Sterling B2BI should provide this support so that certificates can be protected by HSMs
Multi Factor Authentication for Administrator accounts
Need to be able to require Multi Factor Authentication for administrative accounts in B2BI, SSPCM, SEAS.
Allow segregation of administrators to discrete lists of trading partners
Our organization has multiple business units. We need the ability to assign administrators so that they can make changes to only those accounts assigned to their business unit. Example - Trading partners A, B, and C are assigned to business unit A...
Have the User ID in SB2Bi / SFG / MyFG case-insensitive
Currently the User Id information of a SB2Bi / SFG / MyFG User is case-sensitive. This means that when creating the user with myUserId as the UserID, the authentication will only be possible by entering myUserId (and not myuserid or MYUSERID which...
Support for MQ version 9.2, currently supports upto v18.104.22.168
Our Implementation uses Global Mailbox and the current version of B2Bi (22.214.171.124, 6.1.1) supports maximum MQ version 126.96.36.199. Our Security and MQ team have identified a security vulnerability with version 9.1.x.x which is remediated with version 9....
Local "admin" account logon logs should be captured
Recently, we observed one issue with by default local accounts logon logs in Sterling Integrator application. Logs are getting captured when the authentication log is in debug mode. Logs are not getting captured when authentication log is in non-d...
Providing a list of supported encryption keys.
VENDOR supported Keys Keys that will be supported RSA (3072) Ed25519 ECDSA (nistp521) The feedback from the PepsiCo ECG team below is we only accept the following supported keys: PepsiCo supported keys ssh -rsa 2048, ssh-rsa 1024, ssh-rsa , ssh-dss
Capture partner TLS version information during handshake
For all communications protocols (FTPs, SFTP, AS2, ConnectDirect etc), we would like to capture TLS version in logs. In case of upgrades, it helps to work with respective partners to upgrade to supported TLS version.
SFTP SSH Known Host Key ssh-ed25519 format
our customer are using ssh-ed25519 ssh key format we are not bael to add this format in SI SSH Known Host Key
Do not place IBM confidential, company confidential, or personal information into any field.