000017355 - All user report gives incorrect last login date in Authentication Manager 7.1 patch 28

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000017355
Applies ToRSA Authentication Manager 7.1. SP4
IssueAll user report gives incorrect last login date in Authentication Manager 7.1 patch 28
Administrator creates ALL USER REPORT to identify the users who have not been logged in the past 180 dates for audit purpose. During the cleaning of the data, he noticed that the last login date is not accurate.
Edit user record and view user record have two different last login dates.
If a user has two tokens, the token date for a token gets updated as last used date. However, the last login does not get modified in edit user page and the report gets this incorrect date.
Since the administrator is heavily relying upon last login date in 'All User report' it is critical for him to get this corrected for audit requirement.
Resolution

Contact RSA Security Technical Support to obtain the hot fix for defect AM-28033. The hot fix consists of a SQL script to correct this issue.

1. Run the user report to check the last login date for users in question.


2. Update the login date for all users: 

    a. Copy the script update-all-user.sql to Authentication Manager/utils same directory.
    b. cd Authentication Manager/utils
    c. Connect to SQLplus.
        rsautil manage-secrets -a get com.rsa.db.root.password
         Enter master password:
         You will get the password for sysdba account.
    d.  Command to connect:
         cd utils
        $ sqlplus sys/<value from step c > as sysdba

      d. Execute the script as shown below:
           @update-all-user.sql


3. Run "All User Report" and verify the last login date for users in question.

Legacy Article IDa65136

Attachments

    Outcomes