Audit actions typically map to com.waveset.security.Right objects. When adding new Right objects, you must specify a unique two-character logDbKey, which will be stored in the database. You may encounter situations where there is no right to correspond to a particular action that must be audited. You can extend actions by adding them to the list of objects in the extendedActions attribute.
Each extendedActions object must include the attributes listed in Table 10–17.
Table 10–17 extendedAction Attributes
Attribute |
Type |
Description |
---|---|---|
name |
String |
The name of the action, which is used when constructing AuditEvents and during event filtering. |
displayName |
String |
A message catalog key that represents the name of the action. |
logDbKey |
String |
Two-character database key to use when storing this action in the Log table. See Audit Log Database Mappings for reserved values. |
All customer-specific keys should start with the # symbol to prevent duplicate keys when new internal keys are added.
Table 10–17 illustrates adding an action for Logout.
<Object name=’Logout’> <Attribute name=’displayName’ value=’LG_LOGOUT’/> <Attribute name=’logDbKey’ value=’LO’/> </Object> |