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
Post 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,
Post an idea
Upvote ideas that matter most to you
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 notification 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.
For product documentation, see Knowledge Center. Create and View Support Cases and Use the Discussion Forum here
Connexion/authentification to SP with SSO SAMLV2 or OIDC
In our company, user rights are managed using an IAM which allows central management of access authorizations.
The current implementation of SP doesn't allow us to use our authentication server and our IAM as it doesn't provide SSO capabilities and doesn't manage user profiles.
We use IDP (Identity Service Provider) for :
- authenticate users;
- transmit and certify the identity of the authenticated person (to CAS clients).
Would it be possible to have the 2 following evolutions:
- SSO using SAML V2 or OIDC (OpenId Connect) protocols, directly in SP
- Possibility to create user profiles (ex : project owner / Exploitation / product owner) with possibility to associate rights in SP to those profiles.
Do not place IBM confidential, company confidential, or personal information into any field.