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.
enhancement request to implement "ecdh-sha2-nistp256", "ecdh-sha2-nistp384", "ecdh-sha2-nistp521" algorithms
We have customers who use the NIST-ciphers for key exchange. The IBM support-Team told us, that Sterling Secure Proxy does not currently support the NIST key Exchange algorithms. So, we are asking for it to be implemented as soon as possible.
Add SSL Support between Sterling Secure Proxy Configuration Manager / Engine and WebSphere MQ
Security mandates that all the connections need to be secured. WebSphere MQ supports SSL but not SSP CM / SSP Engine, adding this functionality allows meeting the newer security requirements.
Hooks to enable the SSO Authentication for SSPDashboard URL
Add TLS 1.3 Support to Sterling Secure Proxy
Option for TLSv1.1 or Higher in FTPS Netmap
Request to either add an option for TLSv1.1 or higher under FTPS netmap > Security > Secure Connection > Security Setting for a FTPS adapter, or remove SSLv3 and TLSv1 from the "SSLv3, TLSv1, TLSv1.1, or TLSv1.2" option under the same loc...
SSP Custom User Roles
Right now SSP currently allows for two user roles (Admin, Operator)within the application. We would like to be able to create custom roles based on specific user requirements so exact permissions can be assigned.
SSP Welcom Page *make change to force 1st time users to change password.
Looking for solution in SSP welcome page for HTTPS users to be forced to change password on initial login. Current versions don't account for attribute in LDS/AD if the account is defined with attribute of expired.. Allowing the user / password t...
Enable SAML SSO on secure proxy server
We have an existing requirement as follows. The trading partners are required to login to myFIlegateway through SSP Http adapter. SSP should be configured to support SSO using 3rd party application. Below is the sequence of events, should happ...
Increase Key Exchange Security
We have a merchant who can't complete connectivity to SSP SFTP because they don't support the Key Exchange we currently have available.Their preference would be to use these kex protocols:ecdh-sha2-nistp256 ephemeral-ephemeral elliptic curve ...
secure proxy does not support HSTS. it needs to.
IBM Sterling Secure Proxy does not support an HSTS policy on the HTTPS adapter.
Do not place IBM confidential, company confidential, or personal information into any field.