Grouper Developers Forum

[Chris Hyzer <>]

The audit types are not mandated, there are just built-ins… so an institution could create their own audit type, and then insert into the audit entry table via trigger, no problem.

 

The problem with your scenario is the record being updated happens before the audit record insert, so its hard to update it via trigger.  You could put the email address in another table, and have a loader process which puts it back in an audit misc field.  Though there is still the issue of customizing a misc field.

 

With your particular use case, and I assume you are talking about user auditing, and not point in time, then since user auditing is done via java, and not triggers, then there really isn’t any reason to use triggers to customize the audit record I think, we could just expose an audit hook and you could customize.  However, all that said, I think getting too far into this sounds like a good idea for phase 2  J

 

Regards,

Chris

 

From: [mailto:] On Behalf Of Tom Zeller
Sent: Saturday, February 07, 2009 6:50 PM
To: Chris Hyzer
Cc: Grouper Dev
Subject: Re: [grouper-dev] Action Items: Grouper Call 4-Feb-09

 

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