Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps products. 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 Planned for future release
Created by Guest
Created on Dec 2, 2021

make ldap-configuration more customizable

For a NOI installation running on OCP with LDAP mode proxy, it is an absolute requirement that the users icpadmin and impactadmin must exist in the connected LDAP. The names of these users are not freely selectable, but must be exactly the same. This is not practical in most cases, as many companies have specific policies regarding the name or password security for LDAP users. Thus, when installing NOI on OCP, it should be possible to assign individual names and to use special characters in the password.
Idea priority Urgent
  • Guest
    Mar 19, 2024

    Isabell - this has come up again for another customer

  • Guest
    Mar 15, 2024

    Any update on this? 

    This has just  been recently flagged as an issue with one of our customers who are going into production with NOI on OCP (using mostly Runbooks and Impact).

    These system users should absolutely be internal only and LDAP should be only used for external Authentication.

  • Guest
    Apr 26, 2022

    We are assessing this at the moment from a product development perspective.

    We intent to move the impactadmin and icpadmin users out of the connected LDAP, and use internal technical users for this. So you likely no longer will have to configure users with names not complying to corporate policies in the corporate LDAP. Those user will be kept internally to the OCP installation then, likely within a separate small LDAP pod.