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.
SEAS CRL to go through proxy connections
Enable SEAS to use a proxy connection when going out to check the CRL in order to avoid production incidents when an IP behind the CRL URL changes suddenly. Application server sits in a DMZ behind a firewall.
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...
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 ...
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 thro...
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
RHEL8/RH8 Support for SEAS
SEAS currently supports RHEL7 (which reaches "End of Support" in Aug 2021.
Rather than installing a new instance of SEASand its components onto RHEL7 and then repeating the process again on RHEL8 once its supported. It'd be extremely useful to k...
Functionality to test profiles
We need some method to test a configured SEAS engine before integrating it with the rest of our environment. Currently we can only test it by pointing SSP to the new engine and attempting to log in. This means that we can't test the SEAS config ...
SEAS SSO token synchronization
We need a way to synchronize the SSO tokens generated on one SEAS server to another SEAS server. This is needed for redundancy and failover support. Currently SSP points to a Primary SEAS Server and SI points to the Primary SEAS as well. If SSP fa...
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 exampl...
Add REST API, or some way to retrieve config details outside of the UI
For auditing purposes we have to regularly pull a list of users from all of our applications along with their permission level / role, and last login information. For SEAS this process currently requires logging into the UI and manually copying t...
Do not place IBM confidential, company confidential, or personal information into any field.