Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform 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 Not under consideration
Workspace WebSphere Liberty
Created by Guest
Created on Sep 12, 2018

Security exposure in Liberty federated repository behavior

When multiple LDAPs/user registries are configured, user login will prompt a search against all LDAPs. Say I configure IBM bluepage LDAP, and Amazon LDAP. When user tom@ibm type user id and password, we send to both IBM bluepage and Amazon LDAP. Although tom@ibm will be only authenticated by bluepages, and rejected by amazon LDAP, there are several concerns.

1. If name tom@ibm does not exist in Amazon, Amazon still see tom@ibm attempts to login to Amazon. Amazon can build a list of IBM employee names who tries to "hack" into their LDAP.
2. The tom@ibm's password may be leaked to Amazon.

Idea priority Urgent
RFE ID 124649
RFE Product WebSphere Application Server
  • Guest
    Aug 23, 2021

    Thank you for submitting this request for enhancement. We are choosing not to implement this because our belief is that configured LDAP providers need to be completely trusted. As a general rule, we will not implement enhancements that harden security around untrustworthy LDAP providers.