IBM Sterling Ideas
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.
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.
Customer requirement is to to use ISAM web portal for HTTPS multi factor authentication and ISAM also generates the Token after successful authentication before it handover the request to SSP. The SSP will pass userid and token to the SEAS.
The requirement is SEAS should be able to validate the token generated by ISAM without customer user exit. Since both are IBM product and SEAS already can integrate with ISAM using userid and password. Customer wants to extend the SEAS functionality to validate the SSO token created by ISAM.
|What is your industry?||Healthcare|
How will this idea be used?
This will help CSRA to integrate ISAM web portal for HTTPS protocol to leverage multi factor authentication
Do not place IBM confidential, company confidential, or personal information into any field.