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 Future consideration
Created by Guest
Created on May 29, 2018

Enable Account Lockout after 3 failed logins

Passwords are prune to Brute
force attacks, an attacker can easily brute force the passwords as the password policy is weak and
allows simple alpha numeric characters without any restriction of password length e.g.: admin, pass
Account lockout mechanisms are used to mitigate brute force password guessing attacks. Accounts
are typically locked after 3 to 5 unsuccessful login attempts and can only be unlocked after a
predetermined period of time, via a self-service unlock mechanism, or intervention by an
administrator. Account lockout mechanisms require a balance between protecting accounts from
unauthorized access and protecting users from being denied authorized access.

IBM Private Cloud uses the Liberty OIDC implementation as the Authentication service. Today, Liberty does not provide the account lock out for multiple failed logins for the basic and the LDAP user.

Idea priority High
RFE ID 120612
RFE Product WebSphere Application Server
  • Guest
    Oct 22, 2020

    we are accepting the request on the basis of doing some kind of locked, however the implementation may not be done in exactly the way requested in the summary.

  • Guest
    Mar 13, 2020

    This security vulnerability is identified by IBM Security AppScan Standard iFix001, Rules: 17393 due to Inadequate Account Lockout by Liberty Admin Console. This is the IBM WebSphere Liberty Profile included in the IBM TRIRIGA installation package for Application Platform This references Liberty Admin Console not locking out an account after multiple incorrect login attempts.