Audit Logging
The audit log records user account security and administrative activities.
Audit log entries include information such as the event ID, affected account, date and time, and the source of the request. Audit entries are stored in the WST_AUDIT_LOG table.
Use this topic to understand user account audit events, identify account lockouts and account status changes, and determine the appropriate action.
User Account Audit Events
The following table lists the user account audit events recorded in the audit log. In each event description,
| Event ID | Level | Description | Occurs When |
|---|---|---|---|
| 282 | Error | User |
A failed login attempt takes the account past the maximum login retry limit. |
| 283 | Error | User |
A login attempt is made against an account that was already locked. |
| 284 | Information | User |
An administrator successfully unlocks a locked account. |
| 285 | Information | User |
An administrator successfully disables an enabled account. |
| 286 | Information | User |
An administrator successfully enables a disabled account. |
Note: Events 282 and 283 are associated with the account lockout policy configured in PPM Administrator under Security » Password Policies using Max Retries Before Lockout. Events 284, 285, and 286 are generated by administrative account actions. To unlock an account, navigate to Security » Users, select the user, and use the Unlock link on the Authentication tab.
Troubleshooting
The following table lists common causes of each audit event and recommended actions.
| Event ID | Possible Cause or Meaning | Recommended Action |
|---|---|---|
| 282 | The account exceeded the configured login retry limit. | Verify that the user is using the correct credentials. Review recent failed login activity, address the cause, and unlock the account in PPM Administrator if access should be restored. |
| 283 | A login attempt was made after the account had already been locked. Repeated entries indicate repeated attempts against the locked account. | Review the source machine and related failed-login activity. Correct stored or automated credentials if applicable. Unlock the account only after the cause has been addressed. |
| 284 | An administrator successfully unlocked the account. | No corrective action is normally required. If the account is locked again, review events 282 and 283 to identify the source of the attempts. |
| 285 | An administrator successfully disabled the account. | Confirm that disabling the account was intended. Review the administrator and source information recorded with the event if the change was unexpected. |
| 286 | An administrator successfully enabled a previously disabled account. | Confirm that enabling the account was intended and that the user should regain access. |