Account Lockout Upon Failed Login Attempts Does Not Apply to LDAP Users

(Doc ID 571526.1)

Last updated on MARCH 19, 2018

Applies to:

Oracle Agile PLM Framework - Version 9.2.2.6 and later
Information in this document applies to any platform.

Symptoms

Actual Behavior
Account Policy is set from Java Client but account lockout upon failed login attempts does not apply to LDAP users. 

Fact
Account lockout applies to Agile created Users

Steps

  1. Set Account Policy from Java Client > Admin > User Settings > Account Policy

    Account Lockout : Enabled
    Logon Attempts : 3
    Reset Count Time (in minutes ) : 1
    Lockout Duration (in minutes ) : 0
    Account Lockout Notify User : user1

  2. Login to non-LDAP user on web client 3 times with wrong password

    1st try
    ==> Invalid User ID or password.

    2nd try
    ==> Warning: If your next login attempt fails your account will be locked.

    3rd try
    ==> You have exceeded the number of allowable login attempts and your account has been locked. Please contact your PLM Administrator.

  3. Login to LDAP user on web client 3 times with wrong password

    1st try
    ==> Invalid User ID or password.

    2nd try
    ==> Invalid User ID or password.

    3rd try
    ==> Invalid User ID or password.

 

Changes

See symptoms and solution sections.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms