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.

External User should not add in ICC clasic console when we have configured LDAP to authenticate external users

IBM Control Center authenticates with LDAP if we created external users specifically in ICC classic console though we have configured LDAP with SEAS.

 

The Feature Should be as below:

1.) ICC should validate if the user is local or external. If user is not present in ICC classic console, ICC should look the user in LDAP using SEAS and it should not be a mandatory field at ICC classic console to reach SEAS to validate user at LDAP.

 

Present available feature and not a good feature at ICC:

Though we have configured LDAP using SEAS, still we have to manually create no. of users who needs access to ICC web console. This feature is making no point of configuring LDAP to ICC.

 

 

  • Guest
  • Oct 2 2019
  • Under review
How will this idea be used?

This idea would definitely help to avoid dependency in creation of users specifically though we have configured LDAP to authenticate external users.

This idea definitely gives a point in order not to create users again explicitly at ICC console.

What is your industry? Banking
What is the idea priority? Urgent
  • Attach files