Results 1 to 2 of 2

Thread: Audit policy (audit fields/columns on database)

  1. #1
    Join Date
    Mar 2005
    Location
    Madrid, Spain
    Posts
    71

    Default Audit policy (audit fields/columns on database)

    Dear members,

    We need in our appplication to informs about the following action in to a particular tables:
    • Who modified the register on a given table?
    • Who created/delete the register on a given table?
    • Who read the register on a given table?
    Such information we have to audit because the Data Protection Low in our country.

    I am wondering about how to do that in a elegant way. We are planning to use Acegi for security concern, so I guess there is a way to obtain the authentification user name via Acegi, so we can use the user information for example on the DAO's in order to insert the audit information for the actions: query, modify, update, create, delete.

    The way to make such audit operation, we expect can be done in a non intrusive way for example via AOP interceptors.

    I guess we can't do that via trigger directly on data base because we don't have the information about the currently authentified user.

    Do you have any idea about how solve this problem?

    Thanks in advance,

    David
    ______________________
    David Leal

  2. #2
    Join Date
    Sep 2006
    Location
    UK
    Posts
    8,424

    Default

    I would have thought that AOP would be a good way of solving the problem. There are plenty of examples of logging interceptors I guess the same thing could be applied to audit interceptors.

    There is an article here regarding audit interceptors in Hibernate.
    http://www.hibernate.org/318.html

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •