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 RFE to make generic authentication more robust
According to the SEAS L3 team this is basically working as designed. The Generic authentication do come with limitation, your user will be mapped to 1 user, in your case, this is admin user.
SEAS CRL and use of cached CRL
Enable SEAS to be configured in the UI to allow the cached CRL to be used after the refresh interval has expired. In the current setup, unchecking 'Reject expired CRL' does so, but also fails authentications at the end of the refresh interval.
SEAS to allow different passphrase for the KEYCERT and Keystore and Trustore
SEAS has to allow different passphrase for the KEYCERT and Keystore and Trustore. When submitting a CSR to Symantec CA a certificate passphrase has to be setup. Currently it MUST match Keystore and Trustore passphrase or certificate import and/or ...
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...
OpenLDAP support - Force password change on File Gateway Logon
We use OpenLDAP for password authentication of our external customers. Spoke with IBM developers (listed in PMR - Naru Manda) and was told that when Sterling was written because OpenLDAP did not have a password policy at the time, that no hook was...
Admin User ID Creation Automation specifically for SEAS.
System : SEASActor: User needing automated Admin User id on-boarding. SEAS presently we have to use Java Thick client to log in and create Admin users. As part of the firm-wide initiative they need the Admin users on-boarding/off-boarding to be au...
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...
SSP User ID based routing in clustered environment
They are detailed in the attached document
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...
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...
Do not place IBM confidential, company confidential, or personal information into any field.