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
We are looking for a way to be able to log anytime any changes are made ANYWHERE in SEAS with an entry showing what the previous setting was vs the new setting and who made the change. Currently no matter what amout of debug logging is turned on t...
Selecting Active Directory Group for authentication
Instead of selecting each user from LDAP and give access. If we have option to select the Active Directory Group(low_pre_access_group, high_pre_access_group) from LDAP and assign to access. It will be helpful and reduce task of adding every new us...
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...
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.
PIV was initially introduced by HSPD-12 (Homeland Security Presidential Directive 12), in August of 2004. However, it is just now that agencies are being mandated to comply with this directive. The first required delivery date that we know of for ...
Develop SEAS to intelligently query for IPs that come from a subnet and allow them in if that subnet is in an LDAP attribute
Why useful? Useful because these days a lot of trading partners are coming from cloud environments that aren't front-ended by one (or a handful) IP address. Who benefits? Anyone who desires to whitelist IPs as a means of authentication or just as ...
Do not place IBM confidential, company confidential, or personal information into any field.