|
Problem IC82079
|
Status: Closed |
INCORRECT APPLICATION ID MAY BE WRITTEN IN DB2AUDIT LOG |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
When audit log is taken for validate category record, the
authentication event may have incorrect application id for
failing authentication.
The following an example for failing authentication from a
remote client with invalid user id and password. Its application
id is recorded in a wrong format.
timestamp=2012-03-16-14.49.19.722368;
category=VALIDATE;
audit event=AUTHENTICATION;
event correlator=2;
event status=-30082;
database=SAMPLE;
userid=e95q5f;
execution id=REMOTEAPP;
origin node=0;
coordinator node=0;
application id=09BDCC35.07BA.120316054921;
application name=odbcad32.exe;
auth type=SERVER;
plugin name=IBMOSauthserver;
The following is a successful authentication event record for
the same remote client. Its application id is recorded
correctly.
timestamp=2012-03-16-14.15.53.539512;
category=VALIDATE;
audit event=AUTHENTICATION;
event correlator=2;
event status=0;
database=SAMPLE;
userid=e95q5f;
authid=E95Q5F;
execution id=REMOTEAPP;
origin node=0;
coordinator node=0;
application id=9.189.204.53.11270.120316051553;
application name=odbcad32.exe;
auth type=SERVER;
plugin name=IBMOSauthserver; |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* User using db2audit *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 9.5 Fix Pack 10. *
**************************************************************** |
| Local Fix: |
|
| Solution |
Problem was first fixed in DB2 UDB Version 9.5 Fix Pack 10. |
| Workaround |
Not available. |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC84470 IC87902
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.03.2012
31.08.2012
31.08.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.10
|
 |
