This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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...
Let keystore/truststore fields directly editable in the Admin Web Interfaca
In SEAS 6.0 GUI it was possible to specify keystore/truststore as local to the server in the GUI. In SEAS 6.1 the keystore/trust must be fetched from the users LAPTOP as the browse functionality is local to the browser and input fields are protected.
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
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...
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...
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...
Do not place IBM confidential, company confidential, or personal information into any field.