IBM Support

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

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

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 number

    PI95167

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    624

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-03-14

  • Closed date

    2020-07-23

  • Last modified date

    2020-07-23

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"624"}]

Document Information

Modified date:
24 July 2020