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.
BKFS - SSP GUI Visibility
No GUI visibility for account locks over SFTP at proxy level
REST API to delete one user or entry from a user store instead of deleting the whole userstore
Limit CM-BACKUP to Defined Number of Backups
This would benefit all users of SSP who have the configuration managers set to backup on startup within the System Settings CMSystemSettings global tab. Right now SSP creates an unlimited number of backup. This requires users to run separate scrip...
Create Locally Authenticated Admin User via Command Line
In the event that our LDAP authentication fails for whatever reason is there any way via the command line to create a locally authenticated admin account so that we could logged back into the application GUI?
Ability to see perimeter server status on SSP (i.e. monitioring - running/stopped)
Currently we're unable to see which perimeter servers are active on the Sterling Secure Proxy engines, this in turn can cause issues if duplicates are present. This would mimic the monitoring ability currently in place for adapters.
Add built-in report for bruteforce attempts.
The Sterling Proxy is our gateway between
the internet and SFG. As such, we are
exposed to attempts to guess user IDs
using brutefore methods.
The raw internal logs show each event and
contain the IP address, Time, username and
number of faile...
MyFileGateway Password Policy, expiry prompt and password reset functionality for external users (i.e. LDAP via SSP/SEAS)
Ability to notify password expiry to the external users (i.e. LDAP user) via MFG
Ability for external users to be able to reset their LDAP passwords via the MFG UI.
Ability to relay the LDAP password policy to the external users via MFG
Password less and password based authentication
Problem: We have trading partners using one CDNode that may have aCDProcess using either snodeid=(id,password) or snodeid=(id) or nosnodeID. When a snodeid=(id,password) is sent, we use SEAS goingto a Directory Server. The backend server is B2Bi...
SSP CD node configuration allow selection of multiple secure protocols to allow upshifting like CD for migration efforts
The CD node entry in an SSP netmap does not permit selecting multiple protocols in the Secure+ panel. This inhibits SSP from negotiating properly with CDs where more than one protocol is selected.
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...
Do not place IBM confidential, company confidential, or personal information into any field.