Administration Security
Authentication History
Authentication History view
The Authentication History view displays a log of authentication events. An authentication event occurs each time that a user tries to log in to the system. Such an event can succeed or fail, depending on whether the user enters a valid user name and password. You cannot edit information that is displayed in the Authentication History view.
Prerequisites
This view lists authentication events only if the setting FRMSECURITY001 (AUTHENTICATION_EVENT_TO_DB) (on page 1) is set to true.
To access this view, you must have the System - Manage privilege.
You can use the Authentication History view to track user login activity, monitor how long a user was logged in, and identify any activity that might jeopardize system security. You can also use the authentication history to reveal patterns of high and low system use and to identify the heaviest users of the system. Authentication events remain in the log until purged. The Authentication History view shows all failed authentication events irrespective of the scope at which they take place. You can use the ARGOPURGE007 (PURGE_AUTHENTICATION_HISTORY) (on page 1) and ARGOPURGE039 (PURGE_AUTHENTICATION_HISTORY_DAYS_TO_RETAIN) (on page 1) settings to configure the frequency at which the authentication history records are purged. For more information, see Purge settings.
You can use the Display menu to export the current list to either an Excel spreadsheet or a .CSV file. N4 also provides the time stamp in the default file name for the file.
If a N4 instance shuts down while some users are still logged in, N4 cannot record a logout time for those users in the Authentication History view (on page 1) before the Java Virtual Machine (JVM) shuts down. In this case, when you restart the N4 instance, the Current Users Monitor view displays erroneous user records.
You can use the Authentication History view (on page 1) Actions
Fix Missing Logout Times to add a logout time for the entries where the log in time is more than one day. This ensures that the Current Users Monitor view correctly lists only the users that are currently logged in. The Fix Missing Logout Times action does not affect the users that are currently logged in because they have new entries in the database table. To access the Fix Missing Logout Times action, you must have the DEBUG_SYSTEM_DIAGNOSTICS privilege.