PI95167: NO MATCHING LOCK EVENT TO UNLOCK EVENT IN THE AUDIT LOG

APAR status

• Closed as program error.

Error description

• When users are locked after entering an incorrect password too
  many times there should be an audit log entry indicating that
  the user was locked out. Currently, there is only an entry when
  the user's account is unlocked.
  
  In order for a user to be locked out of the system, the Allowed
  Login Attempts for the Authentication Realm must be set to a
  number other than Zero, which indicates that unlimited attempts
  are allowed. After a user, who was created in that
  authentication realm, has been locked out an Administrator will
  see an option to unlock the user account. Doing so creates the
  unlock user audit entry. When the user is locked out there
  should be a lock user audit entry.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All end users on all supported browsers.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When users are locked after entering an incorrect password   *
  * too                                                          *
  * many times there should be an audit log entry indicating     *
  * that                                                         *
  * the user was locked out. Currently, there is only an entry   *
  * when                                                         *
  * the user's account is unlocked.                              *
  *                                                              *
  * In order for a user to be locked out of the system, the      *
  * Allowed                                                      *
  * Login Attempts for the Authentication Realm must be set to a *
  * number other than Zero, which indicates that unlimited       *
  * attempts                                                     *
  * are allowed. After a user, who was created in that           *
  * authentication realm, has been locked out an Administrator   *
  * will                                                         *
  * see an option to unlock the user account. Doing so creates   *
  * the                                                          *
  * unlock user audit entry. When the user is locked out there   *
  * should be a lock user audit entry.                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Fixed in version 7.1.0.1                                     *
  ****************************************************************
  

Problem conclusion

• Fix is provided in IBM UrbanCode Deploy 7.1.0.1
  

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

  UC DEPLOY

• Fixed component ID

  5725M5400

Applicable component levels