000012868 - In RSA Archer, Users show as logged in, but Login History shows System Impersonated session type.

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

Article Content

Article Number000012868
Applies ToRSA Product Set: Archer
RSA Version/Condition: 5.3 and 5.4.0
IssueUsers shows as logged in. Login History shows System Impersonated session type.
  1. Open one of the users that should not be logged in.
  2. Click on the Last Login timestamp to see the Login History.
  3. You should see a System Impersonated session type.
From Manage Users, nothing happens when clicking the Force Disconnect icon for a logged in user. The user still shows Logged In.
CauseSystem Impersonated sessions are used for backend processes like Data Imports or sending Notifications.
The System Impersonated sessions should only last long enough to complete the task/process. Unfortunately, there is a known defect where the System Impersonated session remains active.
 
ResolutionThe defects have been fixed since 5.3.1.7 and 5.4.0.2.
Release Tracker 7369475: System Impersonated sessions are created and stay active for users when a notification is sent to the user (5.4.0.2 fix).
Release Tracker 7343199: System Impersonated sessions are created and stay active for users when a notification is sent to the user (5.3.1.7 fix).
Legacy Article IDa64002

Attachments

    Outcomes