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.
To implement PEM SSO current PEM can only use custom attribute / attribute with which can only return one string. Expected output as mentioned below.
Sample output user role:
Current requirement is AD team will have multiple groups created and have them added to memberof AD attribute. So, there is no static limit on number group that a user is part of. IBM PEM current configuration cannot accommodate this use case.
Below mentioned use case requires appropriate query with | (or) condition with & (and) to filter among multiple user roles specific to the application.
Had discussion with IBM SEAS team through IBM support ticket.
But L3 team has asked us to submit an enhancement request as this is not accomplished as part of the current application capability.
Sample output on Roche specific requirement:<name>prefferedLanguage</name> <value>US</value></property><property><name>role-1</name><value>CN=xxxx-xx,OU=xx,OU=xx,DC=xx,DC=xx,DC=com</value></property><property><name>role-10</name><value>CN=xx11,OU=xx,OU=xx,DC=xx,DC=xx,DC=com</value></property><property><name>role-11</name><value>CN=xx22,OU=xx,OU=xx,DC=xx,DC=xx,DC=com</value></property><property><name>role-12</name><value>CN=xx33,OU=xx,OU=xx,DC=xx,DC=xx,DC=com</value></property>
We would require capability to add | condition in the LDAP filter query which would allow us to compare multiple groups and also to return only the groups that are relevant to the query.
|What is your industry?||Healthcare|
How will this idea be used?
As the customer is moving to the complete SEAS based SSO implementation for the complete MFT implementation. This limitation is becoming a roadblock in the process migration to meet the deadline.
Do not place IBM confidential, company confidential, or personal information into any field.