PH47025: FILE REPOSITORY ACCOUNT LOCKOUT POLICY CAN DELAY EXPIRING FAILED LOGINS

APAR status

• Closed as program error.

Error description

• The ignoreFailedLoginAfter expiration from the File Repository
  account lockout policy can be delayed.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  using a file repository with the user       *
  *                  account                                     *
  *                  lockout feature enabled.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: The ignoreFailedLoginAfter expiration   *
  *                      from the File Repository account        *
  *                      lockout                                 *
  *                      policy can be delayed.                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The ignoreFailedLoginAfter expiration from the File Repository
  account lockout policy can be delayed. The
  ignoreFailedLoginAfter attribute sets the time when failed
  logins should be cleared or expired (if the
  accountLockoutThreshold has not been exceeded). In this
  scenario, if the ignoreFailedLoginAfter attribute is set to 15
  minutes and the user has a failed log again after 16 minutes,
  the user can have 2 failed logins recorded instead of 1 failed
  login (where the prior login should have expired after 15
  minutes). The failed logins will expire, but can be delayed (for
  example, expiring after 17 minutes instead of the configured 15
  minutes). This could lead to an account lockout earlier than
  expected, depending on the timing of failed logins.
  

Problem conclusion

• The code was fixed to expire old logins promptly.
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.23 and 9.0.5.13. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels