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.
SSP to support 9000+ IPs/range nodes in Inbound Netmaps for all protocols
Currently, we have 9000+ IPs/CIDR ranges to allow the traffic from. We have added 9000+ entries in Netmap nodes but when we try to edit/save/add more nodes manually the SSP CM GUI is hanging/breaks/not responding properly/going to inoperable state...
Urgent - SSP increase the Netmap Inbound Node limit to support 9000+ nodes
Currently, we have 9000+ IPs/CIDR ranges to allow the traffic from. We have added 9000+ entries in Netmap nodes but when we try to edit/save/add more nodes manually the SSP CM GUI is hanging/breaking/not responding properly. In the same way we hav...
Urgent - SSP Netmap Inbound nodes limit increase to support 9000+ nodes
Currently, we have 9000+ IPs and CIDR ranges to be whitelisted/allowed on each and every protocol Netmap. After adding all these 9000 entries to a netmap GUI is not responding properly, add/save/edit of new/existing nodes is breaking the entire SS...
Forward client IP for all protocols from sterling secure proxy to sterling file gateway
Currently SSP forward IP for HTTP Protocol to sterling b2b integrator but it doesn't have capability to forward client IP for other protocols to sterling b2b integrator. We have a regulatory requirement to capture IP for all inbound files/transact...
RHEL8/RH8 Support for IBM Secure Proxy
SSPCM currently supports RHEL7 (which reaches "End of Support" in Aug 2021.
Rather than installing a new instance of SSPCM and its components onto RHEL7 and then repeating the process again on RHEL8 once its supported. It'd be extremely usef...
Additional Authentication Exit in SEAS/SSP
External authentication is already achieved through SEAS, however, if additional authentication logic is required then the only way to achieve this is through a SEAS custom exit. Use of a SEAS custom exit means that we have to re-write the existin...
Introduce option in IBM SP to pass on the HTTP host header from client to the backend application
Currently IBM SP when configured as a HTTP Reverse Proxy, does not pass the HTTP host header from the client's request to the backend application. The request here is to have this a configurable option, similar to Apache's ProxyPreserveHost option.
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.
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...
Sterling External Authentication Server High Availability Scenario Failover Mechanism Needs
We would like to extend the options of failover scenarios in SSP-SEAS integration. In high available configuration, where there are two active SEAS, when one of the servers are down, the other takes over the others responsibilities. However,...
Do not place IBM confidential, company confidential, or personal information into any field.