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.
Add more Ciphers for SSH to security.properties supported by JDK8
Please enable the following Ciphers: diffie-hellman-group14-sha256
hmac-sha2-512 Kind Regards
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...
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
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...
RestAPI support for Token Authentication rather than Basic Authentication
Looking for a future service availability to support Token Authentication, either with RestAPI or new one. As per my conversation with an IBM engineer on another troubleshooting call; support of Token Authentication by RestAPI is planned in future...
SSO and OAuth support for authenticating B2BAPI access
At minimum would need to able to use the SEAS SAML like tokens to allow authentication of APIUser for B2BAPI calls. Liberty Profile native supports both SAML /OAuth authentication and the current instance does authenticate with B2Bi so it should a...
Enhance SAP Suite adapter to support Secure Network Communication (SNC)
Support JCO3 SNC parameters in SAP Suite Adapter in B2B Sterling Integrator. SNC secures the data communication paths between the SAP System components and B2B Sterling Integrator. It will add additional security feature for secured communication.
Allow email address to use as user ID
We have requirement to use email address as the user ID in sterling integrator.
Allow a SFG Community to allow using more than one PGP key for decryption.
Allow a SFG community to allow partners to use the existing key or the new key to encrypt their data with so that SFG then can use either PGP key for decryption - this will allow partners to make changes in a gradual way , when we generate new PGP...
Include special characters (e.g. @) in Parameter Name of Obscure Data - Process Data Values service
We are using SI 220.127.116.11 and the Parameter Name does not allow special characters such as "@" being used in the Obscure Data - Process Data Values service. This prevents email addresses being used as Names.
Do not place IBM confidential, company confidential, or personal information into any field.