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 Is a defect
Created by Guest
Created on Aug 13, 2018

One incorrect password blocking LDAP servers

Problem reported:

When the user logs in to an application that relies on WebSphere to authenticate to an LDAP server (Microsoft AD) and types the wrong password, we verify that:

• The wrong password is sent to the main LDAP server + 1 retentative
• If we have the Primary LDAP Server + 1 LDAP Failover Server sent 1 for each + 1 retentative on the principal. In this case with 3 wrong password

Our policy is that if the user misses the password 5 times it blocks the user.

We requested improvement in WebSphere regarding this case so that in case the first LDAP server deny the password is not passed on to the others. Only be passed to the others if the LDAP Server is out. And not due to incorrect credentials.

Idea priority High
RFE ID 123528
RFE Product WebSphere Application Server
  • Guest
    Nov 5, 2021

    Hi, I am reviewing this RFE, and the behavior that you are looking for is already how WebSphere is designed to work. The backup LDAP server should only be contacted if the primary is down, not because of an incorrect password. I notice that you originally had a support case opened against this, however that case, for whatever reason, was not looked at by WebSphere security, and unfortunately I believe that it was closed prematurely. Given that you already had a case open for this, I would like any new cases for this problem to be expedited directly to the WebSphere security experts. If you are still encountering this problem, I would encourage you to please open a new case, and mention that Gary Picher requested for the case to be sent to WebSphere L2 support right away.

  • Guest
    Aug 13, 2018

    Maybe you could list your current configuration. If you have an LDAP configured in global security the backup LDAP should not be tried if a bad password is entered.