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
Configuring the SEAS to only respond with (UserID & Destination Indicator) in response to SSP and forward the Authentication request (Password/SSH Key) aganist/to Sterling integrator local store?
The process/flow will follow the below steps from (User to SSP to SEAS to SI) Step 1 - User Authentication request comes from SSP layer to SEAS; Step 2 - SEAS validates the user against connected AD and return only "UserID/Username && Dest...
Currently SEAS has the ability to integrate with IBM product ISAM ( IBM security access manager ) and authenticate the userid and password provided by SSP. In this case SEAS generates SSO Token after successful authentication.
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...
BKFS - Centralized administrator User Provisioning for SEAS
User accounts created in LDAP must also be created in the following GUIs: SFG, SSPcm, Control Center. Ability to centralize/ "one time" provisioning for all Sterling software would simplify the system administration.
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.
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...
Do not place IBM confidential, company confidential, or personal information into any field.