Grouper Developers Forum

[Tom Zeller <>]

Is it desireable and/or possible to customize auditing ?

For example, let's say it is important for an organization to audit a custom attribute of a group (e.g. email address) or an unknown-to-grouper attribute of the subject (e.g. department) performing a modification. And, for this hypothetical situation, the organization would like to use database trigger driven auditing rather than hooks because triggers are more reliable. So, whenever a group or membership is changed, they want to write the email address of the group or the department of the subject who made the modification to the audit record as a name=value attribute for later historical use.

Would customized auditing dictate a particular audit record data structure ?

TomZ