Skip to Main Content
Cloud Platform

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

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 a notification 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.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to for resolution.

For more information about IBM's Ideas program visit

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
  • Admin
    Gary Picher
    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.