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.
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...
Add REST API for the RUN TIME information
REST API for the RUN TIME details (Connect, Validate, Invalidate, Generate, etc.,) will be helpful and simplify the integration with other systems.
SFG/SI users changing password with SEAS
There is presently no way to for a myfilegateway user to change their password if Sterling External Authenticator is used. Which seems odd because SFG can talk to SEA and validate an SSO token. There needs to be a feature to allow users to change ...
Email alerts for SEAS errors
Currently errors within SEAS cannot be detected without logging into the server and manually checking the SEAS logs. LDAP related failures (for example loss of connectivity to LDAP or expired password for the login we bind to LDAP with) are an exa...
include the encrypt/decrypt (export/import) passphrase into the properties file for rest api calls
We were looking to find a way to automate updating passwords for some of our accounts within SEAS utilized in our connection settings. It prompts for a decrypt passphrase that we cannot seem to pass values through automatically via script and we w...
Add "Session ID" for SEAS authentication attempts
In a high-traffic system it can be difficult to determine which log entries in the seas logs are related to a given authentication attempt. Currently we're forced to grep / search for the specific username /timeframe and then manually parse throug...
Inactive User Accounts Controls - Administrator and user Accounts
Application parameter settings that do not automatically disable and/or remove user accounts after a specified period of inactivity may result in unauthorized access, modification, destruction, and/or disclosure of confidential information
Allow utility scripts like changepassphrase.sh, SEASCipherConfigTool.sh, seasRestAPI.sh to run in non interactive mode
Currently I'm not able to run scripts like changepassphrase.sh, SEASCipherConfigTool.sh, seasRestAPI.sh in the non interactive mode. There is no option to pass the multiple input passphrases to those scripts. Those scripts will also error out if I...
SEAS Logging Update - User Account/Key Auth
We have SEAS pointing to an LDAP for authentication. When a user account fails to authenticate via SSH public/private key, the logs show that failure in 'error' mode, but that line does not contain the useraccount that failed to log in. We can onl...
More detailed ERROR logging for SEAS
SEAS logging at ERROR level does not provide sufficient information regarding authentication failures, forcing us to keep logging level at DEBUG which uses an extremely high amount of disk space in order to have sufficient log retention. For examp...
Do not place IBM confidential, company confidential, or personal information into any field.