Auditing reports the incorrect USER_NAME value in the AW_AUDIT_REPORTS_TABLE

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

When Auditing is enabled in Applications Manager, there is a rare chance that the incorrect USER_NAME is recorded in the AW_AUDIT_REPORTS_TABLE

This behavior occurs only when a Job or Process Flow runs on a Schedule. Adhoc Requests are not affected.

When a Job or Process Flow is scheduled to run, auditing will log the current and next run times. In addition to this, auditing will record the User making the update as "OSU=<am user> JDBC Thin Client". This is the expected behavior as seen in the Audit Report below under the 'Change By' column:

However, there is a rare occurrence where instead of the changed by value being listed as "OSU=<am user> JDBC Thin Client", auditing will report a random User. This random User is likely in an active client session (logged in).

Environment

Release : 9.3

Component : APPLICATIONS MANAGER

Resolution

An additional check has been put in place to ensure that "OSU=<am user> JDBC Thin Client" is the recorded value when a Job or Process Flow is scheduled.

This fix will be included in Applications Manager version 9.4.1