Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Oct 2, 2019

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.



What is your industry? Banking
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.