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.
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 && Destin...
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 ...
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.
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.
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...
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 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 ...