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.
Enable CRL Cache for CRL Check using the Distribution Points
Support First Time Password change between SSP/SEAS and B2Bi managed user accounts and subsequent password change should be allowed via SSP password portal to change the B2Bi password through SEAS.
Support for Active Directory pooling or putting Domain Controller behind a VIP
We would benefit using a VIP to hit Domain Controllers in one or multiple data centers or using pooling of Domain Controllers
PIV Card Support for Sterling MFT/B2B Products
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 fo...
SEAS Validating ISAM Token
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.
Add REST API for the RUN TIME information
REST API for the RUN TIME details (Connect, Validate, Invalidate, Generate, etc.,) will be helpful and simplify the integration with other systems.
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...
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...
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.
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.