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.
Provide a read-only role for the Partner Repository
We'd like to be able to provide sponsor users who are not admins a way to have read-only access to the items in the Partner Repository, such as Code Lists, Generic Data, etc.
More algorithms support for diffie-hellman
Understand that current supported SSH Key Exchange Algorithms:diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1,diffie-hellman-group14-sha1
However, is it possible to support more diffie-hellman algorithm?
Sterling External Authentication server (SEAS) Admin UI needs to be ported over from thick to Web client
System : Sterling External Authentication server (SEAS) Actor : MFT Administrators Presently to setup, install and configure SEAS we need to use Java thick client which is a Java WS application connecting on non-standard ports and requiring a Wind...
Feature of Looping to be incorporated on Tasks/Dialogs/API calls etc
Feature of Looping needs to be added on Tasks/Dialogs/API calls etc. Instead of stretching the current flows statically, it is always advisable to have dynamic looping feature, which would make the flows scalable. It not only makes the flow scalab...
Single Sign On for PEM
Support Single Sign On for PEM to allow integration with identity management systems. This critical to comply with security requirements and verify user/partner identity. From a user experience, this is needed to provide a more seamless client/par...
AES-256 encryption for .bin file creation
we understand that when a .bin file is created via lcu.jar it is encrypted with AES-128. We would like to see this encryption increased to AES-256 to satisfy our Security requirements.
Should be able to import ED25519 format remote SFTP host keys
This functionality would allow B2B Integrator to manage SFTP file transfer activities with trading partners who are using ED25519 format remote host keys.
Add the ability to administer division partners and LOB users via the PEM Portal UI
Currently, Divisions can be created via the portal UI, however, the assigning/unassigning of partners to divisions and the assigning/unassigning of LOB users can currently only be done via API calls. It would be much easier if this could be done v...
reading Source IP address from HTTP headers through for example X-Forwarded-For
Currently there is a dynamic routing feature to read incoming source IP address and base the routing based on this value. However many organizations dont support having source IP address hitting the SSP engine servers. Usually the incoming IP addr...
Enable authentication by token on the Sterling B2B REST API
Seems like currently the B2B REST API only supports authentication of basic type, where username/password is sent in header of get/post/put HTTP call. Can there be a mechanism to authenticate via bearer token? Thanks very much!
Do not place IBM confidential, company confidential, or personal information into any field.